Algenta MCP Server
Model Context Protocol server for Algenta — self-hosted building blocks for AI applications.
Any MCP-capable agent operates the engine — metered and audited like every other caller. This server gives MCP-compatible agents access to governed data discovery, exact queries, decisions, simulations, runtime utilities, and account operations through the same public API contract used by the Algenta SDKs. The Algenta engine itself is proprietary; everything in this package is Apache-2.0.
Full reference: docs.algenta.ai/sdk/mcp
Install
pipx install algenta-mcp
pip install algenta-mcp is also supported. The package includes its MCP transport dependencies;
users do not install or manage a separate protocol package.
Auth model
Introspection (initialize/tools/list) needs no credentials. Executing tools requires a free
community login — device registration at algenta.ai (free): run algenta login, or create a key
at https://app.algenta.ai/dashboard/api-keys, then set ALGENTA_API_KEY.
Configure
export ALGENTA_API_KEY="<YOUR_ALGENTA_API_KEY>"
export ALGENTA_BASE_URL="https://api.algenta.ai"
Use your deployment URL for self-hosted Algenta. Private deployment profiles fail closed rather than silently sending traffic to Algenta Cloud.
Cursor and Claude Desktop
algenta-mcp uses stdio by default. Add this server to Cursor's ~/.cursor/mcp.json or Claude
Desktop's MCP configuration:
{
"mcpServers": {
"algenta": {
"command": "algenta-mcp",
"env": {
"ALGENTA_API_KEY": "<YOUR_ALGENTA_API_KEY>",
"ALGENTA_BASE_URL": "https://api.algenta.ai"
}
}
}
}
Restart the client after changing its MCP configuration.
Codex
Add the stdio server to ~/.codex/config.toml:
[mcp_servers.algenta]
command = "algenta-mcp"
[mcp_servers.algenta.env]
ALGENTA_API_KEY = "<YOUR_ALGENTA_API_KEY>"
ALGENTA_BASE_URL = "https://api.algenta.ai"
Keep credentials in user-level configuration or environment variables, not in a repository.
Streamable HTTP
Start the remote transport:
algenta-mcp --mode http --port 8001
The standalone server binds to 127.0.0.1 by default. Set ALGENTA_MCP_HOST=0.0.0.0 only when
an authenticated container ingress or gateway must expose it to another host.
Connect modern clients to:
http://localhost:8001/mcp
The endpoint uses stateless Streamable HTTP. It dual-serves both protocol eras from the same
endpoint: a legacy initialize handshake negotiates 2025-11-25, and a modern per-request caller
(the MCP-Protocol-Version header plus the 2026-07-28 _meta envelope, no handshake) gets
2026-07-28, including the built-in server/discover method. Algenta pins the official Python MCP
SDK 2.0.0. Deprecated /mcp/sse and /mcp/messages routes remain for older clients but are not
the default.
LangChain example:
import os
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient(
{
"algenta": {
"transport": "http",
"url": "http://localhost:8001/mcp",
"headers": {
"Authorization": f"Bearer {os.environ['ALGENTA_API_KEY']}"
},
}
}
)
tools = await client.get_tools()
Verify
The human-readable discovery route is available alongside the protocol endpoint:
curl -s http://localhost:8001/mcp/tools | jq '.tools | length'
In an MCP client, call get_contract first, then use list_data and get_data_summary before
querying a dataset. Tool names, descriptions, and input schemas are returned by MCP tools/list.
Security
- Tool calls use
Authorization: Bearer <ALGENTA_API_KEY>or the configured process credential. - Streamable HTTP validates
HostandOriginto prevent DNS-rebinding access. - Standalone HTTP binds to loopback unless
ALGENTA_MCP_HOSTis explicitly changed. - Error payloads redact API-key material.
ALGENTA_BASE_URLis required when cloud access is disabled.- Put an authenticating gateway in front of a publicly reachable standalone MCP port.
Compatibility
Canonical environment variables are ALGENTA_API_KEY and ALGENTA_BASE_URL. Legacy
DE_API_KEY, DE_BASE_URL, and ALGENTA_API_URL remain accepted for existing deployments.
License
Apache-2.0
Release files for algenta-mcp 1.0.28
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| algenta_mcp-1.0.28.tar.gz | 95.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| algenta_mcp-1.0.28-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 205.1 kB
Release files / algenta_mcp-1.0.28.tar.gz
| Download URL | algenta_mcp-1.0.28.tar.gz |
|---|---|
| Size | 95.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9304b6a75072b0fcdc789f78c1eba72b095e8dd88687f4c2760e0951cd8ee1b
|
|
BLAKE2b-256 checksum How to use checksums |
f741f12339ad168c743c6b828ca2b63ba5e11d074917e7a3eac9b60e516f8468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / algenta_mcp-1.0.28-py3-none-any.whl
| Download URL | algenta_mcp-1.0.28-py3-none-any.whl |
|---|---|
| Size | 109.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e00f103f5803237966c062624a51c20a08380a64da369c2043e4dab7e7a51f4a
|
|
BLAKE2b-256 checksum How to use checksums |
d2c2d33ff8be39c32eaca24f677f290d9bcf31b90b13d2f7f3f5012801470f62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|