Skip to main content
Glama
Brian20040323

MCP Knowledge Bridge

Related Servers

Alternatives to MCP Knowledge Bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Cross-agent memory bridge for AI coding assistants. Persistent knowledge graph shared across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. 22 tools including team collaboration, auto-cleanup, mini-skills, session management, and workspace sync. 100% local, zero API keys required.
      9
      23,392 npm
      761
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      MCP-native persistent memory layer for AI agents across Claude Code, Cursor, VS Code, and OpenClaw. Powered by hybrid vector search, BM25, and cross-encoder reranking with a published 73.1% LoCoMo benchmark accuracy.
      8
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local-first knowledge backend for AI agents that connects MCP hosts to an Obsidian-compatible vault with indexed retrieval, token-budgeted memory recall, and secure ingestion.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A fully local MCP server that imports Markdown, PDF, and web pages into a running knowledge base, providing hybrid search and document retrieval via authenticated Streamable HTTP for Codex and DeepSeek agents.
      -
    • A
      license
      B
      quality
      A
      maintenance
      Universal documentation knowledge-graph MCP server with hybrid full-text + vector search. Indexes local files and remote sources from Notion, Jira, Obsidian, Linear, GitHub, and Confluence into a single SQLite knowledge graph, exposing it to AI agents via the Model Context Protocol.
      10
      10 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search, fetch by ID, compare two topics, and a debug echo. No overlap in functionality.

    Naming Consistency3/5

    Three tools follow the 'kb_' prefix with verbs, but 'echo_debug' breaks the pattern by omitting the prefix. Mixed conventions reduce consistency.

    Tool Count5/5

    Four tools is well within the typical 3-15 range and feels appropriate for a focused knowledge bridge server.

    Completeness2/5

    Only read and compare operations are present. Missing create, update, and delete for knowledge entries, which are essential for managing a knowledge base.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues