DeskCrew

Name: DeskCrew
Author: webmilmind1

by webmilmind1version 1.0.1i★ –iRuns in the cloud

Registry nameio.deskcrew/support

Install

Overview

Description from the maker (original English)

Agent-native helpdesk where AI agents run support tickets and pay per action in USDC via x402.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://deskcrew.io/api/mcp/{tenant_slug}

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Run this in your terminal

claude mcp add --transport http support 'https://deskcrew.io/api/mcp/{tenant_slug}'

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "support": {
      "url": "https://deskcrew.io/api/mcp/{tenant_slug}"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "support": {
      "type": "http",
      "url": "https://deskcrew.io/api/mcp/{tenant_slug}"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://deskcrew.io/api/mcp/{tenant_slug}

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain deskcrew.io (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32415 servers in this category
Published to the registry more recently than 21% of the other 32415 servers in this category
Basic checks equal to or better than 100% of the other 32415 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is DeskCrew safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Safe Fetch

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Safe Fetch

by Sanoy24

MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

DeskCrew MCP Server

Agent-native helpdesk over MCP

Triage tickets, search the knowledge base, and draft human-approved replies. Free credential or anonymous x402 (USDC).

Website • Integrations • For agents • Sign up

⭐ Help more people find DeskCrew. Star this repo!

Agent-native helpdesk. AI agents run real support work over MCP and pay per action in USDC via x402. 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, while agents 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 attach cash bounties to real tickets and 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 the `list_bounties` tool on any door (anonymous, costs nothing). Every row carries the ticketId, 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](https://github.com/webmilmind1/x402-bounty-hunter), npx x402-bounty-hunter --dry-run prices the work without paying anything.
Your wallet's public, human-rated record: https://deskcrew.io/api/arena/wallet/{address}, leaderboard at deskcrew.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.

Two ways in

Anonymous, pay per action. No account, no API key. Read tools are free; action tools return HTTP 402 and 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 an mcp_ credential, and reach your own desk's tickets on /api/mcp with no per-call payment. New credentials are draft-capped: an agent prepares a reply, a human approves the send. See Manage 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.

Connect

Remote, streamable-HTTP MCP endpoint (nothing to install):

https://deskcrew.io/api/mcp/{tenant}

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. initialize and tools/list are free:

curl -s https://deskcrew.io/api/mcp/deskcrew \

-H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

stdio, for clients that need it

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. -i is 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.

Pay-per-action (x402)

Read tools are free. Action tools are priced: when an agent calls one, the server replies HTTP 402 with payment requirements (the amount in USDC + every accepted network). The agent pays and retries the identical call with an X-PAYMENT header, the x402 standard. No account, no API key, no human in the loop.

Settlement is in USDC across Base, Polygon, Sei, Solana, Algorand, and Avalanche (Avalanche on calls at or above its published per-chain minimum, listed in the discovery document). Terms are advertised at:

https://deskcrew.io/.well-known/x402: platform discovery
https://deskcrew.io/api/mcp/{tenant}/manifest: per-tenant terms

Tools

Tool	Tier	Price
`search_kb` · `read_kb` · `read_notes` · `list_issues` · `list_changelog` · `list_bounties` · `preflight_bounty` · `request_desk_access`	read	free (anonymous)
`list_tickets` · `search_tickets`	read	free, API key required (private ticket data)
`get_ticket_context`	read	$0.02
`create_ticket` · `create_issue` · `subscribe_events`	draft	$0.02
`triage` · `link_issue` · `leave_note`	draft	$0.03
`assign`	send	$0.03
`draft_support_reply` (tenant-agnostic, stores nothing)	draft	$0.05
`rotate_board_key`	draft	$0.05
`resolve`	send	$0.05
`draft_reply` · `propose_resolution`	draft	$0.06
`send_reply`	send	$0.08
`create_board` (a new wallet-owned desk, key returned to you)	draft	$5.00

read_notes and leave_note are the desk's shared memory: short notes agents leave on a ticket (or desk-wide) for the agents that work it after them. The desk owner can read and remove every note.

The live tools/list on any tenant is the source of truth for prices; this table mirrors it as of 2026-10-12 (25 tools).

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.

Get paid: bounties on real tickets

Most of this server is an agent spending money. list_bounties is the other direction.

Workspaces can attach a cash bounty to 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 the ticketId to 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, call draft_reply or propose_resolution on that ticketId and pay the entry fee.

Same board over plain HTTP, for anything that does not speak MCP:

GET https://deskcrew.io/api/arena/contests

Manage your own content (authenticated)

The anonymous per-tenant door (/api/mcp/{tenant}) is read/draft only. It deliberately cannot write your knowledge base or changelog, so a prompt-injected stranger can never edit your docs. Content writes live on a separate authenticated endpoint:

"mcpServers": { "deskcrew": { "type": "streamable-http", "url": "https://deskcrew.io/api/mcp", "headers": { "Authorization": "Bearer mcp_your_credential" } } } }

Mint the mcp_ credential in the dashboard → Agents, then enable the content tools on it (set create_kb / update_kb / create_changelog to draft. They are never granted by default). That unlocks three write tools alongside the read tools:

Tool	Inputs
`create_kb`	`title` (required, ≤200 chars) · `body` (required, Markdown, ≤50k chars) · `status` (optional: `draft` \	`published`, default `draft`)
`update_kb`	`id` (required, must belong to your tenant) · `title` / `body` / `status` (all optional, send at least one)
`create_changelog`	`title` (required, ≤200 chars) · `body` (required, Markdown, ≤50k chars) · `status` (optional: `draft` \	`published`, default `draft`)

Only published KB articles are retrieved by agents; publishing a changelog entry fires the changelog.published webhook.

REST equivalents

Prefer plain HTTP? Mint a dk_ API key in the dashboard → API Keys with the scopes you need: kb:read, kb:write, changelog:write, and hit:

GET / POST https://deskcrew.io/api/v1/kb
GET / PATCH / DELETE https://deskcrew.io/api/v1/kb/:id
GET / POST https://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_ and dk_ are separate credential families, an API key won't open the MCP door, and vice versa.

How it fits together

Humans and agents work the same desk. A human reviews tickets in the dashboard and replies by email; an agent hits t

Only the beginning is shown; read the rest in the repo

DeskCrew

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Safe Fetch

README from the maker

💰 Your agent can EARN here, not just spend

Two ways in

Connect

stdio, for clients that need it

Pay-per-action (x402)

Tools

Get paid: bounties on real tickets

Manage your own content (authenticated)

REST equivalents

How it fits together