MTContext isn't tied to one AI app. It's a standard Model Context Protocol (MCP) server, so any compliant client can connect with two pieces of information. If your client isn't one of the ones with a dedicated guide, this article is for you.
The hosted endpoint
MTContext's hosted server is a standard Streamable HTTP MCP server:
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 that URL and header — check your client's docs for where it wants each. After connecting, the client calls tools/list and shows the tools your subscription tier includes. There's no MTContext-specific plugin to install; it's plain MCP throughout.
If your client only speaks stdio
Many MCP clients only know how to launch a local process over stdio, not connect to a remote HTTPS endpoint. For those, use mcp-remote, a small local bridge:
npm install -g mcp-remote
Then point your client at:
mcp-remote https://mcp.mtcontext.com/mcp/v1
with the Authorization: Bearer MTMCP-YOUR-TERMINAL-KEY header attached. The Connecting Claude Desktop, Connecting Claude Code, and Connecting Cursor articles are all concrete examples of this same pattern.
Do you need a terminal key?
For the hosted endpoint, yes — a terminal key already bound to a terminal is the only credential. See the Activating your license key article for how to generate and bind one.
Troubleshooting
- Server unreachable — verify HTTPS egress and any proxy/TLS interception rules on your network.
tools/listempty or partial — check your subscription tier and account context; tools appear based on capability.- Auth failures — confirm the
Bearerformat and that the key is valid and bound.
Next steps
New to the key concept? Read Activating your license key. Want the overview of every client option? See Connect any AI client to MetaTrader.
Get your key at mtcontext.com or browse the full setup documentation.