mcp server
kObsidian
Filesystem-first MCP for Obsidian — an LLM-maintained wiki inspired by Karpathy's LLM Wiki.
Description as published by the maintainer. Source
- version 0.2.1
- active
active — Most recent push to the repository was 2026-07-16.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 6 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-16 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-23 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-04-23 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.aahlijia/dekko
— last commit 2026-08-06, shares codebase-indexing
Static code map generator: MAP.md + map.json for any repo, plus a Claude Code /map plugin
-
Fodda Brand Intelligence
— last commit 2026-08-06, shares research
Brand health & trend footprint across PSFK expert graphs with citable sources, not web summaries.
-
Fodda Deep Research
— last commit 2026-08-06, shares research
Autonomous deep research reports merging PSFK trend graphs with citable sources.
-
Fodda Earnings Intelligence
— last commit 2026-08-06, shares research
Cross-company earnings trends & executive divergence with citable sources.
-
Fodda Synthetic Expert Consult
— last commit 2026-08-06, shares research
Consult synthetic industry experts grounded in PSFK trend graphs with citable sources.
-
Fodda Knowledge Graphs
— last commit 2026-08-06, shares research
Expert-curated knowledge, brand, research & earnings intelligence — 31 tools, 220+ graphs.
-
Fodda Topic & Trend Research
— last commit 2026-08-06, shares research
Trend, stats & insight search across PSFK expert graphs with citable sources.
-
Conference Partner
— last commit 2026-08-06, shares research
Academic conference & journal CFP deadlines, CCF/ICORE/QUALIS rankings, acceptance rates.
-
com.nobleblocks/nobleblocks-mcp
— last commit 2026-06-08, shares research
Search 340M+ academic papers — citation graphs, semantic similarity, and AI literature reviews.
-
Egypt Research Commons
— last commit 2026-07-20, shares research
Source-grounded research for Egyptian public affairs
These share tags the maintainers applied themselves, such as codebase-indexing, research. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: codebase-indexing, llm-wiki, obsidian, obsidian-mcp, research.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab