Developer · Local MCP server
Chaprola
Serverless API backend: query, JOIN, pivot, batch ops, email, FHIR, programs via HTTP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.cletcher/chaprola- Version
- 1.4.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-28
- Updated
- 2026-03-28
- Publisher
- cletcher (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/cletcher) · how
- Listed under
- Email MCP servers
- Repository
- github.com/cletcher/chaprola-mcp (folder mcp-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @chaprola/mcp-server | 1.4.3 | stdio |
How to connect Chaprola
Chaprola runs locally from a Node.js package published to the npm registry: @chaprola/mcp-server version 1.4.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @chaprola/mcp-server@1.4.3. It reads these environment variables: CHAPROLA_USERNAME (required) and CHAPROLA_API_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"chaprola": {
"command": "npx",
"args": [
"-y",
"@chaprola/mcp-server@1.4.3"
],
"env": {
"CHAPROLA_USERNAME": "<value>",
"CHAPROLA_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChangegamerAgent-first resource directory for AI agents: protocols, security, RAG, memory, evals, and more. | Remote · HTTPLive check: ✓ handshake |
| Changelog Forge MCPGenerate changelogs from git commit history. | Local · stdio |
| changelogaiGenerate changelogs and suggest semver bumps from git history. | Local · stdio |
| ChapaRead, compare, and verify public developer impact profiles and Chapa badges. | Remote · HTTPLive check: ✓ handshake |
| chargehandRuns coding-agent workers on a codebase question; every claim in the answer carries evidence. | Local · stdio |
| ChargerDojoOCPI versions, what changed between them, and which modules and journeys ChargerDojo tests. | Remote · HTTPLive check: ✓ handshake |
| ChartwireGenerate chart code (Recharts, Chart.js, ECharts, Plotly) from a prompt. | Remote · HTTPLive check: sign-in required |
| ChassisScaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end. | Local · stdio |