Submit ECG images to ARPI’s ECG AI and retrieve generated diagnosis reports through a remote MCP endpoint.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by ARPI MCP.
authenticateSign in to ARPI
open_image_submissionStart an ECG image submission
submit_image_for_diagnosisSubmit an ECG image for AI diagnosis
fetch_diagnosis_reportsRetrieve diagnosis reports
list_available_capabilitiesList available analysis capabilities
invoke_arpi_capabilityInvoke a specific analysis capability
The ARPI MCP MCP server exposes ARPI’s ECG AI through the Model Context Protocol. An MCP client can authenticate with ARPI, begin an ECG image submission, send the image for analysis, and retrieve generated diagnosis reports. The service also exposes capability discovery and a general operation for invoking a named ARPI analysis capability.
This is a remote service rather than a server that runs from the repository. The repository contains registry and marketplace metadata, including the official MCP Registry entry and Claude Code plugin files. The hosted MCP endpoint is operated by ARPI at https://mcp.arpi.ai/mcp.
The ARPI MCP MCP server communicates over Streamable HTTP. Authentication uses OAuth, and the MCP client guides the user through ARPI login during the first connection. After authentication, the client can use the image-submission workflow and retrieve reports through the exposed tools.
The typical workflow is to start an image submission, submit an ECG image for diagnosis, and fetch the resulting reports. Clients can also query the analysis capabilities available to the authenticated account and invoke a specific capability when that is appropriate.
No local package or process is described for the MCP server itself. Configure an MCP client to use this endpoint:
Claude Code can register it with the HTTP transport using:
The repository also provides a Claude Code marketplace option. Add the arpi-ai/arpi-mcp marketplace and install the arpi-mcp@arpi-mcp plugin. In Claude.ai or Claude Desktop, add a custom connector with the same endpoint. Other clients need to support both Streamable HTTP and OAuth.
The available tools are:
authenticate: Sign in to ARPI.open_image_submission: Begin an ECG image submission.submit_image_for_diagnosis: Send an ECG image for AI diagnosis.fetch_diagnosis_reports: Retrieve diagnosis reports.list_available_capabilities: View available analysis capabilities.invoke_arpi_capability: Invoke a selected ARPI capability.Together, these tools cover authentication, ECG image analysis, report retrieval, and access to ARPI’s advertised capabilities. The material does not specify image formats, report schemas, response times, or the names of individual capabilities.
The ARPI MCP MCP server connects to a medical AI service. Its diagnosis reports are intended for reference and must not be treated as a replacement for professional medical judgment. The README does not document local hosting, environment variables, configurable options, rate limits, supported image formats, or data-retention behavior.
Because the service is remote, availability and authentication depend on ARPI’s hosted endpoint and OAuth flow. Support is provided by ARPI at support@arpi.ai.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/arpi-mcp)<a href="https://allmcps.com/mcp/arpi-mcp"><img src="https://allmcps.com/api/badge/arpi-mcp?style=directory" alt="ARPI MCP on AllMCPs" /></a>