Research MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_TOKEN | Yes | Your Notion API token obtained from Notion Integrations | |
| NOTION_ROOT_DATABASE_ID | Yes | The ID of your Notion database (the last part of the database page URL) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_survey_summariesC | Get survey summaries |
| get_survey_summaryD | Get survey summary |
| get_property_definitionB | Get property definition for survey summary |
| update_survey_summary_propertyC | |
| update_survey_summary_blockD | – |
| create_new_survey_summaryD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| survey |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools are mostly distinct with clear purposes: creating, getting, and updating survey summaries, plus a property definition tool. However, 'get_survey_summaries' and 'get_survey_summary' could be slightly confusing due to similar names, but their descriptions clarify one fetches multiple summaries and the other a single one. No major overlap exists between other tools.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as 'create_new_survey_summary' and 'update_survey_summary_property'. The only minor deviation is 'get_property_definition' which uses a slightly different noun structure compared to others, but it still fits the overall pattern well.
With 6 tools, this server is well-scoped for managing survey summaries in a research context. The count is appropriate, covering core operations like create, get, and update without being overwhelming or too sparse, making it efficient for agents to handle typical workflows.
The server provides good coverage for survey summary operations, including create, get, and update functions. However, there is a notable gap: no delete tool is present, which could limit full lifecycle management. Additionally, while property handling is included, the lack of a delete operation for survey summaries reduces completeness for CRUD workflows.