🎛️Endpoints and toolsets
The MCP server publishes 134 tools. That is far more than most assistants handle well: a large tool list eats context, slows the model down and makes it more likely to pick the wrong tool. So the catalogue can be narrowed by the URL you connect to.
The URL
https://ai.metacopier.io[/p/{projectId}]/mcp[/x/{toolset}][/readonly]Every part in brackets is optional and they combine freely.
/mcp
The default toolsets on the project resolved from your login
/mcp/readonly
The same, with every write tool removed
/mcp/x/trading
Only the trading toolset
/mcp/x/all
All 134 tools
/mcp/x/all/readonly
Every read tool, no write tool at all
/p/{projectId}/mcp
The default toolsets on that specific project
/p/{projectId}/mcp/x/copiers/readonly
Read only copier tools on that specific project
Toolsets
accounts
25
Trading accounts, their connection state, balances, settings, groups and labels
templates
8
Account templates and their defaults
copiers
17
Copiers, their settings, symbol mappings, filters and state
strategies
10
Strategies, their members and their configuration
trading
10
Open positions, trade history, symbols, quotes, and the five tools that trade
reports
4
Performance and statistics reporting
logs
7
Account and copier logs, the first place to look when something did not fire
news
19
Economic calendar, market news, bank holidays, news filters and calendar alerts
marketplace
13
Signal marketplace, investor traders, signal performance and earnings
dashboards
5
Dashboards
webhooks
4
Webhook requests and stored webhook data
project
6
The project itself, its labels and its features
reference
4
Enum values, copier setting fields, broker servers and the connection description
docs
2
Search and read these documentation pages
Default selection
Connecting to /mcp without naming a toolset gives you:
That covers the great majority of questions people ask: what do I have, why is it not copying, what happened.
Always present
reference and docs are added to every selection and cannot be switched off. The assistant needs them to know which values a field accepts and to look things up rather than guess.
Selecting several toolsets
Name them comma separated:
Or use the header, which works on every endpoint shape:
The header wins when both are present, which is handy for a client that lets you set headers but not the URL.
An unknown name is answered with an error naming the toolsets that exist. You are told, rather than silently handed the default.
Read only endpoints
Appending /readonly removes every tool that can change anything. Only reads remain.
The same can be done with a header:
This is a good default for a first connection. Let the assistant explain your setup for a while, and add write access once you trust what it does.
Read only is applied on top of everything else. A read only endpoint with a read write key is still read only, and a read write endpoint with a read only key is still read only. The most restrictive layer always wins.
Prompts
Prompts are ready made workflows your client can offer as slash commands or buttons.
weekly-review
projectId, days
Walks through the past week of a project: what was traded, what went wrong, what is worth changing
diagnose-copier
accountId, symbol
Works out why trades are not arriving on a follower account
risk-audit
projectId
Checks a project for the gaps that turn a bad day into a blown account
onboard-account
accountId
Checks a newly added account against the accounts that already work
cost-review
projectId
Explains what the project is being charged for and where the money goes
Where an argument is optional, leaving it out means "the project of this connection".
Resources
metacopier://connection
Which project this connection works on, whether it may change anything, when it expires, and the access rules that apply
Attaching it at the start of a conversation saves the assistant from guessing, and stops it proposing a change it is not allowed to make.
Last updated