# Obsidian MCP server

> Search vaults, create notes, and maintain linked knowledge.

- Provider: Obsidian
- Category: Knowledge (https://mcpheaven.com/catalog/category/knowledge)
- Status: Planned
- Slug: `obsidian`
- Verified: 2026-11-10
- JSON: https://mcpheaven.com/api/v1/capabilities/obsidian
- HTML: https://mcpheaven.com/catalog/obsidian

## Why it is in the catalog

Common personal knowledge base with multiple community MCPs but no official vendor server.

## Questions

### Is there an official Obsidian MCP server?

Common personal knowledge base with multiple community MCPs but no official vendor server. mcpheaven lists Obsidian so agents can find it by task and reach it through one MCP endpoint.

### What can an AI agent do with Obsidian?

Search vaults, create notes, and maintain linked knowledge. Agents find it by describing the task, for example with the search_capabilities tool.

### How do I connect Obsidian to Claude, Codex or Cursor?

Add mcpheaven once as an MCP server (https://mcpheaven.com/mcp) with an API key, then ask your agent for the task. It calls get_capability with the slug "obsidian" for details.

### Is the Obsidian integration available?

The Obsidian integration is planned. Agents can already discover it through mcpheaven's search, and it will become callable once the integration ships.

## Connect

MCP endpoint: `https://mcpheaven.com/mcp` (Streamable HTTP, JSON-RPC). Without a key: public catalog, 120 calls per hour per address. With a key (`Authorization: Bearer mch_…`, free at https://mcpheaven.com/signup): plan quota and private capabilities.

```bash
claude mcp add --transport http mcpheaven https://mcpheaven.com/mcp --header "Authorization: Bearer mch_…"
```

```json
{ "mcpServers": { "mcpheaven": { "url": "https://mcpheaven.com/mcp", "headers": { "Authorization": "Bearer mch_…" } } } }
```

REST: `GET https://mcpheaven.com/api/v1/capabilities?q=<task>` · OpenAPI: https://mcpheaven.com/openapi.json · Server card: https://mcpheaven.com/.well-known/mcp.json