research-assistant-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key for embeddings | |
| RESEARCH_DB_PATH | Yes | Base path for storing research databases. A 'research_chroma_dbs' directory will be created inside this path. |
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 | {
"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 |
|---|---|
| save_research_dataA | Save research content to vector database for future retrieval. Args: content: List of text content to save topic: Topic name for organizing the data (creates separate DB) |
| search_research_dataA | Search through saved research data using semantic similarity. Args: query: Search query topic: Topic database to search in max_results: Maximum number of results to return |
| list_research_topicsA | List all available research topics (vector databases). |
| delete_research_topicA | Delete a research topic and all its data. Args: topic: Topic name to delete |
| get_topic_infoA | Get detailed information about a research topic. Args: topic: Topic name to get info for |
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 5 tools
Each tool has a clearly distinct purpose: save, search, list, delete, and get info. There is no overlap or ambiguity between them.
Tool names follow a consistent verb_noun pattern (save, search, list, delete, get). Minor inconsistency: some use 'research_data' and others 'topic(s)', but the pattern is still predictable.
Five tools is well-scoped for a research assistant. Each tool covers a necessary function without redundancy or bloat.
Core lifecycle is covered: create (save), read (search, get_info, list), and delete (topic). Missing an update/edit tool, but for research data re-saving is a viable workaround.