MCP.so
Sign In

Experimental MCP Server for CommCare Connect (ccc)

@dimagi

Basic information

Category

Other

License

MIT license

Transports

stdio

Author

dimagi

About Experimental MCP Server for CommCare Connect

A proof of concept demo of an MCP server for CommCare Connect

#commcare#mcp#server

Experimental MCP Server for CommCare Connect config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Experimental MCP Server for CommCare Connect tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Experimental MCP Server for CommCare Connect (ccc)?

This experimental MCP server integrates with CommCare Connect's global stats API, allowing Claude Code and other MCP clients to query program dashboard data. It is built on the Python MCP SDK and is intended for developers and administrators who need programmatic access to earned amounts, paid amounts, active users, and visit statistics.

How to use Experimental MCP Server for CommCare Connect (ccc)?

To use it with Claude Code, run claude in the server folder. Modify the .mcp.json declaration for other tools. You need uv installed. Obtain an authentication token via the superuser admin page or a curl command with your username/password.

Key features of Experimental MCP Server for CommCare Connect (ccc)

  • Queries CommCare Connect’s global stats API
  • Filters by date ranges and program/organization IDs
  • Returns earned/paid amounts, active users, visit stats
  • Works with Claude Code and configurable for other MCP tools
  • Supports local development and staging environments

Use cases of Experimental MCP Server for CommCare Connect (ccc)

  • Monitor earned and paid amounts across programs and organizations
  • Track active user counts over custom date ranges
  • Retrieve visit statistics for program dashboards
  • Automate program reporting with natural language queries via Claude

Frequently asked questions

1

What can this MCP server query?

It queries the global stats API used by the program dashboard, returning amounts earned/paid, active users, and visit statistics. You can optionally filter by date ranges and specific program/organization IDs.

2

How do I get an authentication token?

As a superuser, visit `https://connect.dimagi.com/admin/authtoken/tokenproxy/` to find a token associated with your email. Alternatively, run `curl -X POST -d "username=you@dimagi.com&password=***" https://connect.dimagi.com/auth-token/` to create one.

3

What dependencies are required?

You need `uv` installed on your system. The server itself uses the Python MCP SDK.

4

Can I test against a development or staging server?

Yes. Change the `SERVER_ENDPOINT` in `.mcp.json` to `http://localhost:8000` or `https://connect-staging.dimagi.com/` and obtain a token from that environment.

5

Is this production‑ready?

No, it is explicitly experimental and built on the Python MCP SDK. Current functionality is limited to querying the global stats API.

Comments

More Other MCP servers