FastMCP Server For Obsidian Wikilink Suggestions From A Pre Computed Knowledge G
Suggest Obsidian wikilinks from a pre-built vault graph so agents help you connect notes without manual backlink hunting.
Overview
graph-autotagger-mcp is a MCP server for the Build phase that suggests Obsidian wikilinks from a pre-computed graphify knowledge graph JSON file.
What is this MCP server?
- FastMCP server focused on Obsidian wikilink suggestions, not full vault editing
- Reads a pre-computed knowledge graph (graphify graph.json) for fast suggestions
- Requires GRAPH_JSON_PATH pointing at graphify-out/graph.json on disk
- stdio MCPB v0.1.0 with pinned release artifact
- Pairs with graph-query-mcp when you need lookup after tagging
- Server version 0.1.0 with stdio MCPB transport
- Single required env var GRAPH_JSON_PATH for graph JSON location
- Designed for pre-computed graphs from graphify-style pipelines
What problem does it solve?
Your vault grows faster than you can manually connect notes, so agents draft in isolation and your second brain stays disconnected.
Who is it for?
Obsidian power users who already run graphify (or similar) exports and want MCP-driven link suggestions during agent-assisted writing.
Skip if: Builders without an Obsidian vault, anyone expecting live vault scanning without a pre-built graph.json, or teams standardized on Notion-only docs.
What do I get? / Deliverables
With graph.json wired in, your agent can propose relevant wikilinks grounded in your existing graph instead of guessing related note titles.
- Agent-callable wikilink suggestions grounded in your vault graph
- Faster note linking workflow without manual backlink searches
Recommended MCP Servers
Journey fit
Documentation and second-brain vaults are maintained continuously during build, but link hygiene also supports early research and later content reuse. Docs is the primary shelf because the server targets Obsidian note graphs produced by graphify-style pipelines, not runtime app code.
How it compares
Graph-backed wikilink suggester MCP, not a full Obsidian plugin or a general RAG document loader.
Common Questions / FAQ
Who is graph-autotagger-mcp for?
Solo builders who maintain an Obsidian knowledge base and want their agent to suggest wikilinks using an offline graph exported from graphify.
When should I use graph-autotagger-mcp?
Use it while writing or refactoring notes whenever you want the agent to propose links to related vault pages without you searching manually.
How do I add graph-autotagger-mcp to my agent?
Generate graphify-out/graph.json, set GRAPH_JSON_PATH to its absolute path, install the v0.1.0 MCPB stdio release, and add the server to your MCP client configuration.