E-File Magic

MCP clients

Send an MCP message

Authenticated MCP Streamable HTTP transport.

POST
/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
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.json

Use 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.