Synerixis Ops MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYNERIXIS_OPS_MCP_API_KEY | Yes | Synerixis merchant API key used by the stdio MCP server. Keys look like sxk_ plus hex. This process reads only this key and does not fall back to SYNERIXIS_API_KEY. | |
| SYNERIXIS_OPS_MCP_BASE_URL | No | Optional base URL override. Must be https on api.synerixis.com. | |
| SYNERIXIS_OPS_MCP_ALLOW_INSECURE_LOCAL | No | Optional flag required when using a local API over http://localhost or http://127.0.0.1. Set to 1 to allow insecure local base URL. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storesA | List connected stores for this merchant tenant. |
| list_conversationsB | List inbox conversations. Optional filters: storeId, status, limit, offset. storeId is a connection id or the store open id. offset is a non-negative page offset. |
| search_conversationsA | Search this merchant's conversations by order number or buyer email (q). Optional storeId/limit/offset. 按订单号或买家邮箱搜本店会话。Same summary fields as list_conversations; no secrets. |
| get_conversationC | Get one conversation detail by id. |
| list_messagesC | List messages in a conversation. offset skips from the newest page. |
| get_order_contextC | Get order / logistics context linked to a conversation (read-only). |
| list_pending_ai_repliesC | List AI draft replies awaiting confirm before send. |
| get_quotaA | Get AI resolve-point balance for this merchant. |
| list_agentsA | List this merchant's agents/seats (id, displayName, isActive/isAvailable) for assign_conversation. 列出本店坐席（id、显示名、是否可用），供分派会话选用。Does not expose secrets or emails. |
| save_draftA | Save or update a draft reply on a conversation. Does not send. |
| send_messageA | Send a reply. Destructive: the host must approve the call. confirm must already be true; this client never sets it. Audited on Synerixis. Same idempotencyKey retries the same send. |
| approve_ai_replyB | Approve one pending AI draft and send it. Pass draftId when more than one draft is waiting. Host must approve. confirm is not set by this client. |
| reject_ai_replyB | Discard one pending AI draft. Does not discard other drafts. Host must approve. Reason is stored on the audit row. |
| assign_conversationA | Assign a conversation to an agent. Call list_agents first for assigneeId. 先 list_agents 取坐席 id。Sends agentId (assigneeId is the same value). Host must approve. |
| update_conversation_statusA | Set conversation status to resolved, reopen, or closed. Host must approve. open is not a write value. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes: conversation listing/reading, message sending, AI draft approval/rejection, assignment, and status updates are separable. The main overlap is list_conversations vs search_conversations, which both return similar summary fields and differ mainly by the optional q filter, so an agent could occasionally choose the wrong one.
All tool names use consistent snake_case with predictable verb_noun structure, such as list_conversations, get_conversation, save_draft, send_message, and approve_ai_reply. No mixed conventions or vague names are present.
Fifteen tools is well-scoped for an operations inbox server covering stores, conversations, messages, AI drafts, agents, quota, and order context. Each tool appears to earn its place without excessive surface area.
The surface covers the core lifecycle: list/search/read conversations, read messages, inspect order context, save/send replies, manage AI drafts, assign conversations, and update status. Minor gaps exist around broader agent/store management and possible read-state handling, but these are not fatal for the stated ops purpose.