mirth_connect_mcp
MCP server for NextGen Connect (Mirth) that exposes API operations as domain-grouped tools.
Requirements
- Python 3.13+
- Reachable NextGen Connect API endpoint
- Credentials with API access
Install
Recommended (global command available in PATH):
uv tool install mirth_connect_mcp
Alternative:
pip install mirth_connect_mcp
After install, the command is:
mirth-connect-mcp
Environment variables
Required:
MIRTH_BASE_URL(example:https://localhost:8443/api)MIRTH_USERNAMEMIRTH_PASSWORD
Optional:
MIRTH_VERIFY_SSL(trueby default; setfalsefor local self-signed certs)MIRTH_TIMEOUT_SECONDS(30by default)MIRTH_OPENAPI_PATH(defaults to bundled OpenAPI spec)
Add to MCP clients
Use stdio transport for all client configs below.
VS Code (MCP)
Open your VS Code MCP config (mcp.json) and add:
{
"servers": {
"mirthNextgen": {
"type": "stdio",
"command": "mirth-connect-mcp",
"env": {
"MIRTH_BASE_URL": "https://localhost:8443/api",
"MIRTH_USERNAME": "admin",
"MIRTH_PASSWORD": "admin",
"MIRTH_VERIFY_SSL": "false"
}
}
}
}
Cline
In Cline MCP settings, add this server entry:
{
"mcpServers": {
"mirthNextgen": {
"command": "mirth-connect-mcp",
"args": [],
"env": {
"MIRTH_BASE_URL": "https://localhost:8443/api",
"MIRTH_USERNAME": "admin",
"MIRTH_PASSWORD": "admin",
"MIRTH_VERIFY_SSL": "false"
}
}
}
}
Claude Desktop
In claude_desktop_config.json, add:
{
"mcpServers": {
"mirthNextgen": {
"command": "mirth-connect-mcp",
"env": {
"MIRTH_BASE_URL": "https://localhost:8443/api",
"MIRTH_USERNAME": "admin",
"MIRTH_PASSWORD": "admin",
"MIRTH_VERIFY_SSL": "false"
}
}
}
}
Gemini CLI
In your Gemini CLI MCP config, add:
{
"mcpServers": {
"mirthNextgen": {
"command": "mirth-connect-mcp",
"env": {
"MIRTH_BASE_URL": "https://localhost:8443/api",
"MIRTH_USERNAME": "admin",
"MIRTH_PASSWORD": "admin",
"MIRTH_VERIFY_SSL": "false"
}
}
}
}
Tool model
Built-in tools:
list_domainslist_actions- One dispatch tool per OpenAPI domain/tag
Domain tool request envelope:
{
"action": "operationId",
"path_params": {},
"query": {},
"body": {},
"headers_override": {}
}
Metadata
Release files for mirth-connect-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mirth_connect_mcp-0.1.1.tar.gz | 48.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mirth_connect_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.4 kB
Release files / mirth_connect_mcp-0.1.1.tar.gz
| Download URL | mirth_connect_mcp-0.1.1.tar.gz |
|---|---|
| Size | 48.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
237ddc4643e4c8cc1b97eefe2dff53faf6696f5ee69e292c7beb430c7bb60498
|
|
BLAKE2b-256 checksum How to use checksums |
bba7977a182729439412406ce10f3541a74569bfd9a7e3fcafa111ea1bbe63e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logRelease files / mirth_connect_mcp-0.1.1-py3-none-any.whl
| Download URL | mirth_connect_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 49.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13a24dbd4871bd5e798dd184e241364204d2cbf279a52fce1db51aff05b0d878
|
|
BLAKE2b-256 checksum How to use checksums |
abb02186e154e3aa0e0c0fb66f6640c6da36fd00680a6e665a02a4ca675b0e08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logSecurity for mirth-connect-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mirth_connect_mcp-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.