MCP servers use the same bearer-token family as REST API V2. Scopes decide which servers and tools a token may call.
Obtain a token
Until Tradeics Platform ships self-serve developer settings:
- Create a Tradeics account at tradeics.example/get-started.
- Request early API / MCP access from support or your account manager.
- Store the token in a secrets manager — never in skill files or shared prompts.
When self-serve lands, expect Tradeics Platform → Developer → MCP with per-server enablement and scopes (same family as REST keys). Regenerating a workspace key may invalidate REST and MCP — coordinate with your team.
Send credentials
Preferred:
Authorization: Bearer <TRADEICS_MCP_TOKEN>Fallback (hosts without custom headers):
https://mcp.tradeics.example/<server>/?token=<URL_ENCODED_TOKEN>Scopes model (structure)
| Scope pattern (placeholder) | Intended server | Notes |
|---|---|---|
docs:read |
Docs MCP | Default for documentation agents |
platform:read / platform:write |
Platform MCP | Split read vs write |
ai:write |
AI MCP | Assistive invocations |
| Product REST scopes | Platform tools | Align with REST groups (master:read, s2p:write, …) |
Exact scope strings finalize with GA — keep this table’s rows; replace names when shipping.
Environments
| Environment | Use |
|---|---|
| Staging MCP | Experiment with write tools |
| Production MCP | Operator-supervised automation |
See Versioning & environments.