spiderchat-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPIDERCHAT_API_URL | Yes | Spider Chat API URL (default: https://nonlinearaichat-production.up.railway.app) | |
| SPIDERCHAT_API_TOKEN | Yes | Your Spider Chat API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flowsB | Search flows by name, description, or tags |
| search_memoriesC | Semantic search in memories |
| search_factsC | Search user facts |
| get_flow_nodesB | List all nodes in a specific flow |
| list_flow_groupsA | List all flow groups (folders) to understand the organizational structure |
| get_flow_groupA | Get details of a specific flow group including its flows and subgroups |
| list_flows_in_groupA | List all flows in a specific group, optionally including nested subgroups |
| unified_searchB | Search across flows, memories, and facts simultaneously |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.