Desk by Ouroboros Apps MCP server — tools & history
Desk by Ouroboros Apps MCP server: observed open status, tool schemas, linked apps and version history.
Desk by Ouroboros Apps
Endpoint: https://desk-mcp-continuity2.vercel.app/mcp
Observed status: open. Checked: 2026-10-12T05:11:12+00:00.
Linked apps
- Desk by Ouroboros Apps
I built Desk so Cursor and other MCP clients answer support tickets only from your approved answers, refund rules and escalation limits. For support and customer-success teams. MCP URL: https://desk-mcp-continuity2.vercel.app/mcp. More at https://ouroborosapps.com.
Observed tools
- create_support_desk — Create a support desk when the user asks for a new policy home. Does not approve answers, refunds, features, or timelines.
- evaluate_commitment — Decide whether a proposed refund, feature, or timeline is in the approved set. REFUSED means do not say it, do not invent a substitute, and draft for human review instead of promising the customer. APPROVED means sayOnly is the only permitted wording. Pass channel to also enforce the escalation limit.
- evaluate_escalation — Decide whether this channel may escalate or may promise a refund, feature, or timeline. REFUSED means do not escalate, do not invent a tier, and draft for human review instead of promising the customer. Permission to promise still requires evaluate_commitment for the exact wording.
- get_desk_context — Retrieve selected approved answers for a customer question, plus the desk's approved refund rules, commitments, and escalation limits. This is evidence, not permission. A missing or RETIRED answer is not an invitation to invent one. Call evaluate_commitment before promising a refund, feature, or timeline. If tools fail or return gaps or REFUSED, draft for human review instead of promising the customer.
- list_approved_commitments — Read approved feature and timeline statements. Listing them does not approve a different promise. Call evaluate_commitment with the exact wording before saying one.
- list_escalation_limits — Read escalation limits. A channel with no APPROVED limit cannot promise a refund, feature, or timeline and cannot be given an invented escalation path.
- list_refund_rules — Read refund rules on a desk. Only APPROVED rules can authorize wording, and only through evaluate_commitment. Do not treat this list as permission to invent a refund.
- list_support_desks — List this team's support desks. Use the returned id. Do not guess a desk.
- save_approved_answer — Store or revise an answer the user has explicitly approved. Identical retries keep the same revision. A changed answer requires expectedRevision from a previous read.
- save_approved_commitment — Store a feature or timeline statement the user has explicitly approved. The statement is the only wording that can later pass evaluate_commitment. Do not save a date or a feature the user did not approve.
- save_escalation_limit — Store the escalation limit the user has explicitly approved for one channel. maxTier must be on tierLadder. Promise flags default closed unless the user sets them true. A limit does not itself approve refund, feature, or timeline wording.
- save_refund_rule — Store a refund rule the user has explicitly approved. matchTerms must name a specific situation. The word refund alone is not a rule. remedy is the only wording that may later be approved. decision ALLOW grants that wording. decision DENY refuses a refund and records the denial script.
- search_approved_answers — Look up approved answers by topic, question, or answer text. An empty result means there is no approved answer. Draft for human review; do not invent one or promise the customer. Page with offset.
Data as of 2026-10-12T05:11:12+00:00.
OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.
REST API specification · Guide for AI clients · Manage API keys and MCP connections