Startup Rocket

Public MCP server

Connect an agent directly to Startup Rocket.

Startup Rocket exposes an authenticated MCP server at POST /mcp. If the founder already has an account, this is the default way to let an agent fill the packet, manage evidence, and keep working inside the same venture over time.

Use OAuth when an existing user wants to authorize an external agent app. Use a manual bearer token when you are doing internal, operator, or local setup. Use x402 only when you need to create a brand-new founder submission before anyone is signed in.

If you want the decision tree first instead of the raw docs, start on Agent Assist.

OAuth-aware MCP clients can now discover Startup Rocket automatically through /.well-known/oauth-protected-resource/mcp, /.well-known/oauth-authorization-server, and the public /register client-registration endpoint.

Available tools

Founder tools

  • list_startups
  • get_startup
  • create_startup
  • update_startup
  • get_submission_packet
  • update_submission_packet
  • list_evidence_items
  • prepare_evidence_file_upload
  • create_evidence_item
  • update_evidence_item
  • delete_evidence_item
  • create_startup_invitation
  • update_startup_handoff

Investor tools

  • list_ventures
  • get_venture
  • update_venture_handoff
  • create_venture_diligence_thread
  • resolve_venture_diligence_thread
  • update_venture_routing_decision

Setup flow

  1. 1. Create a Startup Rocket account or sign in to an existing one.
  2. 2. Point your MCP client at https://startuprocket.railsplayground.com/mcp.
  3. 3. If the client supports OAuth discovery, let it register and complete the OAuth 2.1 PKCE flow automatically.
  4. 4. If you are doing local or operator setup, create a manual API token and send it in the Authorization header.
  5. 5. For file-backed evidence, call prepare_evidence_file_upload, upload the bytes, then attach the returned signed_blob_id in an evidence tool call.

Claude Example

For OAuth-capable Claude setups, point the client at the MCP URL and let Startup Rocket handle discovery and PKCE authorization. 

{
  "mcpServers": {
    "startuprocket": {
      "transport": "http",
      "url": "https://startuprocket.railsplayground.com/mcp"
    }
  }
}

If your Claude setup does not support OAuth discovery yet, fall back to a manual bearer token in the Authorization header.

OpenClaw Example

Example MCP registration for OpenClaw using the same HTTP endpoint. OAuth-capable clients should let Startup Rocket complete discovery and PKCE automatically. 

{
  "servers": [
    {
      "name": "startuprocket",
      "transport": "http",
      "url": "https://startuprocket.railsplayground.com/mcp"
    }
  ]
}

For clients that still require static auth headers, use the same MCP URL with Authorization: Bearer <token>.

Example prompts

  • Create a founder venture: “Create a new startup called Orbit Ledger, then fill the canonical packet with the summary I provide.”
  • Attach URL-backed proof: “Add a traction evidence item linking to our pilot usage report and connect it to the users_growth claim.”
  • Attach file-backed proof: “Prepare an upload for this PDF, upload it, and attach it as financial backup for runway_months.”
  • Work investor-side feed flow: “List ventures with strong readiness and evidence coverage, then open a diligence thread on the best match.”
  • Drive follow-through: “Find startups with pending investor asks and update founder handoff status where materials were sent.”

How it fits with x402

  • x402 is for public paid venture creation before a user is signed in.
  • MCP is for authenticated ongoing work once an account or token exists.
  • x402 can seed URL-backed evidence at intake time.
  • MCP is the right surface for later packet edits, follow-through, and file-backed evidence uploads.