"Information about obsidian" 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.

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

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

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.

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.

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

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.

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.

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 agents to ask read-only questions about a repository's history through GitHub APIs, including blame, path history, merge base, PR association, diffs, and file contents, with aggressive caching and no clone required.

An MCP server that caches your GitHub starred repositories in a local SQLite database and lets you search, list, and retrieve details about them through any MCP client (Claude Desktop, Cursor, VS Code, etc.), with automatic freshness checks via GitHub's ETag mechanism.

MCP server integrating Google Search Console, Google Analytics 4, and GitHub, enabling AI clients to query search analytics, traffic data, and repository information.

MCP server that gives LLMs full visibility into your ws-cli workspace tree, enabling queries about workspaces, git status, tasks, and saved browser tabs.

Enables retrieving comprehensive information about GitLab merge requests, including details, commits, diffs, discussions, approvals, and CI/CD status, through natural language.

Enables AI assistants to answer questions about nixpkgs packages using nixkeeper's public data, covering outdated versions, Hydra build status and failures, update-bot attempts, related PRs and issues, CVEs, and what needs attention for a maintainer or team. It runs locally over stdio, reads only public data, and requires no account or token.

An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.

Provides natural language search capabilities for Spryker GitHub repositories, packages, and public documentation. It enables code-level searches across Spryker organizations to help developers find relevant modules and technical information.

Enables querying the latest commit information for any file in the Chromium repository, including commit hash, author, timestamp, message, and modified files through the Gitiles API.

A Model Context Protocol server that integrates Cursor IDE with Bitbucket Cloud, allowing developers to fetch repository information and commit data directly from their Bitbucket workspace.

Enables interaction with the Tembo API to manage organization tasks and view enabled code repositories. Users can create, search, and list tasks or retrieve account information directly through MCP-compatible clients.

Provides tools for accessing, comparing, and analyzing GitHub repository releases with rich formatting and detailed information.

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.

A Model Context Protocol server that enables integration with GitHub Actions, allowing users to fetch available actions, get detailed information about specific actions, trigger workflow dispatch events, and fetch repository releases.

An MCP server for gitingest. It allows MCP clients like Claude Desktop, Cursor, Cline etc to quickly extract information about Github repositories including repository summaries, project directory structure, file contents, etc

An MCP server that allows Claude and other MCP-compatible LLMs to interact with the GitHub API, supporting features like creating issues, getting repository information, listing issues, and searching repositories.

An MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.