Query this documentation from your assistant (neo-docs MCP)
This guide explains how to connect your AI assistant to this documentation, so it answers questions about NEO by searching the official docs instead of answering from memory.
| Server name | neo-docs |
| Package | neo-docs-mcp, run with uvx neo-docs-mcp |
| Type | Local (stdio): it runs on your computer, like the Jira or Playwright MCPs |
| Content | Everything on this site, in Spanish and English, updated every time the docs are published |
| Access | Read-only |
1. What is it for?
While you work with NEO, the assistant can look up the documentation on the spot: how to configure CI, what a skill does, which playbook fits a situation, what an engine error means. Every answer includes the link to the section it came from, so you can always check it.
Example questions:
- "How do I configure NEO's CI on GitLab?"
- "Which playbook do I use if a bug shows up in production?"
- "What's the difference between
guardandstop_unlessin a plan?"
2. How it stays up to date
The server doesn't ship the documentation inside. Every time the site is published, its search index is published too, and the server downloads it at startup. If nothing changed, it reuses the copy it already has; without a connection, it works with the last one it downloaded.
You don't need to update the package to get the new docs: opening a new assistant session is enough.
3. Connect it
Requirement: uv installed (it provides uvx). It's the same one the Jira MCP uses; check it with uvx --version.
From a terminal:
claude mcp add -s user neo-docs -- uvx neo-docs-mcp --lang en
-s user makes it available in all your projects. Then open a new conversation: MCP servers are loaded when the session starts.
In .mcp.json (Claude Code), .vscode/mcp.json (Copilot), or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"neo-docs": {
"command": "uvx",
"args": ["neo-docs-mcp", "--lang", "en"]
}
}
}
In .vscode/mcp.json the root key is servers instead of mcpServers.
--lang en makes English the default; without it, the tools answer in Spanish.
How it searches
Every query combines two searches and merges the results: a lexical one (it finds exact names such as lippia-neo-run-and-heal or qa-stack.yaml) and a semantic one (it understands questions phrased differently). There's nothing to choose or configure.
Semantic search uses a model that runs on your computer (multilingual-e5-small). The first time, it downloads it in the background (about 470 MB): meanwhile the server already answers with lexical search, and switches to the combined search as soon as it's done. After that, it uses it from the start.
If you work on a network where the model can't be downloaded, add "--mode", "bm25" to args to use lexical search only.
4. Check that it works
- In the assistant, open the list of MCP servers (in Claude Code:
/mcp).neo-docsmust show as connected. - Ask something from the docs and tell it to use them, for example: "search neo-docs for how to configure CI with NEO".
- The answer must include links to
docs.neo.crowdar.com.
5. Which tools it exposes
| Tool | What it does |
|---|---|
search_docs |
Searches the docs and returns the most relevant fragments, with their link. If several fragments of the same section are relevant, it returns the whole section |
get_section |
Returns a whole section, from the id search_docs gave |
get_page |
Returns a whole page and the list of its sections |
list_toc |
Returns the site's navigation tree |
All of them accept lang (en or es).
Query in the language of the docs you're searching
Search works best with queries in the same language as lang. Both natural-language questions and exact names (lippia-neo-run-and-heal, qa-stack.yaml, bug-fix-cycle) work.
6. Common problems (and what to do)
| What you see | Why it may happen | What to do |
|---|---|---|
neo-docs doesn't show in /mcp |
You added it with the session already open | Open a new conversation (in VS Code, if needed, Developer: Reload Window) |
| It shows in one folder but not another | In Claude Code you added it with project scope (the default) | Add it again with -s user |
uvx: command not found |
uv isn't installed | Install it from docs.astral.sh/uv |
could not reach … and there is no cached index |
No connection on the first start | Connect once: after that it works with the local copy |
| The assistant answers without checking the docs | It decides on its own when to use a tool | Ask it explicitly: "search neo-docs…" |
| Something you just published doesn't show up | The server downloads the index at startup | Open a new assistant session |