MCP endpoint
POST
/api/mcp
JSON-RPC 2.0 over stateless Streamable HTTP (one request in, one
response out; no persistent connection or session state). Authenticate
with
Authorization: Bearer <access_token> using a token minted byPOST /api/oauth/token above. The token's audience (if the client senta
resource at authorization) is bound to this endpoint, and access isgated on the account's connector access entitlement, separate
from, and available on every plan including Free, unlike the
/api/v1 REST surface's paid-only API access entitlement (seeForbidden below and docs/connectors.md's "Access requirements").initialize, ping, tools/list,tools/call. tools/list returns five tools: publish_website,confirm_publish, list_websites, get_website, delete_website,each with its own JSON Schema, which is the authoritative contract for
its arguments (see docs/connectors.md for a plain-language summary).
a good fit for OpenAPI's per-operation schema model, so the body below
is intentionally left generic rather than forcing a fake, misleading
schema onto it.
Request
Body Params application/jsonRequired
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://upload.tf/api/v1/api/mcp' \
--header 'x-api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": "string",
"method": "tools/call",
"params": {}
}'Response Response Example
200 - Example 1
{
"jsonrpc": "2.0",
"id": "string",
"result": {},
"error": {
"code": 0,
"message": "string"
}
}Modified at 2026-08-07 15:42:15