Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Connect any MCP client to MetaTrader 4/5 to read prices, manage positions, and place trades.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http mtcontext https://mcp.mtcontext.com/mcp/v1 --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mtcontext": {
"url": "https://mcp.mtcontext.com/mcp/v1",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mtcontext": {
"type": "http",
"url": "https://mcp.mtcontext.com/mcp/v1",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account mtcontext, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect Claude, Cursor, or any MCP-compatible client to a MetaTrader 4 or 5 terminal — no Python, no local server to run.
MTContext is a cloud-hosted, remote MCP server. There's nothing to clone, build, or pip install from this repo — this repo exists to document the connection and point at the real thing. (This is intentional: the server implementation itself is closed-source, cloud infrastructure, not something you run yourself.)
.ex5 for MT5, .ex4 for MT4 — MT4 support coming soon) onto a chart in your MetaTrader terminal.dry_run: true until you confirm.MTContext exposes a single remote Streamable HTTP MCP endpoint per account:
{
"mcpServers": { "mtcontext": { "type": "http", "url": "https://mcp.mtcontext.com/mcp/v1", "headers": { "Authorization": "Bearer YOUR_LICENSE_KEY" } } } }
Get your real YOUR_LICENSE_KEY from your dashboard after connecting a terminal — see examples/claude_desktop_config.example.json.
Full tool reference: docs.mtcontext.com. Setup guides and troubleshooting: help.mtcontext.com.
Several open-source MetaTrader MCP servers exist and require installing Python and running a local process yourself, usually MT5-only, with no safety layer beyond what you build. MTContext trades that developer-only setup for a one-file install, MT4 *and* MT5, and a dry-run-by-default safety model — aimed at traders, not just developers who happen to trade.
The contents of this repository (documentation and examples) are MIT licensed — see LICENSE. This does not cover the MTContext service itself, which is proprietary.