Any Other MCP Client

Requires a terminal key that's already bound to a terminal.

MT-MCP's hosted endpoint is a standard Streamable HTTP MCP server at:

https://mcp.mtcontext.com/mcp/v1

Authenticated with a single header:

Authorization: Bearer MTMCP-YOUR-TERMINAL-KEY

Any MCP client that supports Streamable HTTP transport with custom headers can connect using just those two pieces of information — check your client's documentation for where it wants the URL and header configured.

If your client only supports stdio

Many MCP clients only know how to launch a local stdio process, not connect to a remote HTTP endpoint directly. For those, use mcp-remote, a small connector that runs locally and bridges stdio to the hosted HTTPS endpoint:

npm install -g mcp-remote

Then configure your client to run:

mcp-remote https://mcp.mtcontext.com/mcp/v1

with the header Authorization: Bearer MTMCP-YOUR-TERMINAL-KEY attached. The exact place to put the command and header depends on the client — see the Claude Desktop, Cursor, and Windsurf guides for concrete examples of the same pattern.

What you get

Once connected, tools/list returns every tool documented in the Tool Reference that your subscription tier includes. There's nothing MT-MCP-specific about tool discovery or invocation — it's plain MCP throughout.

Session token refresh

Your terminal key never expires on its own (only on manual revocation), but the session token it's exchanged for does — by default after 1 hour. The hosted server handles that exchange and refresh transparently on every request; you don't need to manage it. If you're calling /api/token yourself instead of going through a standard MCP client library, see the manual token flow described in the Claude Desktop guide.