Listed from the MCP registry; nobody on Odel publishes it.
FastMCP server for Obsidian wikilink suggestions from a pre-computed knowledge graph (graphify…
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Distributed as an MCP bundle (`https://github.com/adelaidasofia/graph-autotagger-mcp/releases/download/v0.1.0/graph-autotagger-mcp.mcpb`) — download it and import the bundle in your MCP client.
A FastMCP server that reads a pre-computed Obsidian knowledge graph and suggests wikilinks for your notes. Designed as a companion to graphify — run graphify to build the graph, then this MCP surfaces connections as you write.
| Tool | What it does |
|---|---|
suggest_links | Suggest wikilinks for a note based on token overlap with graph node labels |
check_god_nodes | Check which highly-connected nodes (top 20 by degree) are relevant to the note |
community_match | Find which graph communities the note most closely belongs to |
log_suggestion_decision | Log accepted/rejected/ignored decisions to a local SQLite database |
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/graph-autotagger-mcp
/plugin install graph-autotagger-mcp@graph-autotagger-mcp
After install, set GRAPH_JSON_PATH (see Environment variables below) and restart Claude Code, then ask:
"Suggest wikilinks for this note: [paste note content]"
Clone:
git clone https://github.com/adelaidasofia/graph-autotagger-mcp.git
cd graph-autotagger-mcp
Set the path to your graph.json:
export GRAPH_JSON_PATH="~/vault/.graph/graph.json"
Or pass it at registration time (see below).
Self-test (the launcher builds the environment from uv.lock on first run, downloading uv if needed):
sh bin/uv-run python server.py --self-test
Register with Claude Code:
claude mcp add graph-autotagger -s user -- \
env GRAPH_JSON_PATH="$HOME/vault/.graph/graph.json" \
sh /path/to/graph-autotagger-mcp/bin/uv-run python /path/to/graph-autotagger-mcp/server.py
Restart Claude Code, then ask:
"Suggest wikilinks for this note: [paste note content]"
| Variable | Default | Description |
|---|---|---|
GRAPH_JSON_PATH | ~/vault/.graph/graph.json | Path to your graphify output |
AUTOTAGGER_DB | ~/.config/graph-autotagger/log.db | SQLite log for suggestion decisions |
The server loads graph.json once at startup and caches it in memory. Node labels are tokenized and matched against note content using token overlap scoring. God Nodes (top 20 by degree) get special treatment since connecting to them creates high-value cross-links.
The log_suggestion_decision tool lets you build a feedback dataset over time: accepted suggestions can be used to tune the relevance threshold; rejected ones reveal graph noise.
Expects the output format from graphify (networkx node_link_data):
{
"nodes": [{"id": "node-id", "label": "Node Label", "community": 0}],
"links": [{"source": "node-a", "target": "node-b"}]
}
Note: networkx serializes edges under "links", not "edges".
Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):
This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.
What is sent:
slack-mcp)0.1.0)What is NOT sent:
Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.
Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.
MIT
Built by Mycelium AI. Full install or team version at diazroa.com.