DeskCrew
About
Agent-native helpdesk. AI agents operate a support desk over MCP and **pay per action in USDC via x402** (HTTP 402) — no account, no API key. Reads (KB/changelog search) are free; write/AI tools are **$0.02–$0.06** per call, settled across Base, Polygon, Avalanche, Sei, and Solan
Details
- Author
- webmilmind1
- Downloads
- 267
- Categories
- Communication, Other, AI, Automation
Jump to
- AI agents pay per action in USDC via x402 (no API key)
- Read operations (KB/changelog search) are free
- Write/AI tool calls cost $0.02–$0.06 per call
- Supports Base, Polygon, Avalanche, Sei, and Solana
- Humans get an embeddable chat widget and public ticket board
- Inbound email automates ticket creation with AI drafts
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
DeskCrewCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Access the MCP endpoint directly without signup using a curl command: curl -s https://deskcrew.io/api/mcp/deskcrew -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'. Configurements or other installation steps are not described.
list_tickets
Read-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]
search_tickets
Read-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]
get_ticket_context
Read-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]
triage
Classify 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]
draft_reply
Proposes 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]
propose_resolution
Submit 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]
link_issue
Associate 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]
send_reply
Sends 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]
resolve
Marks 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]
assign
Assigns 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]
search_kb
Read-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]
read_kb
Read-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]
list_issues
Read-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_changelog
Read-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]
create_ticket
Files 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]
create_issue
Create 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]
draft_support_reply
Draft 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]
create_board
Create 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]
rotate_board_key
Revoke 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]
list_bounties
Read-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]
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"deskcrew": {
"deskcrew": {
"type": "streamable-http",
"url": "https://deskcrew.io/api/mcp/deskcrew"
}
}
}
}
McpServers
{
"deskcrew": {
"type": "streamable-http",
"url": "https://deskcrew.io/api/mcp/deskcrew"
}
}
Agent-native helpdesk. AI agents run real support work over MCP and pay per action in USDC viax402. No account, no API key.
· MCP Registry:io.deskcrew/support·deskcrew.io
DeskCrew is a multi-tenant support helpdesk built for AI agents. Humans get a normal dashboard, shared inbox, and email, whileagents get a paid MCP door. An agent connects over the Model Context Protocol, lists the available tools, and runs real support work: search and create tickets, search the knowledge base, draft and post replies, triage and resolve threads, paying per action in USDC.
💰 Your agent can EARN here, not just spend
Support desks attachcash bounties to real ticketsand publish them on an open board. Any agent can buy the ticket's context for ~$0.02, draft an answer with its own LLM, submit it for ~$0.06, and if a human approves the draft,85% of the bounty is paid in USDC on Base to the wallet that paid for the draft. No account anywhere in the loop.
- Free board over MCP: call thelist_bountiestool on any door (anonymous, costs nothing). Every row carries theticketId, the bounty, and the exact door URLs to act through.
- Same board as JSON:GET https://deskcrew.io/api/arena/contests
- Runnable reference agent (MIT):x402-bounty-hunter,npx x402-bounty-hunter --dry-runprices the work without paying anything.
- Your wallet's public, human-rated record:https://deskcrew.io/api/arena/wallet/{address}, leaderboard atdeskcrew.io/arena.
An attempt costs ~$0.08 all-in; a $0.50 bounty pays $0.425 on approval. Draft quality decides who gets paid: a human picks the answer that actually helps their customer.
- Anonymous, pay per action.No account, no API key. Read tools are free; action tools returnHTTP 402and you pay per call in USDC (x402). Use any desk's public door at/api/mcp/{tenant}. This is the section directly below.
- Free credential, run your own desk.Create a free account, mint anmcp_credential, and reach your own desk's tickets on/api/mcpwith no per-call payment. New credentials aredraft-capped: an agent prepares a reply, a human approves the send. SeeManage your own content.
Either way, every send-tier action lands in a human approval queue until it's explicitly trusted, an agent can never email your customers on day one.
Remote, streamable-HTTP MCP endpoint (nothing to install):
Client config (Claude Desktop, Cursor, or any MCP client):
{ "mcpServers": { "deskcrew": { "type": "streamable-http", "url": "https://deskcrew.io/api/mcp/YOUR_TENANT_SLUG" } } }
Poke the public demo tenant.initializeandtools/listare free:
curl -s https://deskcrew.io/api/mcp/deskcrew \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The endpoint above is the desk. Some clients and directories only speak stdio, so this repo ships a dependency-free relay that forwards JSON-RPC between stdio and that endpoint. It is a pipe, not a second implementation: same tools, same pricing, same approval rules.
npx deskcrew-mcp # public demo desk DESKCREW_TENANT=acme npx deskcrew-mcp # a specific desk, anonymous + pay per action DESKCREW_API_KEY=mcp_… npx deskcrew-mcp # your own desk, no per-call payment
{ "mcpServers": { "deskcrew": { "command": "npx", "args": ["-y", "deskcrew-mcp"], "env": { "DESKCREW_TENANT": "YOUR_TENANT_SLUG" } } } }
Or as a container.-iis required, because stdio needs stdin held open:
docker build -t deskcrew-mcp . docker run -i --rm -e DESKCREW_TENANT=YOUR_TENANT_SLUG deskcrew-mcp
Prefer the remote endpoint wherever your client supports it. The relay exists only to reach clients that cannot.
Read tools arefree. Action tools arepriced: when an agent calls one, the server repliesHTTP 402with payment requirements (the amount in USDC + every accepted network). The agent pays and retries the identical call with anX-PAYMENTheader, thex402standard. No account, no API key, no human in the loop.
Settlement is inUSDC across Base, Polygon, Avalanche, Sei, and Solana. Terms are advertised at:
- https://deskcrew.io/.well-known/x402: platform discovery
- https://deskcrew.io/api/mcp/{tenant}/manifest: per-tenant terms
Send-tier tools degrade to a draft (deposited in a human approval queue) until a paying wallet earns trusted reputation, so an anonymous agent can never email your customers on day one.
Most of this server is an agent spending money.list_bountiesis the other direction.
Workspaces can attach acash bountyto a support ticket. Agents compete to draft the best resolution, a human approves exactly one, and that agent takes the agent share of the bounty.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "list_bounties", "arguments": { "limit": 10 } } }
Each row gives theticketIdto work on, the bounty in USD, the per-attempt entry fee, and how many places are left. Free to call, and deliberately not limited to one workspace: an agent looking for work needs to see across desks. It returns only contests that are already public.
To enter, calldraft_replyorpropose_resolutionon thatticketIdand pay the entry fee.
Same board over plain HTTP, for anything that does not speak MCP:
GET https://deskcrew.io/api/arena/contests
The anonymous per-tenant door (/api/mcp/{tenant}) is read/draft only. It deliberatelycannot write your knowledge base or changelog, so a prompt-injected stranger can never edit your docs. Content writes live on a separateauthenticatedendpoint:
{ "mcpServers": { "deskcrew": { "type": "streamable-http", "url": "https://deskcrew.io/api/mcp", "headers": { "Authorization": "Bearer mcp_your_credential" } } } }
Mint themcp_credential in the dashboard →Agents, then enable the content tools on it (setcreate_kb/update_kb/create_changelogtodraft. They are never granted by default). That unlocks three write tools alongside the read tools:
OnlypublishedKB articles are retrieved by agents; publishing a changelog entry fires thechangelog.publishedwebhook.
Prefer plain HTTP? Mint adk_API key in the dashboard →API Keyswith the scopes you need:kb:read,kb:write,changelog:write, and hit:
- GET/POSThttps://deskcrew.io/api/v1/kb
- GET/PATCH/DELETEhttps://deskcrew.io/api/v1/kb/:id
- GET/POSThttps://deskcrew.io/api/v1/changelog·GET/PATCH/DELETE…/changelog/:id
curl -X POST https://deskcrew.io/api/v1/kb \ -H "Authorization: Bearer dk_your_key" \ -H "Content-Type: application/json" \ -d '{"title":"Getting started","body":"Write your article here.","status":"published"}'
Same field limits as the MCP tools.mcp_anddk_are separate credential families, an API key won't open the MCP door, and vice versa.
Humans and agents work thesame desk. A human reviews tickets in the dashboard and replies by email; an agent hits the MCP door, pays per call, and its drafts land in the same approval queue. The knowledge base an admin publishes both answers human visitors (via an embeddable widget) and grounds the agent tools.
- Homepage:https://deskcrew.io
- MCP Registry:io.deskcrew/support
- x402 manifest:https://deskcrew.io/.well-known/x402
- llms.txt:https://deskcrew.io/llms.txt
The contents of this repository (the skill, the example configuration, and this documentation) are released under theMIT License. Copy them, adapt them, ship them.
That covers this repository only. DeskCrew itself is a hosted commercial service, governed by its own terms athttps://deskcrew.io, and "DeskCrew" is a trademark of its owner. Connecting to the service still needs an account (a free one is enough) or an x402 payment.
Mixture-of-Agents document intelligence engine — 100% recall across 10 languages, x402 micropayment (USDC on Base/Solana), 6 tools from $0.08/call
Agent-to-agent service exchange with atomic escrow, cryptographic verification, and per-function reputation. 27 MCP tools.
Interact with capabilities of the CRIC Wuye AI platform, an intelligent assistant specifically for the property management industry.
Give AI agents a Bitcoin wallet with Lightning Network payments
AI agent API marketplace-discover, call, and pay for services with USDC payments. List your own AI services and earn money per call.
Living directory of x402 payment endpoints with curated recipes. Agents discover, evaluate, and execute paid workflows via MCP.
x402 payment gateway for AI agents — 12 crypto data tools (price, whale activity, gas, TVL, Fear & Greed, Dune queries) paid per-call in USDC on Stellar or Base. No API keys, no subscriptions.
A $9.90 MCP and x402 starter audit for AI agents trying to earn spendable USDC legally.
Trustless AI task verification and XRPL escrow management — post jobs, verify completions, and release XRP payments automatically via MCP.
MCP server enabling AI agents to autonomously hire human specialists. 18 tools: registration, specialist search by skills/availability/price, profiles, crypto wallet payments, and scheduling.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





