Skip to main content
ClaudeWave

Official Stoory MCP server — hire a human specialist (dev, legal, design, growth, ops) from Claude, Cursor, or any MCP client.

MCP ServersOfficial Registry0 stars0 forksUpdated today
ClaudeWave Trust Score
70/100
· OK
Passed
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Flags
  • !No standard license detected
Last scanned: 8/25/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/StooryGitServer/stoory-mcp-server
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "stoory": {
      "command": "node",
      "args": ["/path/to/stoory-mcp-server/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/StooryGitServer/stoory-mcp-server and follow its README for install instructions.
Use cases

MCP Servers overview

# Stoory MCP Server

**Hire a human specialist from your AI workspace — without leaving it.**

AI can build most of your app. It can't get you GDPR-compliant, review your
Stripe integration, design your landing page, or run your SEO. Stoory MCP lets
your AI coding assistant find, brief, and hire the right human for that —
without you ever opening Upwork, writing a job post, or explaining your
problem from scratch.

---

## What it does

- **Search** Stoory's marketplace (400+ specializations: dev, legal, design,
  growth, operations) with a natural-language query.
- **Package a task**: your AI assistant drafts the title, description, and
  budget, and picks only the files the specialist actually needs — never your
  whole repo.
- **Hand off safely**: a private GitHub repo is created per task, shared only
  with the invited specialist.
- **Track progress**: check status and pull results back into your AI
  workspace once the specialist is done.

You stay in control of the two decisions that matter — **who to hire** and
**what budget to approve**. The agent does the rest.

See [Tools](#tools) below for the full list.

---

## Quickstart

### Requirements

- Any AI client that supports MCP over Streamable HTTP (Claude Code, Claude
  Desktop, Claude.ai, Cursor, Windsurf, VS Code, Codex CLI, ...).
- A free Stoory client account and API key (below).

### 1. Get a client API key

Sign up at
[stoory.io/login?step=register&u=Client_(user)](https://stoory.io/login?step=register&u=Client_\(user\)),
then open **MCP Server** on the Stoory homepage to generate your
`client_api_key`.

### 2. Add the server to your AI client

Pick your client below. The URL is always `https://mcp.stoory.io/mcp`, the
header is always `x-api-key`, but where you put them differs per client.

<details>
<summary><strong>Claude Code</strong></summary>

```bash
claude mcp add --transport http stoory \
  https://mcp.stoory.io/mcp \
  --header "x-api-key: YOUR_API_KEY_HERE"
```

Or add directly to `.mcp.json`:

```json
{
  "mcpServers": {
    "stoory": {
      "url": "https://mcp.stoory.io/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY_HERE" }
    }
  }
}
```
</details>

<details>
<summary><strong>Claude Desktop / Claude.ai</strong></summary>

**Settings → Connectors → Add custom connector.** Paste
`https://mcp.stoory.io/mcp` as the URL, open **Request headers**, add
`x-api-key` with your key, then click Add.

(Request header auth is currently rolling out at Anthropic. If you don't see
a "Request headers" option yet, use Claude Code or another client below in
the meantime.)
</details>

<details>
<summary><strong>Cursor</strong></summary>

Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):

```json
{
  "mcpServers": {
    "stoory": {
      "url": "https://mcp.stoory.io/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY_HERE" }
    }
  }
}
```
</details>

<details>
<summary><strong>Windsurf</strong></summary>

Add to `~/.codeium/windsurf/mcp_config.json` — note the field is
`serverUrl`, not `url`:

```json
{
  "mcpServers": {
    "stoory": {
      "serverUrl": "https://mcp.stoory.io/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY_HERE" }
    }
  }
}
```
</details>

<details>
<summary><strong>VS Code</strong></summary>

Add to `.vscode/mcp.json` — note the root key is `servers`, not
`mcpServers`, and each entry needs `"type": "http"`:

```json
{
  "servers": {
    "stoory": {
      "type": "http",
      "url": "https://mcp.stoory.io/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY_HERE" }
    }
  }
}
```
</details>

<details>
<summary><strong>Codex CLI</strong></summary>

Add to `~/.codex/config.toml`:

```toml
[mcp_servers.stoory]
url = "https://mcp.stoory.io/mcp"
http_headers = { "x-api-key" = "YOUR_API_KEY_HERE" }
```
</details>

### 3. Ask for help

> "My AI assistant keeps breaking my Stripe integration. Find me someone who can fix it."

That's it — the assistant searches, drafts the task, shows you cost and
files before anything is sent, and waits for your go-ahead.

---

## Tools

| Tool | What it does |
|---|---|
| `search_specialists` | Semantic search over Stoory's specialist marketplace |
| `create_task` | Drafts and sends a task to one or more chosen specialists (requires explicit user confirmation) |
| `get_task_status` | Checks whether a specialist has accepted / is working / has finished |
| `get_task_result` | Returns the link to the task's private result repo |
| `get_task_repo_files` | Reads the result files directly, so the assistant can review the work itself |
| `cancel_task` | Cancels a task before a specialist has accepted it |

---

## How it works

```
"I need a GDPR specialist"
        │
        ▼
AI searches the marketplace, you pick a specialist
        │
        ▼
AI drafts the task + selects only the needed files
        │
        ▼
You confirm cost and file list
        │
        ▼
Private GitHub workspace created, specialist invited
        │
        ▼
You pull the result back into your AI workspace
```

---

## Security & privacy

**Your private data doesn't need to become public just because you need
human help.**

- Your assistant chooses which files to share — never the whole repo.
- Every task with attachments gets its own **private** GitHub repo, visible
  only to the invited specialist.
- Files are scanned for secrets (`.env`, private keys, API keys/tokens)
  before anything leaves your machine.
- Nothing is shared, and no task is created, without your explicit
  confirmation.

---

## Example

```
User: "I've built my SaaS with AI. I need a privacy policy
       and terms of service before I can launch."

AI: 5 relevant specialists found.

User: "Use #2, budget $200."

AI: Creates the task, writes the brief, selects the relevant
    project files, opens a private repo, and shares it with
    the specialist. Done.
```

---

## Community & support

- Marketplace & signup: [stoory.io](https://stoory.io)
- Issues / bugs: [GitHub Issues](https://github.com/StooryGitServer/stoory-mcp-server/issues)
- MCP Registry entry: `io.github.stoorygitserver/stoory-mcp`

---

## Are you a specialist?

Stoory MCP recommends specialists from Stoory's marketplace to clients —
if you're a developer, designer, lawyer, marketer, or any other freelancer,
a free profile makes you eligible to get invited. No commission, ever.
[Create your free profile at stoory.io/for-specialists](https://stoory.io/for-specialists).

---

## Disclaimer

Stoory MCP does not replace your AI assistant and does not perform payments
or hiring decisions on its own — it prepares the task and hands the decision
to you. Stoory does not process payments: client and specialist settle
payment for the work directly between themselves, entirely outside Stoory.
ai-agents-automationai-codingai-workersclaude-desktopcursorfreelancehiringjob-boardllm-toolsmcpmcp-servermodel-context-protocolrecruitment

What people ask about stoory-mcp-server

What is StooryGitServer/stoory-mcp-server?

+

StooryGitServer/stoory-mcp-server is mcp servers for the Claude AI ecosystem. Official Stoory MCP server — hire a human specialist (dev, legal, design, growth, ops) from Claude, Cursor, or any MCP client. It has 0 GitHub stars and its last recorded update is dated 2026-08-24.

How do I install stoory-mcp-server?

+

You can install stoory-mcp-server by cloning the repository (https://github.com/StooryGitServer/stoory-mcp-server) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is StooryGitServer/stoory-mcp-server safe to use?

+

Our security agent has analyzed StooryGitServer/stoory-mcp-server and assigned a Trust Score of 70/100 (tier: OK). See the full breakdown of passed checks and flags on this page.

Who maintains StooryGitServer/stoory-mcp-server?

+

StooryGitServer/stoory-mcp-server is maintained by StooryGitServer. The last recorded GitHub activity is dated 2026-08-24, with 0 open issues.

Are there alternatives to stoory-mcp-server?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy stoory-mcp-server to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: StooryGitServer/stoory-mcp-server
[![Featured on ClaudeWave](https://claudewave.com/api/badge/stoorygitserver-stoory-mcp-server)](https://claudewave.com/repo/stoorygitserver-stoory-mcp-server)
<a href="https://claudewave.com/repo/stoorygitserver-stoory-mcp-server"><img src="https://claudewave.com/api/badge/stoorygitserver-stoory-mcp-server" alt="Featured on ClaudeWave: StooryGitServer/stoory-mcp-server" width="320" height="64" /></a>

More MCP Servers

stoory-mcp-server alternatives