Skip to main content
Glama
Spider-Chat

spiderchat-mcp-server

Official
by Spider-Chat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to spiderchat-mcp-server

No user-submitted related servers found.

    Related Servers

    • OmniContext

      h4sht
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude Desktop to Notion and YouTube transcripts with one-click installation, enabling natural language queries about your pages and video content.
      5
      2
      MIT

    • Claude RAG MCP Pipeline

      kenjisekino
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to search and query personal document collections (PDF, Word, Markdown, text) using semantic search and conversational AI with full context preservation across exchanges.
      MIT

    • cowork-history

      egoughnour
      A
      license
      B
      quality
      C
      maintenance
      Enables searching and browsing of Claude conversation history with hybrid search combining full-text, Spotlight, and optional vector embeddings.
      10
      1
      MIT

    • Neuro MCP V2

      Arks-06
      F
      license
      A
      quality
      C
      maintenance
      Supercharges Claude Desktop with persistent semantic memory, sandboxed file I/O, live web search, and local emotional intelligence using a local ChromaDB and Hugging Face model.
      6
      -

    • quarry

      punt-labs
      A
      license
      A
      quality
      A
      maintenance
      Enables local semantic search over documents and code for Claude Code and Claude Desktop, running entirely offline with local embeddings and vector storage.
      12
      3
      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 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (search_flows, search_memories, search_facts target different resources; unified_search is a combined search). However, get_flow_group and list_flows_in_group both relate to group contents and could be confused, though descriptions differentiate the group details from the list of flows.

    Naming Consistency4/5

    Tool names mostly follow a verb_noun pattern with snake_case (search_flows, get_flow_nodes, list_flow_groups). The exception is unified_search, which uses an adjective instead of a verb, creating a minor inconsistency.

    Tool Count5/5

    8 tools is well within the ideal range for a focused MCP server. Each tool covers a distinct need (searching, listing, retrieving), and there is no redundancy or excessive fragmentation.

    Completeness3/5

    The tool surface covers search and browsing well, with flows, memories, facts, and group navigation. However, there is no direct retrieval by ID for memories or facts, no way to list all flows without going through groups, and no create/update/delete operations, which limits full lifecycle coverage if such functionality is expected.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources