Skip to main content
Glama
msicilia

mcp-server-redcap

by msicilia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-server-redcap

No user-submitted related servers found.

    Related Servers

    • Redash MCP Server

      jasonsmithj
      A
      license
      B
      quality
      B
      maintenance
      Enables interaction with Redash instances through a standardized interface, allowing users to execute SQL queries, manage data sources, and retrieve query results using natural language.
      4
      3,371 npm
      1
      MIT

    • FHIR MCP Server

      the-momentum
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.
      13
      102
      MIT

    • FHIR MCP Server

      zachary55984
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents to interact with FHIR-compliant backends through natural-language prompts, supporting CRUD operations on clinical resources, document ingestion, semantic search, and LOINC terminology lookup.
      -

    • FHIR MCP Server

      IsabelaReddy
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to query and manipulate clinical data on a FHIR-compliant backend through natural-language prompts, including CRUD operations, document ingestion, semantic search, and LOINC terminology lookup.
      -

    • FHIR MCP Server

      EmmaEsposito50
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to query and manipulate FHIR-compliant clinical data through natural-language prompts, supporting CRUD operations, document ingestion, semantic search, LOINC lookup, and secure FHIR API integration.
      -
    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.9/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with the export_* family differentiated by target (records, report, files, PDF, arms, events, surveys). A few pairs like get_project_info vs get_project_structure could initially confuse agents, but their descriptions separate metadata from structural overview.

    Naming Consistency5/5

    All 38 tools follow a consistent verb_noun pattern using lowercase with underscores (e.g., delete_file, get_metadata, import_records). There are no mixed naming conventions or vague verbs, making the API highly predictable.

    Tool Count4/5

    38 tools is a substantial surface, but it maps to the full breadth of REDCap functionality (records, files, metadata, instruments, arms, events, surveys, project structure). Each tool has a specific job, and the count feels justified for a comprehensive integration, though it borders on heavy.

    Completeness4/5

    The tool set covers the core REDCap workflows: record CRUD, file attachments, data dictionary editing, instrument/event management, longitudinal arms/events, and survey links. Obvious gaps include user/role management and project-level settings updates, but these are peripheral to most programmatic REDCap interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources