Skip to main content
Connect MCP-compatible clients to the MTA API using Streamable HTTP. Endpoint

Authentication

API key

Send your MTA API key as Authorization: Bearer <key>. Requests use the same authentication, metering, quotas, and plan limits as REST API requests.

Clerk OAuth

Clients that sign in instead of sending an authorization header can use Clerk OAuth. The account needs a paid plan for data access. The first data-tool call creates an MCP (auto) API key for usage; it appears with the account’s other keys on the dashboard.

Connect a client

Use an API key in clients that support custom headers. Clients without custom headers can connect using Clerk OAuth.
Set MTA_API_KEY in your shell, then run:

Transit tools

Transit tools are read-only. With an API key, each call is authenticated and metered exactly like the corresponding REST request.

PATH tools

OAuth-only account tools

Account tools need Clerk OAuth sign-in (scopes openid profile email) and act only on the signed-in user’s own keys and billing.

Errors and limits

If Clerk OAuth is used without an eligible paid plan, a data-tool call that needs to create the usage key returns plan_required. Choose a plan from the billing dashboard, then retry. Data-tool text output includes any quota headers returned by the REST API: X-MTA-API-Request-Cost, X-MTA-API-Credits-Remaining, X-MTA-API-RateLimit-Limit, and X-MTA-API-RateLimit-Remaining. Calls remain subject to the account’s REST plan and rate limits.