taskfleet-mcp
An MCP server that exposes TaskFleet's
pay-per-call AI task APIs as tools any MCP-capable agent can discover and call:
web search, web scraping, structured extraction, translation, code review,
summarization, and on-chain wallet intelligence.
Payment is handled by the x402 protocol (USDC on Base) — the caller brings
the wallet; there are no accounts or API keys.
Why this exists
It's a discovery channel. Agents that browse MCP registries or load MCP
servers can find and use TaskFleet directly, in addition to the x402
directories. The tool list is loaded live from the fleet's manifest, so new
services appear automatically.
Use it (as an agent operator)
Add to your MCP client config (e.g. Claude Desktop, or any MCP host):
{
"mcpServers": {
"taskfleet": {
"command": "npx",
"args": ["-y", "taskfleet-mcp"],
"env": {
"BUYER_WALLET_PRIVATE_KEY": "0xYOUR_WALLET_KEY"
}
}
}
}
- With
BUYER_WALLET_PRIVATE_KEY (an EVM key holding a little USDC on Base):
tool calls auto-pay via x402 and return results.
- Without it: tools still list (discovery works) and a call returns the
x402 payment instructions, so an x402-capable client can pay itself.
TASKFLEET_URL overrides the target (defaults to https://taskfleet.net).
The wallet key stays on the operator's machine — it never reaches TaskFleet,
which only ever sees the on-chain payment.
One tool per TaskFleet service, named taskfleet_<service> (e.g.
taskfleet_search, taskfleet_scrape, taskfleet_wallet_intel). Each tool's
input schema and price come straight from the fleet manifest.
Publish it (as the fleet operator — discovery)
cd mcp
npm install
npm publish
Once on npm it's installable via npx taskfleet-mcp and can be listed in MCP
registries (the public MCP Registry, Smithery, PulseMCP, etc.) — each listing
is another place agents discover TaskFleet. Submitting to those registries is
free and generally just points at the npm package or this repo.
Local test
npm install
TASKFLEET_URL=https://taskfleet.net node index.mjs