What is io.github.BFAI-1/taskfleet-mcp?

Pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base.

How do I install io.github.BFAI-1/taskfleet-mcp?

Clone io.github.BFAI-1/taskfleet-mcp from https://github.com/BFAI-1/taskfleet-mcp and configure it as an MCP server in your client (Claude Desktop, Cursor, or VS Code).

What category does io.github.BFAI-1/taskfleet-mcp belong to?

io.github.BFAI-1/taskfleet-mcp is listed under Developer Tools MCP servers on MCPFind.

io.github.BFAI-1/taskfleet-mcp — MCP Server for Developer Tools

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.

Tools

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            # publishes taskfleet-mcp to npm

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
# should print: taskfleet-mcp v0.1.0: 14 tools from https://taskfleet.net (payment: caller-pays)

Set up in your AI client

AI clientOperating system

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json

{
  "mcpServers": {
    "io-github-bfai-1-taskfleet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "taskfleet-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Compatible MCP Clients

io.github.BFAI-1/taskfleet-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.

Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.

VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.

Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.

Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

io.github.BFAI-1/taskfleet-mcp