![\"FrootAI](\"https://frootai.dev/img/frootai-mark.png\")
One local MCP server for FrootAI knowledge, FAI workflows, marketplace operations, and trust-gated federation.
\n\n ![\"npm](\"https://img.shields.io/npm/v/frootai-mcp?style=flat-square&logo=npm\")
![\"npm](\"https://img.shields.io/npm/dm/frootai-mcp?style=flat-square&label=downloads\")
![\"Node.js](\"https://img.shields.io/node/v/frootai-mcp?style=flat-square\")
![\"MIT](\"https://img.shields.io/badge/license-MIT-f2c94c?style=flat-square\"){kind=icon}
Product page · Setup guide · FAI Orchard · npm
\n\n\n\n## Choose the right MCP job\n\n| Job | Use | Boundary |\n|---|---|---|\n| **FrootAI knowledge** | Search architecture knowledge, inspect Solution Plays, compare models, estimate cost | Bundled and read-oriented unless a live tool is selected |\n| **FAI workflows** | Build → review → tune, wire manifests, evaluate quality, scaffold components | Tools declare read/write and open-world annotations |\n| **Local federation** | Discover, trust, attach, invoke, and detach external MCP areas | Downstream credentials stay in the local process |\n| **Marketplace** | Discover, validate, compose, install, and update FAI plugins | File-changing tools are explicitly annotated |\n| **Orchard Harvest MCP** | Convert repositories into governed Solution Plays | Separate specialized package; see [FAI Orchard](https://frootai.dev/orchard) |\n\nThe npm package exposes **62 MCP tools**. The hosted FrootAI MCP endpoint intentionally exposes a smaller public, read-oriented surface. This README documents the local npm server.\n\n## Five steps to first value\n\n### 1. Start the local server\n\n```bash\nnpx -y frootai-mcp@latest\n```\n\nRequirements: Node.js 18 or newer. The default transport is stdio and is normally launched by an MCP client.\n\n### 2. Connect an MCP client\n\nVS Code and GitHub Copilot — `.vscode/mcp.json`:\n\n```json\n{\n \"servers\": {\n \"frootai\": {\n \"type\": \"stdio\",\n \"command\": \"npx\",\n \"args\": [\"-y\", \"frootai-mcp@latest\"]\n }\n }\n}\n```\n\nClaude Desktop or Cursor:\n\n```json\n{\n \"mcpServers\": {\n \"frootai\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"frootai-mcp@latest\"]\n }\n }\n}\n```\n\nRestart or reload the client after saving its configuration.\n\n### 3. Run a useful first workflow\n\nAsk the connected agent:\n\n```text\nFind the best FrootAI Solution Play for a secure enterprise RAG system.\nCompare the top two options, estimate production cost direction,\nand show the FAI manifest checks required before implementation.\n```\n\nA typical tool path is:\n\n```text\nsemantic_search_plays → compare_plays → get_play_detail\n → estimate_cost → validate_manifest\n```\n\n### 4. Build, review, and tune\n\n```text\nagent_build → architecture, patterns, dependencies, and Play context\nagent_review → deterministic code/config findings with actionable guidance\nagent_tune → configuration thresholds, blockers, and readiness guidance\n```\n\nEach tool returns evidence for the next decision. The chain does not silently deploy infrastructure or grant unrestricted workspace authority.\n\n### 5. Add federation or Orchard only when needed\n\nFor an external MCP server:\n\n```text\nfai_discover_mcp → fai_trust_query → fai_attach_mcp\n → fai_list_attached → fai_invoke_via → fai_detach_mcp\n```\n\nFor repository-to-Solution-Play conversion, use the specialized [Orchard Harvest MCP](https://frootai.dev/mcp?view=start). Orchard discovers, extracts, retrieves, scaffolds, customizes, and stages a governed artifact; FAI Engine verification remains a separate decision boundary.\n\n