MCP server for all Recon knowledge — getrecon.xyz, book.getrecon.xyz, and getrecon.substack.com
Recon MCP Knowledge MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for all Recon knowledge — getrecon.xyz, book.getrecon.xyz, and getrecon.substack.com.
MCP server that makes Recon documentation searchable by AI tools. Fetches and parses getrecon.xyz/llms-full.txt into structured, queryable content.
Once Recon MCP Knowledge is connected, these are the calls the assistant has available:
search_glossary — query: stringget_blog_post — slug: stringget_comparison — slug: stringsearch_site — query: stringlist_tools — (none)get_book_chapter — slug: stringget_book_concept — slug: stringsearch_book — query: stringlist_book_chapters — (none)get_substack_post — slug: stringsearch_substack — query: stringlist_substack_posts — (none)The server ships on npm as @recon-fuzz-mcp/knowledge, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Recon MCP Knowledge's toolset — search_glossary, get_blog_post, get_comparison and 10 more — is a fair guide to whether it matches your workflow. It is maintained by recon-fuzz; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_glossary | query: string |
| get_blog_post | slug: string |
| get_comparison | slug: string |
| search_site | query: string |
| list_tools | _(none)_ |
| get_book_chapter | slug: string |
| get_book_concept | slug: string |
| search_book | query: string |
| list_book_chapters | _(none)_ |
| get_substack_post | slug: string |
| search_substack | query: string |
| list_substack_posts | _(none)_ |
| Cursor | No API key needed. The server fetches public documentation only. |
{
"mcpServers": {
"recon-mcp-knowledge": {
"command": "npx",
"args": ["-y", "@recon-fuzz-mcp/knowledge"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.