Tradeics exposes multiple MCP servers so AI agents get the right tools for the job — documentation lookup, live platform operations, and AI helpers — instead of a single overloaded tool bag.
MCP (Model Context Protocol) lets hosts such as Cursor, Claude, ChatGPT, and custom agents discover tools with schemas. Each Tradeics server is independently auth’d, scoped, and versioned.
| Server | Purpose | URL (placeholder) | Status |
|---|---|---|---|
| Docs MCP | Search and read official developer docs | https://mcp.tradeics.example/docs |
Structure ready |
| Platform MCP | Live workspace: catalogs, S2P, sales, network, finance posture | https://mcp.tradeics.example/platform |
Early access |
| AI MCP | Assistive AI tools + LLM-oriented helpers | https://mcp.tradeics.example/ai |
Structure ready |
Transport for all servers: Streamable HTTP. Auth: bearer tokens from the same family as REST V2 (server-specific scopes). Pair with Agent Skills for procedural guidance.
Hostnames and path prefixes above are reserved placeholders. Keep this catalog and per-server page layout stable when production URLs go live — only replace values, not section structure.
Prefer HTTPS SDKs for high-volume backends. Prefer MCP when an agent should explore or operate under human/policy oversight.