Guided article

Start with the public manifest to discover NetShow's MCP endpoint. Discovery does not require an account or execute a tool. Authenticated tool calls remain subject to the caller's permissions and execution limits.

4 min read 398 words Developers

Manifest

GET /api/mcp/manifest returns the public manifest. Read its advertised protocol and capabilities before configuring your client.

curl --max-time 30 \
  https://app.netshow.ai/api/mcp/manifest \
  -H 'Accept: application/json'

The public agent card is also available at GET /.well-known/agent-card.json; see the A2A guide for peer-agent discovery.

Your MCP token

POST /api/mcp is the authenticated JSON-RPC 2.0 endpoint, and every call carries your MCP token. To get one, sign in, open your agent from your agents, choose MCP connection (the card headed "Use this agent inside Claude") and press Create connection. Copy the token it shows: you see it once, and it works for 30 days. Replace the literal <YOUR_TOKEN> locally; never paste a real token into documentation, shared logs or a recipe. A harness pairing session token does not work here.

List the tools visible to your authenticated caller:

curl --max-time 30 \
  https://app.netshow.ai/api/mcp \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer <YOUR_TOKEN>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Use the returned tool names and input schemas when constructing tools/call requests. Tool visibility does not bypass owner approval, destination checks, feature availability or spend admission. Missing or invalid authentication returns 401; inspect JSON-RPC errors as well as the HTTP status.

Rate limits

MCP inherits the API limiter: 60 requests per minute per authenticated user, or per IP for public discovery. On 429, honor Retry-After before resuming. Bound client timeouts and cancel requests when the caller leaves. The A2A 20 per minute route throttle and its hourly buckets apply to A2A routes, not to this MCP endpoint.

Lane ceilings

For metered customer MCP execution, the owner sets a daily spend ceiling for MCP in their dashboard; zero means closed. An exhausted or closed lane refuses execution. Public manifest discovery itself does not authorize spending. No live deployment ceiling or environment value is published here.

Owners can inspect their permitted tools at What the Harness can use. This discovery door requires sign-in, verification and the harness discovery feature; it returns 404 when unavailable. For a local connector, continue with Harness pairing, or find all three guides in the developer docs.

Use your agents inside Claude Code, Cursor and VS Code

Sign in with POST /api/user/login to get a NetShow token. It lasts 7 days. Replace <YOUR_TOKEN> on your own device and keep the real token private.

After connecting, ask your client to run tools/list. Then try agent_list to find your agents and agent_chat to talk to one.

Claude Code

Run this command in your terminal:

claude mcp add --transport http netshow https://netshow.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

For a project configuration, create .mcp.json at the project root:

{
  "mcpServers": {
    "netshow": {
      "type": "http",
      "url": "https://netshow.ai/api/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Cursor

Create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "netshow": {
      "type": "http",
      "url": "https://netshow.ai/api/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

VS Code

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "netshow": {
      "type": "http",
      "url": "https://netshow.ai/api/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Was this helpful?

We can turn this into interactive help, search, and guided checklists next.

Ready to meet your AI agent?

Create your first agent free. No credit card required.

Get Started Free

MCP Developer Guide