https://api.peel.sh/mcp that speaks JSON-RPC over HTTP POST; every platform tool is a one-to-one wrapper over a REST route, and your endpoints are called through call_endpoint.
Connect a client
Use OAuth when your client supports it, or an API key for a fixed credential. See Authentication.- OAuth (any client)
- API key
- Claude Code
cursor://anysphere.cursor-mcp/oauth/callback.
Use it from an agent
- Call
list_apisto reuse an API, orcreate_apiwith aurlandinstructionsto build one. Passwait_for_completion: trueto wait. - Call
get_apiwith theapi_id. Readstatus,endpoints[].endpoint_name,input_schemaandexamplesbefore calling anything. - If
get_apireturns a non-nulluser_input_prompt, callrespond_to_api_input. For a live question (user_input_prompt.liveistrue) sendresponse: { "question_id": "...", "answer": "..." }. - Call
call_endpointwith theapi_id,endpoint_nameandparams.
tools/call request for call_endpoint:
result is an MCP tool result. result.content holds a text item with the same JSON envelope REST :call returns (status, status_code, data, error_code, execution_time, credits_charged), and result.isError may be set.
Protected endpoints take session_id and encryption_key as top-level arguments, next to api_id and endpoint_name, never inside params. See Signed-in and action endpoints.
Platform tools
Each tool maps to one REST route. The scope is the OAuth scope a bearer token needs; API keys are not scoped.
Parameters for each tool are in
tools/list, and each REST route is in the API Reference. Every tool in tools/list has a title. Every platform tool has an outputSchema, and so does an endpoint tool whose stored output schema strict JSON Schema 2020-12 validators accept; the stored schema describes the result’s data. A schema with a nested $id, a $ref outside #/$defs or #/definitions, or a property named like a built-in object member (such as toString or constructor) gets no outputSchema, and that tool’s results are text only. A successful result from a tool with an outputSchema carries structuredContent that matches it, next to the same JSON as text for older clients. Errors and refusals set isError and come back as text only.
Reaching any read route
When no tool covers what you need, such as the source export or your webhooks, find the route withsearch_routes, read its parameters with describe_route, and call it with call_read_route:
status_code and body, exactly as a direct REST call with your key returns them. The call runs as your API key, so the key’s access, its team role and an API limit refuse it the way they refuse the REST call. It calls GET routes only; changes go through their own tools. It needs an API key: OAuth sign-ins get api_key_required, since the REST API takes only keys. File routes and the long-polling wait route are left out.
Direct JSON-RPC clients
- Send an
Acceptheader that includesapplication/jsonortext/event-stream. Otherwise Peel returns406. - Peel serves the stateless
2026-07-28revision. Callserver/discover, orinitializeas older clients do (next item). Withserver/discover, put the version in each request’s_metaasio.modelcontextprotocol/protocolVersion. If you also send theMCP-Protocol-Version,Mcp-MethodorMcp-Nameheaders, they must match the body. Discovery results and the keylesstools/listmay be cached for an hour (cacheScope: "public"). Thetools/listof/mcpand of each API’s server depends on your key, so it iscacheScope: "private"with a one-minutettlMs. - Clients that initialize can negotiate
2025-11-25,2025-06-18,2025-03-26or2024-11-05. A request without a protocol-version header is treated as2025-03-26. - Send one JSON-RPC request or notification per
POST. Batches are accepted only under2025-03-26. - A body that is not JSON answers
-32700Parse error with HTTP400. JSON that is not a request object or a batch array, such as a string, number,trueornull, answers-32600Invalid Request with HTTP200. tools/liston/mcppages withnextCursor. Send it back unchanged: a cursor that is altered, empty or from another key answers-32602Invalid params. The keyless and per-API servers list every tool on one page, so any cursor there answers-32602.GET /mcpandDELETE /mcpreturn405.
client_id that is an HTTPS URL to the client’s metadata, as ChatGPT uses) or with dynamic client registration. Authorization responses include iss.
One MCP server per API
Each API also has its own MCP server athttps://api.peel.sh/mcp/apis/{api_id}. Its tools are that API’s endpoints and nothing else, so an agent that only needs one integration sees a short tool list. export_mcp returns the URL as connect.url. It accepts the same OAuth tokens and API keys as /mcp.
Without an account
https://api.peel.sh/mcp/keyless takes no key and offers only the marketplace tools, for public data calls under the same daily limits as REST. See Call without an account.
Long builds as tasks
Builds take minutes. Clients that declare the MCP Tasks extension (io.modelcontextprotocol/tasks) get a task back from create_api, revise_api and rebuild_api instead of waiting:
tasks/getreportsworking, thencompletedwith the API, orinput_requiredwhen the build asks a question.- A question arrives as an elicitation. Plain questions are forms; answer them with
tasks/update. Secret questions, such as a texted code, are URL elicitations that open the API’s page on Peel, so the code never passes through the agent. tasks/cancelacknowledges cancellation.
get_api. Webhooks give servers the same progress.
Errors
Tool-level failures such as
404 Endpoint not found or an error_code use the same shapes as REST. See Errors.