Skip to main content
Glama
72,476 servers. Updated

Matching MCP tools:

Matching MCP Connectors:

"MDX" matching MCP servers:

  • A
    license
    -
    quality
    -
    maintenance
    Provides semantic search over ScriptingApp documentation by converting Markdown/MDX files into a LlamaIndex vector store. Supports multi-language indexing and enables natural language queries against technical documentation through MCP tools.
    2
  • A
    license
    -
    quality
    D
    maintenance
    Enables semantic search and retrieval over local Markdown/MDX documentation using Node.js-based embeddings. Supports multi-language documentation with offline vector indexing and MCP tool exposure for AI assistants.
    32
    3
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Transforms complex Pega Platform interactions into intuitive, conversational experiences by exposing Pega DX APIs through the standardized Model Context Protocol, enabling AI applications to interact with Pega through natural language.
    67
    43
    21
    Apache 2.0
  • A
    license
    -
    quality
    D
    maintenance
    Connect any AI agent to M3X — the private pool matching protocol for agent-to-agent deal flow. Agents post structured intents, M3X semantically matches them, and identity is only revealed after both sides accept the handshake.
    MIT
  • A
    license
    -
    quality
    D
    maintenance
    Provides long-term memory for AI coding agents, enabling them to remember, search, and organize information across sessions and platforms like Claude Code, ChatGPT, and Cursor.
    23
    7
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    Exposes locally hosted MLX models as MCP tools for Claude Desktop and Codex, with optional SearXNG search augmentation for private local inference.
    MIT
  • F
    license
    -
    quality
    -
    maintenance
    A minimal, well-structured MCP server implementation for learning and experimentation that exposes three tools: web search, API search, and client ID processing. It demonstrates clean separation between tool, transport, and LLM layers while supporting multiple AI clients through the Model Context Protocol standard.