MCP

What the connector gives your AI

Everything the workspace can do, as tools the assistant calls mid-conversation: search live buyer demand and what is already being built, read market gaps and buyer clusters, list your builds and their deliverables, start an agent in a build and read its cards, check whether a build's deliverables still agree, and add to the knowledge base. The results are the same cards, runs and reviews you see in the workspace, and they appear there too.

What to ask for

• “What are accelerator programme managers paying for right now, and where is supply thin?”
• “Give me the brief and the deliverables of the Verdict Evals build before I plan the sprint.”
• “Run the Gap Validator in that build on this idea, then read the verdict back to me.”
• “Do the deliverables in this build still agree? Show me what needs review.”
• In a coding assistant: “Pull the solution design and its business rules from Growhold and implement the first slice.”

What stays your decision

Reading is free-form. Changing a build is not: starting a run spends credits like it does in the workspace, and accepting or dismissing a deliverable review is only done when you say so. The server tells the assistant this, and the tools follow the permissions of the key or connector you created.

Sign in from the assistant (OAuth)

For assistants that add connectors by signing in, such as Claude on the web and desktop: create an OAuth client on the API & Devs page, then add Growhold as a custom connector in the assistant with the server address, the client id and the secret. The assistant signs in with your workspace and the tools appear in every conversation. Revoking the client disconnects it at once.

Use an API key

For assistants and agents configured by file or command, such as Claude Code, Cursor and Claude Desktop: create an API key on the API & Devs page and give the client the server address with the key as a bearer token. Keys are scoped by area, so a key with only the knowledge permission gives an assistant market intelligence and nothing else.

Client configuration

Every client takes the same two things: the address and the Authorization header. The shape most clients use:

{
  "mcpServers": {
    "growhold": {
      "url": "https://api.growhold.com/mcp",
      "headers": { "Authorization": "Bearer gh_your_api_key" }
    }
  }
}

Available tools

Permissions and credits

A tool is offered only when the key or connector carries its permission: knowledge, runs, schedules, agents or specialists. Market intelligence queries, chat and agent runs spend the workspace's credits at the same prices as in the app; listing and reading cost nothing.

Raw JSON-RPC

curl -X POST https://api.growhold.com/mcp \
  -H "Authorization: Bearer gh_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

curl -X POST https://api.growhold.com/mcp \
  -H "Authorization: Bearer gh_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "search_demand",
      "arguments": { "query": "monthly KPI collection from portfolio companies", "limit": 10 }
    }
  }'