obsidian-mcp-server

Read, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.

Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 8ec39dc404f9

TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, ai tools, bun, cyanheads, knowledge base, mcp, mcp server and model context protocol.

obsidian-mcp-server runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed, project builds, all 2608 tests pass, and the server starts via stdio with 14 tools and 3 resources registered.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
716
forks
109
open issues
16
watchers
7
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
3 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
bun run build exited 0 (128 files, 834.3 KB); bun run test exited 0 (37 files, 2608 passed); bun ./dist/index.js --help started stdio transport with 14 tool/3 resource definitions
Model tokens used
41,040
Exact commit tested
8ec39dc404f9
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 Test Files  37 passed (37)
      Tests  2608 passed (2608)
   Start at  04:27:40
   Duration  19.48s (tests 70%, import 25%, transform 4%, worker 1%)
All systems are fully operational. Here's the summary:
The project works completely out of the box in this container. Bun 1.4.3 was installed via `npm ins…
No errors were encountered at any stage. The test suite uses a stub fetch layer injected into `Obsi…
tokens used
41,040
All systems are fully operational. Here's the summary:
The project works completely out of the box in this container. Bun 1.4.3 was installed via `npm ins…
No errors were encountered at any stage. The test suite uses a stub fetch layer injected into `Obsi…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Nothing broke on the way: zero errors between clone and running.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 3 minutes to install, slower than the median of the 26 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 27 ai-tools projects Argusic has installed and timed, obsidian-mcp-server was the 15th fastest to reach a running state, and 19 of 27 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.02

Topics (from GitHub)

ai-agentsai-toolsbuncyanheadsknowledge-basemcpmcp-servermodel-context-protocolnote-takingobsidianobsidian-mdobsidian-vaultpkmstdiostreamable-httptypescript

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/obsidian-mcp-server.svg)](https://argusic.com/subject/obsidian-mcp-server)

Questions

Does obsidian-mcp-server run?
obsidian-mcp-server runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test obsidian-mcp-server?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8ec39dc404f9. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test obsidian-mcp-server?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does obsidian-mcp-server take to install?
3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does obsidian-mcp-server need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing obsidian-mcp-server?
Nothing did, in the recorded run: zero errors between clone and running.
How does obsidian-mcp-server compare with the alternatives?
Of the 27 ai-tools projects Argusic has installed and timed, obsidian-mcp-server was the 15th fastest to reach a running state, and 19 of 27 reached one at all.
Where is the evidence for obsidian-mcp-server?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion