Skip to main content
Glama
Kailash-Sankar

PocketMCP

by Kailash-Sankar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to PocketMCP

No user-submitted related servers found.

    Related Servers

    • knowledgine

      3062-in-zamud
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first MCP server that extracts structured knowledge from markdown notes into SQLite with full-text search, enabling AI coding tools to retrieve relevant context offline at zero cost.
      3
      MIT

    • rag-mcp

      MasihMoafi
      A
      license
      Not graded
      quality
      B
      maintenance
      A local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.
      5
      MIT

    • freshvault

      KIOKO-LAB
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides always-fresh semantic search over Obsidian vaults, automatically watching file changes and using local embeddings via Ollama.
      56 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: delete_documents removes documents, list_documents retrieves them, search finds similar content, and upsert_documents inserts or updates. An agent can easily tell them apart based on their specific actions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., delete_documents, list_documents, upsert_documents), with 'search' as a slight deviation that still fits semantically. The naming is predictable and readable throughout.

    Tool Count5/5

    With 4 tools, the server is well-scoped for document management, covering core operations like listing, searching, upserting, and deleting. Each tool earns its place without being too sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for basic document CRUD and search operations, but lacks explicit tools for actions like retrieving a single document by ID or updating metadata, which could be minor gaps agents might need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources