MCP Private GitHub Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPO | Yes | The name of the repository containing your Obsidian vault | |
| GITHUB_OWNER | Yes | The owner/organization of the GitHub repository | |
| GITHUB_TOKEN | Yes | Your GitHub personal access token (create one here: https://github.com/settings/tokens) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.