Skip to main content
Glama
oksure

OpenAlex Research MCP Server

by oksure
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to OpenAlex Research MCP Server

No user-submitted related servers found.

    Related Servers

    • legal_scholarship_mcp

      MH-LT
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching scholarly literature via the OpenAlex database, with tools for full-text search, work details, citation lookup, and author queries.
      MIT

    • OpenAlex MCP Server

      reetp14
      A
      license
      B
      quality
      F
      maintenance
      Provides access to OpenAlex's catalog of 240M+ scholarly works, enabling search and retrieval of research papers, authors, institutions, journals, concepts, and funders with advanced filtering and classification capabilities.
      11
      42 npm
      5
      MIT

    • OpenAlex MCP Server

      NimaZahediN
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search and analyze OpenAlex scholarly database for OSINT research, including works, authors, institutions, funding, citations, and collaboration networks.
      MIT

    • ScholarScope MCP

      ErikNguyen20
      A
      license
      A
      quality
      D
      maintenance
      Enables academic research through the OpenAlex API, allowing users to search for papers, authors, and institutions, retrieve citations, and fetch full-text content when available. Perfect for building intelligent research assistants that can explore academic literature and related works.
      8
      7
      MIT
    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

    A3.6/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., search_works vs. search_in_journal_list vs. get_work). A few pairs like get_work_citations and get_citation_network have slight overlap but descriptions clarify differences. Overall, agents can reliably select the right tool.

    Naming Consistency4/5

    Tool names follow a verb_noun pattern with consistent snake_case. Some verbs vary (search_, get_, find_, analyze_, check_, list_, batch_) but each name is descriptive and the pattern is predictable. Minor inconsistency: 'find_' vs 'get_' for similar actions.

    Tool Count3/5

    31 tools is on the high side for a single server. While the domain is broad (research analytics, author profiling, citation networks, venue quality), some tools could be merged (e.g., multiple search variants). The count feels heavy but not excessive given the scope.

    Completeness5/5

    The tool set covers the full research lifecycle: author discovery, work search, citation analysis, venue quality checks, trend analysis, and entity details. Key operations like CRUD are not applicable, but for analysis, it provides comprehensive coverage with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources