"Information about Obsidian (note-taking app or volcanic glass)" matching MCP servers:

An Obsidian plugin that runs an embedded MCP server inside Obsidian, exposing vault operations and optional GitHub integration to any MCP client.

Fetches public GitHub repositories and uses an LLM to generate a json-render UI specification.

This MCP server enables AI collaborators to read and write to a git-backed Obsidian vault with transactional integrity, ensuring every write is a validated, attributed commit pushed to the remote.

Multi-tenant remote MCP server that exposes any GitHub-backed Obsidian vault to any MCP client via OAuth authentication.

A Model Context Protocol server that gives AI agents bounded, auditable access to propose changes to an Obsidian vault stored in GitHub, with per-agent expiring tokens, read/write/deny path policies, mutability rules, frontmatter checks, and human-reviewed proposal branches.

Enables secure GitHub App authenticated Git operations and GitHub API workflows through MCP, using ephemeral containers and a private key broker to protect credentials.

A dockerised, self-hostable host that runs an Obsidian vault headlessly and serves it to MCP clients, with pluggable sync (git first).

Read and propose changes to an Obsidian vault through git-apply-able diffs, with a security model that prevents the AI from ever writing to the vault directly.

This MCP server bridges ChatGPT to GitHub, letting you use natural language to read repositories, modify code, create branches, and open pull requests while enforcing security policies like repository whitelists and branch protection.

Enables Claude to read, write, search, and manage Obsidian vault notes with Git-backed sync support for multi-device access and extensible AI workflows.

Git-backed MCP server for creating and maintaining an Obsidian-style markdown knowledge base with full CRUD, search, and git sync.

Enables GitHub MCP tools to target multiple GitHub App installations by selecting a repository, organization, or user scope per request.

A lightweight stdio-to-http relay that enables the GitHub MCP server to authenticate using a GitHub App instead of a Personal Access Token. It automatically manages fine-grained permissions and short-lived tokens for secure, organizational AI agent workflows.

An MCP server for small-scale iOS app development, providing safe Git/GitHub operations like release preparation, hotfixes, and PR creation with dry-run support.

Local code review for people and their coding agents: an agent opens a review of its changes and hands over a link, the person comments on lines, and the agent reads the threads, replies and resolves what it fixed. Reads the git worktree directly, uncommitted work included; nothing leaves the machine.

Deterministic code-churn measurement and AI-agent detection from the CodeDelta engine: measure churn between two directories or git refs, scan for code that runs AI agents, and get AI-authorship pointers. Runs fully locally.

A Model Context Protocol server that provides tools for searching private GitHub repositories, enabling access to repository files, commit history, and issues with automatic handling of rate limiting and error handling.

Enables AI agents to securely create and manage GitHub-to-Slack review routing setups through Tenpace, using OIDC-verified browser authorization and short-lived links.

Enables Claude to maintain a team knowledge base stored as markdown in a GitHub repository, with tools for search, edit, linking, and interactive views.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables querying any GitHub, GitLab, or Bitbucket repository and getting AI-generated answers about the codebase, powered by Gemini.

Enables asking natural-language questions about any GitHub repository and receiving answers grounded in the actual code, with read-only enforcement and automatic repository fetching.

Serves the review notes left at lines of a diff in seam, a terminal diff viewer, to an agent with the code around them. The agent answers each note, and the answer shows in seam at that line.

Generates a daily standup note from GitLab merge request or GitHub pull request state: what is ready to merge, what is blocked, what is stale, and what is waiting on your review. When CI is red it opens the failed job's log and reports the error lines, so the note says why the pipeline failed rather than just that it did.

Semantic git queries via MCP. Beyond git log — answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.

Enables natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.

Combines GitHub releases from multiple repositories into a single product release note, with context sources for LLM synthesis.

Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and INDEX.md) from GitHub repositories, enabling LLMs to answer questions about features, stories, and acceptance criteria without cloning or pasting files.

An MCP (Model Context Protocol) server for handling GitHub URLs with validation and parsing capabilities. This server provides tools to convert between GitHub repository information and URLs, with intelligent validation to distinguish between public repositories, private repositories, and non-exist

Enables AI assistants to turn local git history into answers about recent activity, file hotspots, change coupling, stale or already-merged branches, contributors, ref comparisons, and drafted release notes. It runs locally over stdio with a git subcommand allowlist, so it is read-only, works offline and without shell access, and is safe to auto-approve.