← wickwatch home

Model Context Protocol

Ask your AI assistant whether your trading bots are running

wickwatch has a read-only Model Context Protocol (MCP) endpoint. An AI client that speaks MCP reads the same data as the dashboard and answers questions like “Are all bots running?”, “Why did this one stop last night?” or “How much of the daily loss is used?”.

What an assistant can read

• The overview: all accounts, all instances with status, uptime and broker connection, and the current alerts
• One account with its challenge evaluation, open positions and pending orders
• One instance with its deals, the realised P&L curve and key figures such as win rate, profit factor and risk per trade
• Log lines of an instance, searched by text, time, or for problems only
• What changed on a position while it was open: stop loss, take profit, volume
• CPU, memory and disk of the host, and whether its clock is in sync
• With an admin token: the audit log and the parameter values of an instance, without values whose name looks like a secret

What it cannot do

Anything that changes something: there are no tools to start, stop, configure or trade, on purpose. Log lines, order labels and comments are written by bots and brokers and reach the model as untrusted text. A line in a log that reads like an instruction must not be able to stop a bot or close a position.

Set it up

1. In wickwatch, open the user menu → API tokens and create a token. The viewer role is enough.
2. Add the address shown on that page to your client, with the header Authorization: Bearer <token>.

With Claude Code, for example:

claude mcp add --transport http wickwatch https://wickwatch.example.com/mcp \
  --header "Authorization: Bearer ww_…"

Clients configured with JSON take the same address and header. The example, all tools with their arguments and troubleshooting are in docs/MCP.md.

Security

• The endpoint takes an API token only, never the session cookie of the web app.
• A request acts with at most the token's role; deleting the token cuts the client off at once.
• Tokens are stored only as a hash, shown once, and can expire.
• MCP=off switches the endpoint off.