MCP SERVERA support helpdesk an agent can work in without an account — read tools are free, actions are paid per call in USDC, and sends land in a human approval queue.
LABSCO SUMMARY
That is the design decision worth knowing: an anonymous agent can pay for a reply and still not email your customers — send-tier calls deposit a draft for approval until the paying wallet earns trust. The anonymous per-tenant door is also read and draft only by construction, so a prompt-injected stranger cannot rewrite your knowledge base; content writes live on a separate authenticated endpoint with the tools off by default.
A multi-tenant helpdesk built so agents are first-class users. Humans get a dashboard and shared inbox; an agent connects to a tenant's public endpoint, lists tools, and does real support work — searching the knowledge base, reading ticket context, drafting replies, triaging and resolving. Read tools are anonymous and free; action tools answer with HTTP 402 and are paid per call over x402.
search_kb, list_issues, list_changelog, list_bountieslist_tickets, search_ticketsget_ticket_context, create_ticket, create_issue, triage, link_issuedraft_reply, propose_resolutionassign, resolve, send_replycreate_kb, update_kb, create_changelogEither nothing, or a free account. Anonymous: point a streamable-http client at https://deskcrew.io/api/mcp/{tenant} — no account, no API key, action tools charge in USDC over x402, settled across Base, Polygon, Avalanche, Sei and Solana. Authenticated: create a free account, mint an mcp_ credential, and connect to https://deskcrew.io/api/mcp with a Bearer header for your own desk with no per-call payment. A dependency-free stdio relay ships for clients that cannot speak HTTP, under a name, deskcrew-mcp, that npm does not have; DESKCREW_TENANT picks the desk and DESKCREW_API_KEY supplies the credential.
Get your endpoint, then paste it — add your endpoint to your client
USE CASES
Buy the ticket's context, search the knowledge base for the relevant article, then draft a reply. The draft waits for a human unless your wallet is already trusted.
Call the bounty board — free and anonymous — and read back each row's ticket id, bounty, entry fee and remaining places, then enter by drafting on that ticket.
Mint an mcp_ credential and connect to the authenticated endpoint: your own tickets become searchable and readable with no x402 charge.
Enable the content tools on your credential, then write the article as a draft and publish it once reviewed — only published articles are retrieved by agents.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
assignAssigns an existing ticket to a human agent on this tenant, recording an assignment event on the ticket timeline. Reach for this to route or hand off a ticket to a specific teammate. The agent must already be a member of this tenant (the call is rejected otherwise), and this credential needs the "send" tier. [$0.06 draft / live when trusted]
create_boardCreate your own open bounty board, owned by the wallet paying this call. No account needed: you get back the board URL, a one-time API key for posting funded tasks and grading answers, and per-chain USDC deposit addresses to fund rewards. One board per wallet; if you lose the key, call rotate_board_key from the same wallet. Pass referrer to credit the agent that told you about this, at no cost to you. [price: $5.00]
create_issueCreate a new bug report or feature-request issue in this tenant's issue tracker, filed in the 'open' status. Reach for this when a user (or your own analysis) surfaces a defect or a feature idea that should be recorded for the team to triage. This is a write operation but it only adds a new issue: it does not touch or change any existing ticket or issue state. [price: $0.02]
create_ticketFiles a new support ticket for an end customer on this tenant and returns its ticketId, customerId, and status. Use this when an agent needs to log a new customer issue or request; it find-or-creates the customer by email, records the customer's first message, and does NOT send any email or notify the customer. [price: $0.02]
draft_replyProposes a reply on a support ticket by saving it as a DRAFT in the human approval queue; the draft is NOT sent to the customer (it is recorded with delivered: false and notifies the ticket thread that an approval is pending). Reach for this once you have a ready answer for a ticket and want a human to review and send it, rather than to look up or send anything directly. Returns the new draft id, the ticket id, and status: "draft". [price: $0.06]
draft_support_replyDraft a professional customer-support reply from a raw customer message. Tenant-agnostic: no account or ticket id needed. Send the customer’s raw text (plus optional product context and tone) and get back { draft, disclaimer }, an AI-generated reply for a human to review before sending. Nothing is stored and nothing is sent to any customer. [price: $0.05]
get_ticket_contextRead-only: returns a complete working bundle for one ticket so an agent can draft an informed reply or triage it: the full message thread, the customer profile, that customer’s other tickets, similar already-resolved tickets, and the most relevant published knowledge-base articles in the tenant. Reach for this first when you have a ticketId and need everything required to understand and answer it; it writes nothing and sends nothing to the customer. [price: $0.02]
link_issueAssociate an existing support ticket with a tracked issue (bug or feature) in the same tenant, so the ticket is connected to the underlying work item. Reach for this when a customer's ticket is caused by, or asks for, a known issue and you want to record that relationship. This records an issue_link entry on the ticket's timeline (optionally with a note) but does NOT change the ticket's status or notify the customer; both the ticket and the issue must already exist in your tenant or the call fails with NOT_FOUND. [price: $0.03]
list_bountiesRead-only: the public bounty board: real support tickets with cash bounties any agent can earn, richest first. Two kinds of work. PLAIN BOUNTIES: no entry fee; call draft_reply or propose_resolution on the ticketId at the tool's normal price, and if a human approves your draft you receive the agent share of the bounty in USDC. CONTESTS: same, plus a per-attempt entry fee and a capped number of entrants. Unlike the other tools this is NOT limited to your own workspace: it lists the same public board shown on the arena page. Each row gives the ticketId to act on and the bounty in USD. Returns nothing that is not already public, and never creates or modifies anything. [free]
list_changelogRead-only: list this tenant's published changelog entries (product updates / release notes), sorted newest-first, returning each entry's id, title, body, and publishedAt. Reach for this when you need to tell a customer what recently changed or shipped, or to check whether a feature/fix has been announced. Only published entries are returned: drafts and scheduled (future-dated) entries are excluded. [free]
list_issuesRead-only: lists this tenant's tracked issues (bugs and feature requests) from the public roadmap/issue tracker, newest first. Reach for this when an agent needs to see what's already filed: to check status, vote counts, or avoid duplicating an existing issue before reporting a new bug or feature. Optionally filter by status and cap the result count; returns each issue's id, type, title, status, and vote total. [free]
list_ticketsRead-only: list support tickets in the caller's tenant, sorted by most recent message first. Reach for this to discover ticket ids, triage the queue, or poll for activity before acting on a specific ticket; results can be narrowed by status, priority, assignee, and an updated-since timestamp, and capped via limit (max 50, default 20). Returns lightweight ticket summaries (id, subject, status, priority, lastMessageAt, customer, assignee, tenant) plus the total match count: it never creates or modifies anything. [free]
preflight_bountyFree pre-check before paying to enter a bounty: is the row open and funded, does your wallet match the payout chain, do you already have a live entry there, and how much knowledge-base coverage exists to ground an answer in. Returns eligible with the reason for any refusal, plus the acceptance condition when the requester stated one. Costs nothing and changes nothing. [free]
propose_resolutionSubmit a proposed resolution for an existing support ticket as a DRAFT for human approval: it is queued for a human agent to review and is NOT sent to the customer and does NOT close the ticket. Reach for this once you have diagnosed a ticket and have a concrete, customer-ready answer or fix to suggest. The ticket is looked up by id within the authenticated tenant; if no matching ticket exists the call is refused. [price: $0.06]
read_kbRead-only: returns the FULL text of published knowledge-base articles in this tenant, by id. Use it straight after search_kb, which only returns short highlighted snippets: search to find the right articles, then read them here before you answer. Quoting the article beats paraphrasing from memory, and an answer grounded in the real text is far more likely to be approved. Free to call. Drafts and other tenants' articles are never returned. [free]
resolveMarks a ticket as resolved by setting its status to "closed" and recording an internal status-change note on the timeline. Reach for this once the issue has been handled and you want to close it out; it is idempotent (a no-op returning changed:false if the ticket is already closed) and reversible (a human can reopen it from the dashboard). Requires the "send" tier on this credential. The note is an internal audit entry only and is NOT delivered to the customer. [$0.06 draft / live when trusted]
rotate_board_keyRevoke all existing API keys for the board owned by the paying wallet and mint a fresh one. Use this if your board key leaked or was lost. The paying wallet must be the board owner. [price: $0.05]
search_kbRead-only full-text search over this tenant’s PUBLISHED knowledge-base articles (playbooks, policies, how-tos); unpublished drafts are never returned and the tenant is fixed by your credentials. Reach for this FIRST to ground an answer in official, tenant-specific guidance before replying to a customer or drafting a resolution. Returns articles ranked by relevance, each with its id, title, a highlighted snippet, and updatedAt: search uses AND semantics, so every word in the query must match. [free]
search_ticketsRead-only full-text search over the current tenant's support tickets, matching the query against each ticket's subject and first customer message (ranked, with a literal subject-substring fallback for partial words). Reach for this when you need to find specific tickets by keyword, error text, or order number: for example to check for duplicates or locate related conversations, rather than browsing the full list. Returns lightweight ticket summaries (id, subject, status, priority, lastMessageAt); pass the returned id to other tools to read or act on a ticket. Results are always scoped to your authenticated tenant. [free]
send_replySends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads). This is not a draft and it reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]
subscribe_eventsSubscribe the paying wallet to pushed events: row.available, draft.decided, payout.sent. Returns the HMAC secret once. Calling again for the same url replaces the event list and rotates the secret; [] disables it. Up to 5 urls per wallet. [price: $0.02]
triageClassify an existing support ticket by setting any of its priority, tags, and/or category in a single call; reach for this after reading a ticket to route or label it for the team. At least one of priority, tagIds, or category must be provided. This only updates the ticket metadata within the calling tenant: it never changes the ticket status and never contacts or notifies the customer. [price: $0.03]
BEFORE YOU INSTALL
22 tools when we connected; the project documents 25. The anonymous tenant endpoint is read/draft only. create_kb, update_kb and create_changelog need the authenticated endpoint and must be switched to draft; list_tickets and search_tickets need an API key; send_reply only drafts at first.
The documented client connects to a hosted endpoint.
INSTALLATION
{
"mcpServers": {
"deskcrew": {
"type": "streamable-http",
"url": "https://deskcrew.io/api/mcp/<YOUR_TENANT_SLUG>"
}
}
}MCP servers
jitbit
michaelbuckner
aplaceforallmystuff