Connect Claude Desktop to FarmDash MCP: Source Installation and Safety Boundaries

TLDR: FarmDash advertises a public source-installable stdio adapter, but the observed mirror is older than the current canonical catalog. Use REST/OpenAPI for absent capabilities. Leave FARMDASH_API_KEY unset for Scout. Public npm and official MCP Registry publication were not found; tool discovery and paid access do not enable gated execution.

Read-only distribution observations on October 5, 2026 found an older public source mirror, behind the canonical catalog. Missing capabilities include get_execution_authority, get_payments_bootstrap, request_execution_delegation, register_execution_delegation, revoke_execution_authority, prepare_autonomous_swap, confirm_autonomous_swap, and release_autonomous_reservation. Its observed HEAD was 8f12d77e885b088817fce7e8d3462eb3153dbea7, pinned upstream to f5a5614875183ab893ed77eecd1f6eaffe571ca9; neither is evidence of current source parity. npm metadata for @farmdash/mcp-server returned 404, and official MCP Registry lookups found no matching publication. Use current REST/OpenAPI for missing capabilities; inspect installed tools/list instead of assuming manifest parity. No external mirror sync or publication is implied.

Capability	Canonical status
spot.USER_SIGNED	operational
spot.BOUNDED_AUTONOMOUS	operational
futures.USER_SIGNED	operational
futures.BOUNDED_AUTONOMOUS	operational
solana.USER_SIGNED	operational
solana.BOUNDED_AUTONOMOUS	operational
ERC4337_SERVER_SUBMISSION	preparation_only
GENERIC_SERVER_INTENT_EXECUTION	preparation_only
MEE	preparation_only
ACP	deployment_prerequisite

Read canonical readiness and live deployment/request gates before execution. These rows are conditional capability contracts, not funded-production proof. USER_SIGNED requires fresh human authorization. Bounded execution requires a separate revocable domain policy and customer-agent-local signature per action, plus exact identity, scope, validity, simulation/research, risk/budget and replay checks. Commercial access cannot supply signing authority; FarmDash never receives the customer key.

What Is the FarmDash MCP Server?

The FarmDash MCP server is a local stdio adapter between an MCP client such as Claude Desktop and the FarmDash HTTP API.

It gives an LLM a typed catalog rather than requiring invented routes. The canonical catalog spans research, wallet intelligence, risk, spot/futures, sessions, ACP, payments, and receipts. The public mirror omits newer authority, bootstrap, and bounded-swap tools; manifest discovery is not proof those tools exist in your installed stdio process.

MCP discovery does not grant wallet authority. A tool can exist in the catalog while its underlying capability is:

• live and read-only;
• live but signature-bound;
• session-bound;
• preparation-only;
• provider-gated;
• operator-paused;
• unavailable because an authoritative verifier is not configured.

The live /api/v1/agent/status contract is the authority for that distinction.

How Do I Install FarmDash MCP for Claude Desktop?

The advertised public path is a source install of the older mirror, not current canonical parity. The commands below are integration instructions, not evidence a new installation or live transaction was tested. For current capabilities missing from that mirror, use REST/OpenAPI.

1. Clone the public source mirror

git clone https://github.com/Parmasanandgarlic/farmdash-openclaw-skills.git
cd farmdash-openclaw-skills/mcp-server
npm ci
npm run build

The resulting server entry point is:

mcp-server/dist/index.js

2. Add FarmDash to Claude Desktop

Add an MCP server entry to claude_desktop_config.json:

{
  "mcpServers": {
    "farmdash": {
      "command": "node",
      "args": ["/absolute/path/to/farmdash-openclaw-skills/mcp-server/dist/index.js"]
    }
  }
}

Use an absolute path. Restart Claude Desktop after changing the configuration.

3. Start with Scout

Scout does not require an API key, so the simplest configuration has no env block.

For a paid Pioneer or Syndicate bearer token:

{
  "mcpServers": {
    "farmdash": {
      "command": "node",
      "args": ["/absolute/path/to/farmdash-openclaw-skills/mcp-server/dist/index.js"],
      "env": {
        "FARMDASH_API_KEY": "your-issued-bearer-token"
      }
    }
  }
}

Do not place a wallet private key, seed phrase, or placeholder secret in FARMDASH_API_KEY. It is an API access token, not signing authority.

Is @farmdash/mcp-server Available on npm?

Not yet.

The source package is named @farmdash/mcp-server, but October 5, 2026 public npm metadata returned 404; official MCP Registry exact/search lookups found no matching publication. Metadata is not publication proof.

