Skip to main content
Glama
MCP Private GitHub Search

MCP Private GitHub Search

npm version

Obsidian GitHub MCP

A Model Context Protocol (MCP) server that connects AI assistants to GitHub repositories containing Obsidian vaults. This server enables seamless integration with your knowledge base stored on GitHub, allowing AI assistants to read, search, and analyze your Obsidian notes and documentation.

Why This Tool?

Many Obsidian users store their vaults in GitHub for backup, versioning, and collaboration. This MCP server bridges the gap between your GitHub-hosted Obsidian vault and AI assistants, enabling:

  • Knowledge Base Access: Retrieve specific notes and documents from your Obsidian vault

  • Intelligent Search: Find relevant content across your entire knowledge base

  • Evolution Tracking: See how your ideas and notes have developed over time

  • Task Integration: Connect with issues and project management workflows

Related MCP server: GitHub Integrated MCP Server

Features

  • GitHub Repository Access: Connect to any GitHub repository containing your Obsidian vault

  • Type-Safe Implementation: Written in TypeScript with comprehensive type definitions

  • Input Validation: Robust validation for all API inputs using Zod schemas

  • Error Handling: Graceful error handling with informative messages

  • MCP Integration: Full compatibility with Claude, Cursor, Windsurf, Cline, and other MCP hosts

Available Tools

Knowledge Base Access

  • getFileContents: Retrieve the contents of specific notes, documents, or files from your Obsidian vault

  • searchFiles: Enhanced search with multiple modes:

    • filename: Find files by exact filename (perfect for "OKR 2025" type searches)

    • path: Search anywhere in file paths

    • content: Search within file contents

    • all: Comprehensive search across filenames, paths, and content

Project Management Integration

  • searchIssues: Search for issues and discussions related to your knowledge base projects

  • getCommitHistory: Track how your knowledge base has evolved over time with detailed commit history and diffs

Use Cases

For Knowledge Workers

  • Research Assistant: AI can access your research notes and reference materials

  • Writing Support: Pull relevant background information from your knowledge base

  • Idea Development: Track how concepts have evolved across your notes

For Developers

  • Documentation Access: Retrieve project documentation and technical notes

  • Learning Journals: Access your learning notes and code examples

  • Project Planning: Integrate with GitHub issues for comprehensive project management

For Students & Academics

  • Study Materials: Access lecture notes and study guides

  • Research Papers: Retrieve research notes and citations

  • Collaboration: Work with shared knowledge bases stored in GitHub

Installation

The easiest way to install Obsidian GitHub MCP is using Smithery:

# For Claude Desktop
npx -y @smithery/cli install @Hint-Services/obsidian-github-mcp --client claude

# For Cursor
npx -y @smithery/cli install @Hint-Services/obsidian-github-mcp --client cursor

# For Windsurf
npx -y @smithery/cli install @Hint-Services/obsidian-github-mcp --client windsurf

# For Cline
npx -y @smithery/cli install @Hint-Services/obsidian-github-mcp --client cline

Manual Installation

npm install obsidian-github-mcp

Configuration

Add the server to your MCP settings file with the following configuration:

{
  "mcpServers": {
    "obsidianGithub": {
      "command": "npx",
      "args": ["-y", "obsidian-github-mcp"],
      "env": {
        "GITHUB_TOKEN": "your-github-token",
        "GITHUB_OWNER": "your-github-username",
        "GITHUB_REPO": "your-obsidian-vault-repo"
      }
    }
  }
}

Required Environment Variables

  • GITHUB_TOKEN: Your GitHub personal access token (create one here)

  • GITHUB_OWNER: The owner/organization of the GitHub repository

  • GITHUB_REPO: The name of the repository containing your Obsidian vault

GitHub Token Permissions

Your GitHub token needs the following permissions:

  • repo (for private repositories) or public_repo (for public repositories)

  • read:org (if accessing organization repositories)

Example Workflows

Accessing Your Daily Notes

{
  "tool": "getFileContents",
  "arguments": {
    "filePath": "Daily Notes/2024-01-15.md"
  }
}

Finding Files by Name (Perfect for "OKR 2025" example!)

{
  "tool": "searchFiles",
  "arguments": {
    "query": "OKR 2025",
    "searchIn": "filename"
  }
}

Finding Files by Path

{
  "tool": "searchFiles",
  "arguments": {
    "query": "Daily Notes",
    "searchIn": "path"
  }
}
{
  "tool": "searchFiles",
  "arguments": {
    "query": "machine learning algorithms",
    "searchIn": "content",
    "perPage": 10
  }
}

Comprehensive Search (Filename, Path, and Content)

{
  "tool": "searchFiles",
  "arguments": {
    "query": "project planning",
    "searchIn": "all"
  }
}

Advanced GitHub Search Syntax

{
  "tool": "searchFiles",
  "arguments": {
    "query": "path:*.md extension:md",
    "searchIn": "content"
  }
}

Tracking Knowledge Evolution

{
  "tool": "getCommitHistory",
  "arguments": {
    "days": 30,
    "includeDiffs": true,
    "maxCommits": 10
  }
}

Search Tips & Troubleshooting

Can't Find Your File by Name?

Problem: Searching for "OKR 2025" doesn't find your file named "OKR 2025.md"

Solution: Use the searchIn: "filename" parameter:

{
  "tool": "searchFiles",
  "arguments": {
    "query": "OKR 2025",
    "searchIn": "filename"
  }
}

Advanced Search Techniques

  1. Exact Phrases: Use quotes for multi-word searches

    {
      "query": "\"project planning 2025\"",
      "searchIn": "content"
    }
  2. File Extensions: Find specific file types

    {
      "query": "path:*.md",
      "searchIn": "content"
    }
  3. Directory Specific: Search within folders

    {
      "query": "path:\"Daily Notes/\"",
      "searchIn": "content"
    }

Project Structure

obsidian-github-mcp/
├── src/
│   ├── index.ts          # Main MCP server entry point
│   └── github/           # GitHub API integration
│       ├── client.ts     # GitHub client implementation
│       └── types.ts      # TypeScript type definitions
├── docs/                 # Documentation
├── package.json          # Project configuration
└── tsconfig.json         # TypeScript configuration

For Developers

If you're interested in contributing to this project or developing your own tools with this server, please see the Development Guide.

Development Commands

  • pnpm install - Install dependencies

  • pnpm run build - Build the project

  • pnpm run dev - Run in development mode with inspector

  • pnpm run inspector - Launch MCP inspector for testing

If you're migrating from the older mcp-private-github-search package:

  1. Update your package name in configuration:

    {
      "mcpServers": {
        "obsidianGithub": {
          "command": "npx",
          "args": ["-y", "obsidian-github-mcp"]
        }
      }
    }
  2. The functionality remains the same - all existing tools work identically

  3. Consider the new Obsidian-focused use cases and workflows

Learn More

For further information on the MCP ecosystem, refer to:

About Hint Services

"The future is already here, it's just unevenly distributed"

— William Gibson, Author

Hint Services is a boutique consultancy with a mission to develop and expand how user interfaces leverage artificial intelligence technology. We architect ambition at the intersection of AI and User Experience, founded and led by Ben Hofferber.

We offer specialized AI workshops for design teams looking to embrace AI tools without becoming developers. Learn more about our training and workshops.

Available Tools

4 tools
getCommitHistoryB

Track the evolution of your Obsidian vault knowledge base by retrieving commit history from GitHub (johndoe-org/obsidian-vault). See how your notes and ideas have developed over time with detailed diffs.

Inputs: days (required), author, includeDiffs, maxCommits, +1 more.

getFileContentsC

Retrieve the contents of a specific note, document, or file from your Obsidian vault stored in GitHub (johndoe-org/obsidian-vault). Perfect for accessing your knowledge base content.

Inputs: filePath (required).

searchFilesB

Search for notes, documents, and files within your Obsidian vault on GitHub (johndoe-org/obsidian-vault). Find specific knowledge base content using GitHub's powerful search syntax. Supports searching in filenames, paths, and content.

Inputs: query (required), page, perPage, searchIn.

searchIssuesB

Search for issues and discussions in your Obsidian vault repository (johndoe-org/obsidian-vault). Great for tracking tasks, project management, and collaborative knowledge work.

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getCommitHistory retrieves commit history, getFileContents fetches specific file contents, searchFiles searches for files, and searchIssues searches for issues. There is no overlap in functionality, making tool selection unambiguous.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (getCommitHistory, getFileContents, searchFiles, searchIssues) with all tools using camelCase. However, 'searchFiles' and 'searchIssues' use plural nouns while 'getCommitHistory' and 'getFileContents' use singular or compound nouns, showing a minor deviation in noun consistency.

    Tool Count4/5

    With 4 tools, the count is appropriate for the server's purpose of interacting with a specific GitHub repository for an Obsidian vault. It covers key operations like retrieving history, files, and searching, though it might benefit from additional tools for actions like creating or updating issues or files to be more comprehensive.

    Completeness3/5

    The tool set provides good read/search capabilities for commits, files, and issues, but lacks write operations (e.g., create/update issues, commit changes, modify files). For a GitHub-focused server, this is a notable gap that could limit agent workflows, especially for collaborative or dynamic tasks.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      C
      quality
      Not graded
      maintenance
      A Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      MCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.
      15
      6 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude to directly interact with GitHub, including repos, files, branches, issues, pull requests, Actions, and code search using a personal access token.
      26
      295 npm
      1
      MIT