Platform MCP exposes live Tradeics workspace tools — master data, marketplace, source-to-pay, sales, network, and finance posture — backed by REST API V2 under your token’s scopes.
Pair with the Tradeics Platform skill and Tradeics API skill.
Connection
| Field | Value (placeholder) |
|---|---|
| Transport | Streamable HTTP |
| URL | https://mcp.tradeics.example/platform |
| Auth | Bearer token with platform:read / platform:write (+ product scopes) |
Transition URL: https://api.tradeics.example/mcp/ (treat as Platform until per-server hosts cut over).
Tool surface (structure)
Group tools to mirror REST / docs IA. Fill concrete ids at GA:
| Domain | Example tools (placeholder) | REST anchors |
|---|---|---|
| Master / catalogs | list_vendors, get_item, list_vendor_categories |
Master Data |
| Marketplace | list_catalogs, list_products, get_product |
Marketplace |
| B2B E-store | list_stores, get_cart, create_store_order |
B2B E-store |
| Source to Pay | list_rfx, get_rfx, create_rfx_draft, list_purchase_orders |
S2P |
| Sales | list_opportunities, list_quotes |
Sales |
| Network | list_partners, get_partner |
Network |
| Finance posture | list_payments, list_invoices, list_wallets |
Finance |
| Webhooks / account | list_webhook_subscriptions, get_organization |
Webhooks / Account |
Safety defaults
- Prefer list/get before create/update.
- Require operator confirmation for writes unless policy auto-approves.
- Never invent tool arguments outside schema.
Write tools can affect live commercial workflows. Use staging credentials while developing agent prompts.
Example prompts
- “List vendor sub-categories, then propose a sync plan for our PIM.”
- “Summarize open RFXs — read only.”
- “Draft (do not submit) an RFX create payload and wait for my OK.”
Page sections to fill at GA
- Full tool catalog with schemas
- Scope matrix per tool
- Idempotency keys for mutating tools
- Pagination parameters