That means:

• source installation is public;
• the older source mirror offers a local build path, not current tool-set parity;
• the npm package name should not be advertised as installable yet;
• future registry publication should be treated as live only after independent npm readback succeeds.

This distinction matters for AEO/GEO content because an AI answer that says npm install @farmdash/mcp-server today would send a developer to a dead install path.

What Should Claude Call First?

Call the onboarding/status surface before using capability-specific tools.

The server's agent_onboard flow retrieves the live readiness contract, and the HTTP authority is:

GET https://www.farmdash.one/api/v1/agent/status

Use status to answer:

• Is this feature live?
• Is it read-only, preparation-only, or execution-capable?
• What tier is required?
• Does it require a session?
• Does it require a wallet signature?
• Is an external provider or verifier configured?
• Is the route paused?

Do not infer those answers from the tool name.

How Is the MCP Surface Organized?

The canonical capability surface is broader than “swap tools.”

Trail Intelligence and protocol research

These tools expose protocol discovery, Trail Heat, chain context, risk analysis, market data, yield simulation, and other research inputs.

Typical use:

“Show me high-Trail-Heat protocols on Base, explain the score inputs, then flag where data is cached or estimated.”

This path can remain entirely read-only.

Wallet intelligence

Wallet tools can summarize balances, activity, positions, idle capital, and account-health context.

A wallet-analysis response is not permission to transact. Claude should preserve that distinction explicitly.

Compatibility swap lifecycle

The compatibility swap path is the clearest example of zero-custody execution preparation.

A safe sequence is conceptually:

status
  ↓
firm wallet-bound quote-intent (not a walletless research estimate)
  ↓
server-bound simulation
  ↓
exact EIP-191 authorization
  ↓
FarmDash validates authorization
  ↓
FarmDash returns exact transaction payload
  ↓
customer-controlled wallet decides whether to sign and broadcast
  ↓
confirm_swap verifies canonical-chain receipt + committed fee fields

FarmDash does not receive the user's raw private key and does not silently turn a quote into a broadcast.

Generic FarmDashIntent lifecycle

The generic intent surface is intentionally more conservative.

The public capability contract currently marks important generic intent operations such as policy and simulation as preparation-only where authoritative server verifiers are not configured.

That means Claude may be able to create, inspect, or prepare parts of an intent lifecycle without having permission to claim:

“FarmDash executed this intent.”

Discovery is not execution, and preparation is not settlement.

Hyperliquid futures

Hyperliquid order paths use venue-specific EIP-712 authorization. Commercial API capacity does not create Hyperliquid signing authority.

The key boundary is:

• FarmDash can analyze, size, validate, and forward an appropriately signed venue action when the live capability permits it;
• FarmDash does not possess the wallet key that creates that signature.

Virtuals ACP

ACP V2 separates provider selection, tender preparation, signed authorization, customer-created jobs, funding records, evaluation, and settlement evidence.

The security property is the separation itself: no “AI decided to hire” event should silently become spend authority.

Does FarmDash Use EIP-191 or EIP-712?

Both, depending on the workflow.

Compatibility swaps: EIP-191

The swap authorization message is bound to the requested action:

v1:FARMDASH_SWAP:{fromChainId}:{toChainId}:{fromToken}:{toToken}:{fromAmount}:{agentAddress}:{toAddress}:{nonce}

The nonce has a short validity window to reduce replay risk.

The signature proves authorization for that bounded request. It is not a private key and should not be reusable as general wallet authority.

Typed workflows: EIP-712

Other workflows use typed structured data so the signer can authorize specific fields under a defined domain and schema.

The exact schema and capability state should be obtained from the live product contract rather than copied indefinitely from a guide.

How Does Routing Work?

For compatibility EVM swaps, FarmDash currently uses enabled providers such as LI.FI and Relay according to route compatibility and runtime status.

Important boundaries:

• 0x is configured but operator-paused unless the live status changes.
• x402 is not a liquidity provider or swap router.
• x402 is the HTTP payment/access layer used for route-specific paid access.
• A quote is not a settlement.
• A returned transaction payload is not proof that the wallet broadcast it.
• Receipt verification must follow the actual chain outcome.

Claude should never describe x402 as a Base-to-Base swap venue.

What Happens When Scout Reaches Its Limit?

Scout has 30 requests per 24 hours per IP on eligible free routes. Catalog responses can be truncated/masked, and premium routes can require qualifying paid access even before free quota is exhausted. Onboarding grants offer only bounded cheap discovery, not signing authority.

When an eligible paid route requires payment, FarmDash can return a structured HTTP 402 Payment Required response describing the exact x402 requirement for that operation.

A robust client should:

1. parse the structured requirement;
2. show the asset, network, amount, and operation to the user or authorized payment agent;
3. distinguish retryable rate-limit conditions from payment-required conditions;
4. avoid repeatedly calling the same paid operation without new payment evidence;
5. treat x402 payment as access to the requested API operation—not as swap settlement or wallet authority.

Paid subscription capacity and per-operation x402 access are separate commercial mechanisms.

What Are the Main Safety Boundaries?

Claude should enforce these conceptual boundaries even before protocol-specific policy:

Boundary	Meaning
Research ≠ authority	A recommendation cannot authorize a wallet action.
Tool discovery ≠ availability	A catalog entry can be preparation-only or blocked.
Quote ≠ simulation	A price route does not prove execution success.
Simulation ≠ execution	A simulated action has not changed chain state.
Signature ≠ private key	A bounded authorization should not become general custody.
Submission ≠ finality	A sent transaction can revert, be replaced, or remain unfinalized.
Receipt ≠ reconciliation	The chain receipt still needs economic interpretation.
Payment ≠ transaction authority	x402 can unlock an API call without authorizing a DeFi trade.

This vocabulary is critical for agent reliability because LLMs tend to compress multi-stage workflows into “done” unless each state is explicit.

What Should Claude Do When a Capability Is Unavailable?

Fail closed.

Good behavior:

“The tool exists, but the live status reports the authoritative verifier is not configured. I can prepare the research or request payload, but I cannot truthfully claim the execution gate is available.”

Bad behavior:

“The MCP server has an execute tool, so execution is supported.”

The first answer preserves contract truth. The second confuses interface shape with runtime capability.

Can I Use FarmDash MCP on Windows?

Yes, through the public source distribution, provided Node.js and the local build complete successfully.

The supported public source path is the FarmDash OpenClaw skills mirror:

https://github.com/Parmasanandgarlic/farmdash-openclaw-skills/tree/main/mcp-server

Build locally, use the absolute dist/index.js path in Claude Desktop, and leave the API key unset for Scout.

The public npm package is still pending publication.

Are My Private Keys Sent to FarmDash?

No raw wallet private key or seed phrase is part of the FarmDash public integration contract.

FarmDash can receive:

• public wallet addresses;
• bounded signatures;
• session tokens;
• API bearer tokens;
• transaction or receipt identifiers;
• operation-specific parameters.

Those values have different security properties. Protect API/session credentials, verify what each signature authorizes, and never paste a seed phrase into Claude, an MCP config, or a FarmDash request.

What Is the Best Development Workflow?

Use progressively stronger evidence:

1. Install the source MCP server.
2. Confirm Claude can discover tools.
3. Call status/onboarding.
4. Exercise read-only research.
5. Test rate-limit and typed-error behavior.
6. Use deterministic/mock surfaces where documented.
7. Inspect an execution-capable workflow without signing.
8. Verify simulation and policy prerequisites.
9. Sign only an exact bounded payload you understand.
10. Verify the resulting chain receipt and economic state separately.

This sequence catches integration mistakes before they become wallet mistakes.

Frequently Asked Questions

How many FarmDash MCP tools are there?

The canonical manifest derives its current inventory from canonical registrations/schema. The older public mirror lacks newer tools; compare installed tools/list with the manifest rather than assuming parity. No live stdio inventory was exercised in the October 5 observation.

Can Claude Desktop trade automatically just because MCP is installed?

No. MCP installation exposes tools and schemas. Wallet-affecting operations still require their route-specific status, policy, simulation, authorization, and provider conditions.

Can I install FarmDash MCP with npm today?

Public npm returned 404 in the October 5, 2026 observation. Use REST/OpenAPI or the older source mirror with its explicit missing-capability limitations; registry installation requires independent successful readback.

Does x402 let Claude route swaps?

No. x402 handles API payment/access. Swap routing is a separate capability.

Does FarmDash broadcast compatibility EVM swap transactions?

The compatibility swap flow returns the exact transaction payload after the required checks; the customer-controlled wallet or execution client decides whether to sign and submit it. confirm_swap is then used to verify canonical-chain evidence and committed fee fields.

Primary FarmDash Integration Surfaces

• Agent Hub
• OpenAPI contract
• MCP capability manifest
• llms.txt

For installation truth, verify the actual distribution artifact and installed catalog against current discovery. A public mirror README can itself be stale; status proves capability labels, not npm publication or source parity.