MCP clients
Send an MCP message
Authenticated MCP Streamable HTTP transport.
/mcp- Authentication
- OAuth access token for MCP
- Required scopes
- See authentication requirements
- Idempotency key
- Not required
How to use this endpoint
Availability depends on the account and current human authorization. The server uses stateless JSON responses and advertises its supported protocol versions; clients must not assume persistent sessions or a resumable event stream. Use POST for protocol messages and tool calls. Tools expose only their admitted filing-preparation operations and existing scoped API schemas; they cannot submit or pay for a filing on the user’s behalf.
curl --request POST '<origin from OAuth metadata>/mcp' \
--header 'Authorization: Bearer <access-token>' \
--header 'Accept: <Accept value>' \
--header 'Content-Type: application/json' \
--data-binary @request.jsonUse the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Create request.json using the documented fields. Field descriptions are not sample values.
Request fields
2 fieldsjsonrpcSee descriptionSee description
MCP JSON-RPC envelope for POST. Use tools/list for the currently authorized tool catalog and exact argument schemas.
_rulesSee descriptionSee description
Mutation tool arguments require a stable idempotency_key (16–128 letters, digits, hyphen, underscore, dot or colon); preserve it after an uncertain response. HTTP headers cannot substitute for this argument.
Headers (2)
AuthorizationRequired- OAuth Bearer token for the MCP resource.
AcceptRequired- MCP Streamable HTTP accepted response types, including application/json and text/event-stream.
curl --request POST '<origin from OAuth metadata>/mcp' \
--header 'Authorization: Bearer <access-token>' \
--header 'Accept: <Accept value>' \
--header 'Content-Type: application/json' \
--data-binary @request.jsonUse the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Create request.json using the documented fields. Field descriptions are not sample values.
Successful outcomes: ok.
No response example is defined for this operation. Refer to its response fields and outcomes.
Errors to handle
Use the returned status and code to decide what to correct or retry.
- 400
invalid_request - 401
invalid_token - 403
access_denied - 503
temporarily_unavailable - Agent access is unavailable.