synapse-research
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Embeddings only (text-embedding-3-small) | |
| TAVILY_API_KEY | Yes | Web search | |
| ANTHROPIC_API_KEY | Yes | Claude LLM — planning + report writing |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_research_runB | Get a research_run by ID. IDs start with rr_. |
| list_research_runsA | List research_runs. Filters by status (default: active). Returns newest first. IDs start with rr_. |
| search_research_runsA | Search research_runs with text query and/or structured filters. Text query matches across all string fields (case-insensitive). Filters support: direct equality, $gt, $gte, $lt, $lte, $ne, $in, $contains, $exists. Sort with '-field' for descending. IDs start with rr_. |
| delete_research_runA | Delete a research_run by ID. Soft delete by default (sets status to 'deleted'). Set hard=true to permanently remove. IDs start with rr_. |
| add_fieldB | Add a new field to an entity schema. Validates the change is safe, writes the updated schema to disk, and reloads it. |
| rebuild_indexA | Force a full rebuild of the relationship index from entity files. Use this if the index seems stale or after manual file edits. |
| start_researchA | Run a research task on the given query. Supports MCP task augmentation — clients that advertise |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Context | App domain knowledge |
| research-runs | Skill: research-runs |
| research_ui | UI resource rendered in the platform sidebar. |
TDQS
Scored across 7 tools
Tools are mostly distinct: get, list, search, delete, start for research runs, plus add_field and rebuild_index for supporting operations. However, start_research and the list/search tools could cause some confusion, as start_research creates a run while list/search find existing ones.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_research_run, add_field). No mixing of conventions or vague verbs.
With 7 tools, the server is well-scoped for managing research runs and associated schema/index operations. Not too few or too many relative to the domain.
The server covers core operations for research runs (create via start_research, read via get/list/search, delete) but lacks an explicit update operation for runs. Schema management is limited to adding fields. This is a notable gap.