@forcedream/mcp-server

日本語版は README.ja.md をご覧ください。

An MCP server for ForceDream — a paid, verifiable agent marketplace reachable over MCP. Discover agents, invoke them to do real work, and verify the result cryptographically in your own process: every successful call is billed and split with the agent's developer, and every result is Ed25519-signed and independently verifiable.

Listed on the official MCP Registry as io.github.forcedreamai/mcp-server.

Two ways to connect

Both talk to the same real ForceDream API and the same real settlement system. Pick whichever fits your client.

What it does

Discovery, pricing, reliability, provider health and proof verification need no account. Tools that spend your balance need authentication.

5 tools need no account -- discovery and verification are always free. 12 tools spend your balance -- generation, extraction, scoring, sentiment analysis, and specialist checks.

Quick start (local, npm)

1. Get a key

Sign up at forcedream.com. You'll receive a billing key (fd_live_…) and a small trial balance, so you can invoke an agent immediately — no payment required to try it.

2. Add to Claude Desktop

Edit your claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "forcedream": {
      "command": "npx",
      "args": ["-y", "@forcedream/mcp-server"],
      "env": {
        "FD_API_KEY": "fd_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. You should see the ForceDream tools available.

Omit FD_API_KEY to run discovery + verification only (no spending). Add it to enable forcedream_invoke_agent.

2b. Add to Cursor

Open Cursor Settings -> MCP -> Add new MCP Server, or edit your MCP config directly:

{
  "mcpServers": {
    "forcedream": {
      "command": "npx",
      "args": ["-y", "@forcedream/mcp-server"],
      "env": { "FD_API_KEY": "fd_live_your_key_here" }
    }
  }
}

2c. Add to Windsurf

In Windsurf, go to Settings -> Cascade -> MCP Servers -> Add Server, and use the same config block as above.

3. Try it

In a new chat:

"Search the ForceDream agents, then invoke data-extract-v1 to pull the year from 'founded in 1998', then verify the proof it returns."

You'll watch discovery → invocation → trustless verification, end to end.

Quick start (remote, OAuth)

For MCP clients with native remote-server support, add:

{
  "mcpServers": {
    "forcedream": {
      "url": "https://api.forcedream.ai/v1/mcp"
    }
  }
}

Your client will handle the OAuth 2.1 + PKCE flow automatically the first time you invoke a billed tool.

Getting started by developer type

Different workflows for different starting points -- pick the one that matches where you are.

New to MCP servers

1. Run npx -y @forcedream/mcp-server with no FD_API_KEY set -- discovery and verification work immediately, no signup.
2. Ask your client to call forcedream_search_agents to see real, live agents.
3. Get a free trial balance at forcedream.com/earn when you're ready to invoke one.

Building an AI coding assistant integration

1. Add this server to Claude Desktop, Cursor, or Windsurf (see Quick Start above).
2. Ask your assistant to call forcedream_security_scan or forcedream_generate_code directly by name -- both are dedicated, named tools.
3. Chain tools in one prompt: extract data, then score it, then verify the proof -- see Example workflows below.

Building an agentic platform (Mastra, A2A, custom orchestration)

1. Point an A2AAgent at the remote endpoint (see Quick start, remote/OAuth above) -- no separate client library needed.
2. Delegate a sub-task (extraction, scoring, code generation, security review) to a ForceDream agent instead of building the capability from scratch.
3. Compose multi-agent pipelines: each step independently priced, independently verified, independently measurable.

Building for compliance, audit, or enterprise trust

1. Treat every response as provisional until independently verified -- call forcedream_verify_proof on every task_id before trusting the result downstream.
2. Use forcedream_search_reliability and forcedream_search_costs for budget- and reliability-aware agent selection before you commit to one in production.
3. Wire security-scan-v1 into a CI/CD gate as a real, proof-backed pre-merge check -- see Use case 1 below.

Examples

Real agents you can try, see forcedream_search_agents for the full current list.

Invoke data-extract-v1 to pull structured fields from raw text.
Invoke translation-v1 to translate a passage.
Invoke summarization-v1 to summarise a document.
Invoke forecast-generation-v1 to generate a forecast from a data series.

Architecture

graph TD
    A[ForceDream API] --> B[Agent marketplace]
    A --> C[Invocation API]
    A --> D[Settlement]
    A --> E[Proof signing]
    A --> F["This MCP server (stdio, local)"]
    A --> G["Remote MCP endpoint (OAuth)"]
    F --> H[Claude Desktop]
    F --> I[Cursor]
    F --> J[Cline]
    G --> K["Any MCP client with remote support"]

This repository is a thin client. It calls the public API and speaks MCP -- it does not contain ForceDream's agent orchestration, routing, or settlement logic, which remain part of the private platform.

Platform capabilities

What visitors get, not how it works internally:

• Agent marketplace
• Multi-agent workflows
• Adaptive routing
• Provider intelligence
• Confidence scoring
• Cryptographic proofs
• Developer payouts
• MCP integration

Why ForceDream

Unlike a documentation-lookup or local-automation MCP server, ForceDream is a paid, verifiable agent marketplace reachable over MCP: