Chaprola

io.github.cletcherPublished by GitHub account cletcherv1.4.3Updated Oct 25, 2026

Serverless API backend: query, JOIN, pivot, batch ops, email, FHIR, programs via HTTP.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Chaprola is a local MCP server that gives an assistant HTTP access to a serverless API backend for querying, joining, pivoting and batch operations.

What you can do
Query data through the Chaprola serverless API backend over HTTP, including JOIN and pivot operations across datasets. Run batch operations against the backend. Work with email and FHIR data through the same API. Invoke programs exposed by the backend. The manifest lists no individual tools, so exact capabilities follow the backend's API.
When to use it
Add it when you already use the Chaprola serverless API backend and want an assistant to query, join, pivot or batch-process that data, including email or FHIR records, from a local session.
Requirements
Runs as a local stdio process from the npm package @chaprola/mcp-server, so Node.js is needed. Requires a Chaprola account: a username in CHAPROLA_USERNAME and an API key in CHAPROLA_API_KEY. Network access to the Chaprola API is required. Desktop only.
Before you install
The API key in CHAPROLA_API_KEY is a secret and should be kept out of shared configuration. Batch operations and program invocation may write to or change backend data, so review what the assistant sends. Data, including email and FHIR records, is sent to the third-party Chaprola API over HTTP.

Installation

In SourceWeft

  1. Open Chaprola in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.3LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts