"A server for finding information about Obsidian, the note-taking app" matching MCP servers:

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.

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

Enables people to open a shared group chat as a card inside their own AI chat, where they and their AIs talk together and post, claim, and confirm tasks on a self-organizing board. Its tools also let any AI read the repository's code and submit a proposed change that becomes a pull request.

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.

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

Odds are, most of what you want to build is already open source. Tell your AI agent what you're making, and it finds it: which repos to use as they are, which to adapt, and what's left for you to write. Every repo it names is real, licensed for your use or flagged, and checked live.

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).

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 Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

. 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 '{

Self-hosted MCP coding server and unified local Control Center for ChatGPT web, enabling file editing, command execution, Git operations, and optional upstream MCP tools with conversation access controls.

Enables Codex agents to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail and next step, then append validated, audited, idempotent progress events that become matching project-record Git commits. Access is scoped to one workspace and project through short-lived, revocable, hash-stored credentials that cannot touch members, keys, deletion, publication or deployment.

It enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.

It lets AI coding clients read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append a validated, audited, idempotent progress event with a matching project-record Git commit.