MCP server

Connect ShowMyTrades to Claude, ChatGPT or any MCP client. Search verified public track records and compose widgets with no key; add a free key to ask about your own accounts.

The same data as the REST API, exposed so an AI assistant can use it on its own.

You connect ShowMyTrades once, then ask questions in plain language:

"Find verified accounts with over a year of history that never dropped more than 10%.""How has this account done month by month?""Give me the code to put this account's growth chart on my site.""How did my Weltrade account do in August?" (with a key)

The assistant works out which calls to make. You do not write any code.

REST or MCP? Same data, same permissions: the difference is who reads the instructions. With the REST API you read this documentation and write the code. With MCP the model reads the tool descriptions, every conversation, and decides what to call. Use REST for a script or a dashboard; use MCP to ask questions.

Endpoint

https://showmytrades.com/api/v1/mcp

Streamable HTTP, stateless, protocol version 2025-06-18.

Two modes: without a key, with a key

	Without a key	With a free Developer API Key
Search accounts traders have published	yes	yes
Read one published account, every section	yes	yes
Compose the embed widget for an account	yes	yes
Your own accounts and portfolios, private ones included	no	yes
Your closed trades and open positions	no	yes
Attribution	required	required (Pro and Ultra: recommended)
Requests per minute	20 per IP address	30 per key, 120 on Pro and Ultra

Without a key the server works for anyone, including people who have no ShowMyTrades account: that is what lets an assistant answer a question about public track records on the spot. A key is created in Settings → Developer API Keys and sent as the same Authorization: Bearer header as the REST API.

Connecting

Claude Desktop

Add this to your claude_desktop_config.json, then restart Claude. Without a key:

claude_desktop_config.json

{
  "mcpServers": {
    "showmytrades": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://showmytrades.com/api/v1/mcp"]
    }
  }
}

With a key, so that your own accounts are included:

claude_desktop_config.json

{
  "mcpServers": {
    "showmytrades": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://showmytrades.com/api/v1/mcp",
        "--header", "Authorization: Bearer smt_live_YOUR_KEY"
      ]
    }
  }
}

Claude.ai, ChatGPT and other clients

Any client that accepts a remote MCP server (sometimes called a custom connector) needs only the URL above. In Claude.ai it is Settings → Connectors → Add custom connector; in ChatGPT, Settings → Connectors with developer mode on. Where the client lets you add an HTTP header, add Authorization: Bearer smt_live_YOUR_KEY to include your own accounts; without the header the public tools are available straight away.

Claude Code

claude mcp add --transport http showmytrades https://showmytrades.com/api/v1/mcp

Add --header "Authorization: Bearer smt_live_YOUR_KEY" for your own accounts.

The tools

search_public_accounts

Search accounts traders have published: free text, platform, verified only, minimum return, maximum drawdown, minimum history, sort order. Each result carries its own attribution with the account's page. No key needed.

get_account

One account with its headline performance. Optional heavier sections: equity curve, monthly returns, per-instrument and per-strategy breakdowns, advanced statistics. Without a key it reads published accounts; with a key, your own too. No key needed for published accounts.

get_widget_snippet

The ready-to-paste embed code for an account: an interactive iframe widget or a self-updating image, with the URL, the HTML (plus Markdown and BBCode for images), the size and the list of the other types. See the widget reference. No key needed for published accounts.

list_my_accounts

Your accounts and portfolios, private ones included. This is where the assistant gets the slug of your own accounts. Key required.

list_trades

Closed trades of one of your accounts, with an optional date range. Key required.

list_open_positions

Positions currently open on one of your accounts, with their floating profit. Key required.

The assistant only sees the tools it can use: without a key, the first three; with a key, the ones its scopes allow. At connection time the server also hands the model a short description of what it is and what it is not, so it does not need to guess.

What it can and cannot do

The MCP server is read-only, like the rest of the API. No tool can rename, publish or delete anything, and none can place or close a trade. Whatever you ask, the assistant can only read.

It also cannot look up people. It searches accounts; of an owner it sees a public slug and brand name, never a personal name, email or contact detail. And a search result is not a ranking endorsed by ShowMyTrades: it is what the filters matched.

Things worth knowing

It sees what you see

Your own accounts come through unfiltered. Accounts belonging to other people arrive with whatever their owner chose to hide already removed: the assistant will simply find those fields empty.

Ask for a summary, not for everything

"Summarise my year" is answered from monthly returns in one call. Asking the assistant to page through several thousand trades is slower and no more accurate.

Check the units in the answer

The tools tell the model that percentages are in percent and drawdown is positive. If an answer looks off by a factor of 100, say so: models do occasionally reformat numbers.

It credits the source

When the assistant builds a chart, a page or a report from the data, it adds the line Data from ShowMyTrades with a link. Without a key and on the free plan that credit is required; on Pro and Ultra you can ask the assistant to leave it out.

Treat it as a reader, not an oracle

It reports what an account did. It does not know anyone's intentions, risk limits or what happens next, and a good track record is not a promise.

Search across every account published on ShowMyTrades.

Errors

Status codes, the error shape, and what to do about each one.