Skip to main content
Glama
h-yanagawa

Research MCP Server

by h-yanagawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Research MCP Server

No user-submitted related servers found.

    Related Servers

    • NotionMCP Server

      tleeds1
      F
      license
      Not graded
      quality
      D
      maintenance
      A Python server that integrates MCP with Notion to automate documentation workflows and manage Notion pages via LLMs, supporting operations like creating, updating, and searching Notion content.
      1
      -

    • Notion MCP Server

      snowan
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that connects to the Notion API and exposes functionality through Claude's Machine Context Protocol, enabling search, retrieval, querying, and creation of Notion pages and databases.
      2,184 npm
      MIT

    • Notion MCP Server

      hyunseok-ctrl
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables natural language interaction with the Notion API, allowing users to search, comment, create pages, and access content within their Notion workspace.
      152,494 npm
      -

    • Fourth Brain Demo

      Rev4nchist
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude.ai to a Notion-based marketing knowledge base, enabling search and retrieval across specialized domains like enterprise platforms and competitive positioning. It provides tools for RAG-style Q\&A and content browsing to assist with drafting RFPs and value propositions.
      1
      -
    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

    C2.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources