Obsidian GitHub MCP

What this does

Obsidian GitHub MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

VAULT_MCP_PORT
VAULT_MCP_GITHUB_OWNER
VAULT_MCP_GITHUB_REPO
VAULT_MCP_POLICY_FILE
VAULT_MCP_TOKEN_FILE
GITHUB_TOKEN
GITHUB_APP_ID
GITHUB_APP_INSTALLATION_ID
GITHUB_APP_PRIVATE_KEY_FILE

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Obsidian GitHub MCP?

Run the Claude Code command in the install section to add Obsidian GitHub MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Obsidian GitHub MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Obsidian GitHub MCP as well.

Does Obsidian GitHub MCP need an API key?

Yes. Before it can run, set these environment variables: VAULT_MCP_PORT, VAULT_MCP_GITHUB_OWNER, VAULT_MCP_GITHUB_REPO, VAULT_MCP_POLICY_FILE, VAULT_MCP_TOKEN_FILE, GITHUB_TOKEN, GITHUB_APP_ID, GITHUB_APP_INSTALLATION_ID, GITHUB_APP_PRIVATE_KEY_FILE. They go in the env block of your MCP config.