Farm.js Docs MCP
Remote MCP server with Farm.js documentation: pages, sections, code examples and config options for an agent to search
- 659 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The server only searches and returns public documentation text and gets no access to your code or data
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/farm-js-docsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The server only searches and returns public documentation text and gets no access to your code or data
This is third-party code. Review the repository files before installing.
What it does
Farm.js is a full-stack framework for web applications built on Vite and Nitro with React by default and beta adapters for Preact, Solid, Vue and Svelte. Every app serves pages to people and to AI agents: server-rendered HTML, a Markdown copy of each page and `llms.txt` are on from the start. With MCP turned on, the app's server functions become tools for agents. This card covers a different artifact: the documentation server `dev.farmjs/docs` published in the MCP registry. It is remote, works over Streamable HTTP at `https://mcp.farmjs.dev/mcp` and searches and reads the Farm.js documentation: pages, sections, code examples and config options. The agent answers from current pages instead of inventing an API from model memory. Nothing needs installing, you only add the URL to the client.
Who it is for. Developers building an app on Farm.js with Claude Code or Cursor who want the agent to check the framework's current documentation.
Good fit when
- The agent edits `farm.config.ts` and checks option names against the docs instead of guessing
- A new page in the `src/app` directory is built from a code example in the routing section
- Mutations through Server Actions with `"use server"` have to be written from the description rather than a guess
- The agent has to work out how to turn on MCP and `llms.txt` in your own Farm.js app
Not a fit when
- The project is not on Farm.js: the server answers only from this framework's documentation
- You need access to your app's data or server functions: for that you turn on MCP inside the app itself
- You need to work offline: the server is remote, and offline docs have to come from the repository
Example request
Find in the Farm.js docs how to define a route with a Server Action and show a code example for a form with a mutationMCP
- Transport
- http
- Authentication
- not required
Limitations
The server is hosted by the framework's authors and answers over the network, so you need internet and availability depends on their hosting. The MCP registry version 0.1.28 matches the documentation version while the framework itself is at 0.1, and per the Stability and Support page part of it is experimental: the Preact, Solid, Vue and Svelte adapters are beta and the AOT compiler for React is experimental. The server's tool set is not described in the repository, so look at the list through the client. The server asks for no keys or tokens.
How to disable. Remove the server from the client config, for example `claude mcp remove farmjs-docs`. It leaves no packages or files on the machine.
FAQ
How do I connect the Farm.js docs to Claude Code?
Run `claude mcp add --transport http farmjs-docs https://mcp.farmjs.dev/mcp`. The URL comes from the MCP registry and no keys are needed.
How does the docs server differ from MCP inside an app?
The docs server is a single shared one and only searches and reads documentation text. MCP inside a Farm.js app exposes your own project's server functions to agents.
How do I create a Farm.js app?
With `pnpm create @farm.js/app my-app --template basic --typescript`, then run `npx farm dev`. Tailwind CSS is preconfigured in the created app.
Which renderers are supported?
React by default, and the Preact, Solid, Vue and Svelte adapters are in beta and use the same routing and server contracts.
What is llms.txt in Farm.js?
A file every Farm.js app serves along with Markdown copies of pages and server-rendered HTML. These modes are on by default so that both people and agents can read the pages.
Discussion
No questions or reviews yet.
Related
MCP serversA key-free remote MCP server that gives an agent the docs and examples of react-three-fiber, drei, zustand and jotai page by page
Connects an agent to a running Next.js 16+ dev server: errors, routes, logs and docs for your installed version
The Arc UI MCP server: an agent searches animated React components, reads docs and props and gets the shadcn install command.
An agent gets the MDMA spec, prompts and validation so it can answer with forms, tables and approvals right inside Markdown
Vuetify MCP server: the agent pulls component APIs, guides, release notes and the v2 to v3 upgrade playbook from it
ReactUse MCP: React hooks reference
ReactUse MCP
ReactUse MCP server: the agent finds the right React hook and reads its description, example and API table straight from the library
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Farm.js Docs (this card) | yes | not required | 659 | |
| Context7 | yes | API key | 64,735 | a general service for current documentation of thousands of libraries rather than the pages and options of one framework |
| Ant Design Components MCP | no | not required | 247 | documentation and API of Ant Design components rather than the Farm.js framework |
README in short
The text presents Farm.js as a framework for the web and agents and lists features in a table: a custom RSC renderer, Server Actions, typed routes and streaming server rendering. Next come creating an app with the `create` command, pages in `src/app`, plugins and contributing.