Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Read-only MetaTrader 4 and 5 accounts: balances, positions, trade history, quotes and candles.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
FXSOCKET_API_KEY, X-API-Key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"fxsocket": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"FXSOCKET_API_KEY",
"docker.io/fxsocket/mcp:1.0.1"
],
"env": {
"FXSOCKET_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http fxsocket https://mcp.fxsocket.com/mcp --header 'X-API-Key: your-value'claude mcp add fxsocket --env FXSOCKET_API_KEY=your-value -- docker run -i --rm -e FXSOCKET_API_KEY docker.io/fxsocket/mcp:1.0.1运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fxsocket": {
"url": "https://mcp.fxsocket.com/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"fxsocket": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"FXSOCKET_API_KEY",
"docker.io/fxsocket/mcp:1.0.1"
],
"env": {
"FXSOCKET_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fxsocket": {
"type": "http",
"url": "https://mcp.fxsocket.com/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"fxsocket": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"FXSOCKET_API_KEY",
"docker.io/fxsocket/mcp:1.0.1"
],
"env": {
"FXSOCKET_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
X-API-Key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 fxsocket.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:FXSOCKET_API_KEY, X-API-Key
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.0.1)于19天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Lets Claude, Cursor, VS Code and other MCP clients read your MetaTrader 4 and 5 accounts on FxSocket: balances, open positions, closed trades with win rate and P/L, quotes, symbol specifications and price history. It is read-only. It cannot place, modify or close orders.
This image runs FxSocket's MCP server as a local stdio server, for clients that start their servers themselves (Claude Desktop, Docker's MCP Toolkit, or anything configured with a command). It relays each message to https://mcp.fxsocket.com/mcp with your API key. The tools run on FxSocket, next to the terminals your accounts are connected to, so the image stays tiny and never needs updating when tools change.
If your client takes a remote server URL plus a header, you can skip the image: point it at https://mcp.fxsocket.com/mcp with your key in an X-API-Key header.
Create a read-only key (fxs_ro_...) at app.fxsocket.com/dashboard/api-key. A named key scoped to some of your accounts limits the agent to exactly those. A full fxs_live_... key works too, but an agent has no use for one.
Claude Desktop (Settings, Developer, Edit Config, then restart):
{
"mcpServers": { "fxsocket": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "FXSOCKET_API_KEY", "fxsocket/mcp"], "env": { "FXSOCKET_API_KEY": "fxs_ro_..." } } } }
Claude Code:
claude mcp add fxsocket -e FXSOCKET_API_KEY=fxs_ro_... -- docker run -i --rm -e FXSOCKET_API_KEY fxsocket/mcp
Cursor (~/.cursor/mcp.json):
{
"mcpServers": { "fxsocket": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "FXSOCKET_API_KEY", "fxsocket/mcp"], "env": { "FXSOCKET_API_KEY": "fxs_ro_..." } } } }
VS Code (.vscode/mcp.json, prompts for the key once):
{
"inputs": [ { "type": "promptString", "id": "fxsocket-key", "description": "FxSocket API key", "password": true } ], "servers": { "fxsocket": { "type": "stdio", "command": "docker", "args": ["run", "-i", "--rm", "-e", "FXSOCKET_API_KEY", "fxsocket/mcp"], "env": { "FXSOCKET_API_KEY": "${input:fxsocket-key}" } } } }
-e FXSOCKET_API_KEY without a value passes the variable through from the client's env, so the key never appears in the process list.
Without Docker: the relay is one file with no dependencies. Download fxsocket_mcp.py and use python3 (3.10 or newer) as the command with the file's path as the argument, keeping the same env.
| Tool | What it answers |
|---|---|
list_accounts | Every account the key can see, optionally with balance, equity and totals per currency. Call first. |
get_account | One account in full: summary, broker info and terminal status. |
get_open_positions | Open positions and pending orders across accounts, with floating P/L and swap. |
get_trade_history | Closed trades for a period, with wins, losses, win rate, net P/L and a per-symbol breakdown. |
search_symbols | Find the broker's exact symbol name (EURUSD, EURUSD.sd, EURUSDm...). |
get_quotes | Live bid/ask and spread for up to 20 symbols. |
get_symbol_info | Contract specification: digits, contract size, volume limits, swaps, sessions. |
get_price_history | OHLC candles for a symbol and timeframe. |
Amounts are in each account's deposit currency and are never summed across currencies. Times are broker server time.
| Variable | Default | |
|---|---|---|
FXSOCKET_API_KEY | (required) | Your FxSocket API key. |
FXSOCKET_MCP_URL | https://mcp.fxsocket.com/mcp | The server to relay to. Plain http is only allowed to localhost. |
FXSOCKET_MCP_TIMEOUT | 120 | Seconds to wait for one reply. |
FXSOCKET_MCP_LOG | info | error, warning, info or debug. Logs go to stderr. |
FxSocket allows 60 MCP requests a minute per user.
The client writes newline-delimited JSON-RPC to the container's stdin. The relay POSTs each message to the MCP endpoint over a kept-alive HTTPS connection, adds the API key and the headers the protocol requires, and writes the replies to stdout. It handles both protocol eras:
_meta, and the relay mirrors it into the MCP-Protocol-Version, Mcp-Method and Mcp-Name headers (plus any x-mcp-header tool parameters).initialize, and the relay sends the negotiated version as MCP-Protocol-Version from then on.If FxSocket rejects the key, the relay still answers initialize and tools/list from the server's public card (https://mcp.fxsocket.com/.well-known/mcp/server-card.json), so directories and inspectors that start it with a placeholder key can see the tools. Every tool call still needs a valid key and otherwise returns the rejection.
Requests run concurrently. A notifications/cancelled from the client closes that request's connection, which is how Streamable HTTP cancels. HTTP failures (bad key, rate limit, network) come back as JSON-RPC errors with a sentence saying what to fix, rather than a hung client.
python3 -m unittest discover -s tests
docker build -t fxsocket/mcp:dev .
The tests start the relay as a subprocess against a local stub server, so they cover the real stdio and HTTP paths.
To release, bump __version__ in fxsocket_mcp.py, then push a matching tag (git tag v1.0.1 && git push --tags). The publish workflow builds linux/amd64 and linux/arm64 and pushes fxsocket/mcp: , : . and :latest, and the dockerhub-overview workflow copies this README to the Docker Hub page.
MIT