MCP server
Connect Claude, Cursor, VS Code and other agents to the Echo Editor docs via the Model Context Protocol.
This site runs a remote Model Context Protocol server at /mcp (Streamable HTTP). Coding agents can search and read the documentation, list extensions and generate setup code — so they write correct Echo Editor code instead of guessing.
Connect
Running the docs locally (pnpm docs:dev)? Use http://localhost:3000/mcp.
Tools
| Tool | Description |
|---|---|
search_docs | Ranked full-text search across all pages, returning excerpts. |
get_doc | Read a page as Markdown by path (e.g. /guide/collaboration). |
list_docs | Every page with its path and description, grouped by section. |
list_extensions | The extension catalogue with descriptions and configuration examples, filterable by category. |
get_setup_code | Install commands and a ready-to-paste Vue or Nuxt component for a preset (minimal, blog, full), extra extensions, output format and optional collaboration. |
Resources
Every page is exposed as a resource at docs://<path> (e.g. docs://guide/markdown), so clients that support resources can attach pages to the context directly.
Prompts
| Prompt | Arguments | Description |
|---|---|---|
integrate_echo_editor | framework (vue | nuxt), requirements | Walks the agent through picking extensions, generating setup code and checking the relevant guides. |
Example
"Add a collaborative Markdown editor with image uploads to my Nuxt app."
The agent calls list_extensions, then get_setup_code with framework: "nuxt", output: "markdown", extra: ["ImageUpload"] and collaboration: true, and reads /guide/uploads with get_doc — producing a working component on the first try.
Self-hosting
The server lives in the docs app (docs/server/mcp) and is built with @nuxtjs/mcp-toolkit. Deploy the docs anywhere Nitro runs (Vercel, Netlify, Cloudflare, Node) and the endpoint comes with it.