Any Other MCP Client
Connect any MCP-compatible client to MTContext.
Requires a terminal key that's already bound to a terminal.
MTContext's hosted endpoint is a standard Streamable HTTP MCP server at:
https://mcp.mtcontext.com/mcp/v1Authenticated with a single header:
Authorization: Bearer MTMCP-YOUR-TERMINAL-KEYAny 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.
Canonical connection model
No MTContext-specific client plugin is required. Any compliant client only needs:
- Streamable HTTP MCP transport.
- Server URL:
https://mcp.mtcontext.com/mcp/v1. - Header:
Authorization: Bearer MTMCP-YOUR-TERMINAL-KEY.
After connection, the client should call tools/list and display available tools based on your subscription capabilities.
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-remoteThen configure your client to run:
mcp-remote https://mcp.mtcontext.com/mcp/v1with 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 and Cursor 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 MTContext-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.
Troubleshooting
- Client says server unreachable: verify HTTPS egress and proxy/TLS interception rules.
tools/listempty or partial: check subscription capability and account context.- Auth failures: verify Bearer format and key validity.
- Intermittent failures on long sessions: ensure your client handles standard MCP reconnect behavior.