Stoory Hire Specialist

io.github.StooryBotPublished by GitHub account StooryBotv0.1.0Updated Oct 25, 2026

Find and hire a human specialist from the Stoory marketplace, right from chat.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an AI assistant search the Stoory marketplace for human specialists, draft and send a task with a budget, track it, and cancel it before work starts.

What you can do
Search the Stoory marketplace for human specialists by natural-language query, with broader retries when hits are few or only alternative fits appear. Draft and send a task to one or more chosen specialists with a title, description, budget and deadline, attaching only selected files by link or upload. Retrieve the full task record: status, budget, deadline, timeline, invited and accepted specialists, and attached files. Cancel a task while the specialist has not yet started work.
When to use it
Use it when a project needs human expertise the assistant cannot supply, such as legal or privacy review, payment integration fixes, design or SEO work, and you want to find, brief and track a specialist without leaving the chat.
Requirements
A remote MCP endpoint over Streamable HTTP, reachable from an MCP-capable client. A free Stoory client account and a client API key, sent in the x-api-key request header. Network access to the Stoory service.
Before you install
The API key identifies your account and must be kept secret. Creating a task sends your brief and the files you attach to Stoory and to the invited specialist, so check the file list and budget before confirming; the server scans attachments for secrets but you should still avoid sharing sensitive files. Task creation requires explicit user confirmation. Stoory does not process payments; you settle payment with the specialist directly outside the platform.

Installation

In SourceWeft

  1. Open Stoory Hire Specialist in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.StooryBot%2Fstoory-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stoory-hire-specialist": {
      "type": "http",
      "url": "https://mcp.stoory.io/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

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 (430+ specializations: dev, legal, design, growth, operations) with a natural-language query.
  • Package a task: your AI assistant drafts the title, description, and budget, and attaches only the files the specialist actually needs — shared by link or uploaded to the task, never your whole repo.
  • Hand off safely: files are attached privately to the task on Stoory, visible only to the invited specialist — no repo to create or manage.
  • Track progress: one call returns the whole task — status, budget, deadline, the invited/accepted specialists, and every file (yours plus whatever the specialist delivers) pulled back into your AI workspace.

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 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, Replit, Lovable, ...).
  • 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), 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.

Claude Code
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" }    }  }}
Claude Desktop / Claude.ai

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.)

Cursor

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" }    }  }}
Windsurf

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" }    }  }}
VS Code

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" }    }  }}
Codex CLI

Add to ~/.codex/config.toml:

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

Replit connects MCP servers at the account level — added once, available in every project. Open Settings → MCP Servers, click + Add MCP server, then:

  1. Name it stoory.
  2. Paste https://mcp.stoory.io/mcp as the server URL.
  3. Open Advanced settings and add a custom header x-api-key with your key.
  4. Click Test & save.
Lovable

Open Settings → Connectors, and under Personal connectors click Custom. Paste https://mcp.stoory.io/mcp as the remote MCP server URL and click Add.

(Lovable's custom connector currently authenticates via OAuth only. If there is no field for a custom x-api-key header, header-key auth isn't available in Lovable yet — use Claude Code or another client above in the meantime.)

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

ToolWhat it does
search_specialistsSemantic search over Stoory's specialist marketplace
create_taskDrafts and sends a task to one or more chosen specialists (requires explicit user confirmation)
get_taskReturns the whole task record — status, invited/accepted specialists, budget, deadline, and files (your context files plus whatever the specialist delivers)
cancel_taskCancels 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        │        ▼Task created on Stoory, files attached privately, 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.
  • You pass those files as a link or a direct upload — the server has no access to your disk and never reads local paths.
  • Attachments are stored privately on the task, visible only to the invited specialist.
  • Files are scanned for secrets (.env, private keys, API keys/tokens) on the server before they're stored.
  • 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, attaches them privately to the task, and    invites the specialist. Done.

Community & support

  • Marketplace & signup: stoory.io
  • Issues / bugs: GitHub Issues
  • MCP Registry entry: io.github.StooryBot/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.

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.

Source: README.md at commit aaa6c67

Tools

4

search_specialists

Search specialists

Searches for specialists in the Stoory marketplace via semantic search. Result quality depends mostly on a well-built `query` — see the `query` field description. If a result has <3 hits or only 'Alternative fit', retry with a simpler/broader query (see `query`) instead of asking the user; only after about 3 failed attempts tell the user you have no one to recommend for these requirements and suggest widening the criteria.

Parameterslimitqueryrequiredcountrylanguagesgeo_location

create_task

Create task

Invites one or more chosen specialists to a project — does NOT charge payment. budget is a single amount for the whole task (not multiplied per specialist) — whoever accepts it does the work for it. Requires user_confirmed=true, set only after the user has explicitly confirmed in the conversation the choice of specialists, the list of shared files and the estimated cost. Estimate budget yourself from the problem's complexity (e.g. 1h = a single well-localized bug / a simple document fix / a minor graphic tweak; 2h = a standard debug across a few files / a draft legal document (e.g. Privacy Policy) / a landing page design; 3h = an architecture review, a full legal package (ToS+Privacy+GDPR) or a compliance audit, full branding, no clear diagnosis) times the specialist's min_rate_per_hour (from search_specialists) — this field is informational, not enforced, always in USD (the only currency on the marketplace).

Parameterstitlerequiredbudgetrequiredlanguagerequiredtimelinedescriptionrequiredcontext_filesspecialist_idsrequireduser_confirmedrequiredproblem_contextrequired

get_task

Get task

Returns the whole task record in one call — use it both to check progress and to read the result. Fields: status, title, desc, budget, deadline, timeline, created, modified; specialist_invited and specialist_accepted (arrays of { id, profile_url } — profile_url is already in the right language, show it to the user as a link, not a bare id); and `files` — URLs of every file attached to the task on Stoory (the client's context files plus whatever the specialist delivers). Call it again when the user asks about progress. create_task already returns attached_files for the files it uploaded.

Parameterstask_idrequired

cancel_task

Cancel task

Cancels the task, as long as the specialist has not started work yet.

Parameterstask_idrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.