Agimus MCP Server
Connects AI coding tools (Claude Desktop, Claude Code, Cursor, OpenAI Codex and other Model Context Protocol clients) to the Agimus data platform. The server gives the AI live awareness of your ontology (entities, properties, links, categories, types), reads of live data as object sets, and the Agimus Python SDK reference, so it writes correct code instead of guessing field names. There is no dataset surface: every read is an entity of the ontology.
What the AI gets
Tools (13)
Discovery:
| Tool | What it does |
|---|---|
agimus_semantic_schema_search |
Natural-language search over entity, property and link descriptions; categories=[...] scopes by domain |
agimus_list_entities |
Every entity, with its primary key, property and link counts, categories and tier; categories=[...] filters |
agimus_get_entity_schema |
Full schema for one entity: properties with types and declarations, links with cardinality and direction, categories, and the SDK line for bulk |
agimus_list_links |
Every link in the ontology, both directions per link |
agimus_get_link |
Full details for a link by api_name |
agimus_list_categories |
Every category with access-filtered entity counts |
agimus_get_category |
One category and its entities |
agimus_whoami |
Tenant name, scope and rate limit of the current API key |
Read (read-only; bulk and writes happen through the SDK in user code):
Every read is one object set: an entity and ordered steps (filter,
pivot, with, top); a filter is a clause, and/or/not, or a link
predicate ({"link": L, "any": F}, {"link": L, "none": F}). The steps
parameter's description carries the grammar.
| Tool | What it does |
|---|---|
agimus_query_set |
A page of the objects of a set (sort, fields, expand, cursor; at most 500 per call) |
agimus_count_set |
The exact count of a set |
agimus_distinct_set |
The distinct values of one field over a set, optionally with counts |
agimus_aggregate_set |
Exact metrics over a set, grouped by values, time grains or ranges |
agimus_get_object |
One object by primary key |
The related objects of one object are a filter on its key and a pivot. Every
set tool takes an optional plane (operational or analytical) to choose
which plane serves the set; the platform chooses when it is omitted, and a
plane that cannot serve the set is refused at once with the entity named.
Resources
agimus://schema/entities/{entity}: live, full schema for one entityagimus://docs/sdk-reference: the full Agimus Python SDK reference (sourced directly from the SDK's README so it never drifts)
Install & configure
The recommended path is uvx: it auto-installs
the latest version on first run and keeps it isolated. No prior pip install
is required.
Claude Code
Add to ~/.claude/claude_code_config.json:
{
"mcpServers": {
"agimus": {
"command": "uvx",
"args": ["agimus-mcp"],
"env": { "AGIMUS_API_KEY": "agm_your_api_key_here" }
}
}
}
Cursor
Create .cursor/mcp.json in your project root:
{
"mcpServers": {
"agimus": {
"command": "uvx",
"args": ["agimus-mcp"],
"env": { "AGIMUS_API_KEY": "agm_your_api_key_here" }
}
}
}
OpenAI Codex
Add to ~/.codex/config.toml:
[mcp_servers.agimus]
command = "uvx"
args = ["agimus-mcp"]
env = { AGIMUS_API_KEY = "agm_your_api_key_here" }
Claude Desktop
Add to claude_desktop_config.json (Claude → Settings → Developer → Edit Config):
{
"mcpServers": {
"agimus": {
"command": "uvx",
"args": ["agimus-mcp"],
"env": { "AGIMUS_API_KEY": "agm_your_api_key_here" }
}
}
}
Alternative install: pip
If you prefer a pinned global install:
pip install agimus-mcp
Then replace "command": "uvx", "args": ["agimus-mcp"] with
"command": "agimus-mcp" in any config above.
CLI options
agimus-mcp [--api-key agm_xxx] [--base-url URL] [--timeout SECONDS] [--log-level LEVEL]
Every flag has an environment-variable equivalent:
| Flag | Env var | Default |
|---|---|---|
--api-key |
AGIMUS_API_KEY |
(required) |
--base-url |
AGIMUS_BASE_URL |
https://api.agimus.ai |
--timeout |
AGIMUS_TIMEOUT |
30 |
--log-level |
AGIMUS_LOG_LEVEL |
WARNING |
Logs are written to stderr; stdout is reserved for the MCP stdio protocol.
Requires Python 3.10 or later and the agimus SDK 1.x, which it installs.
License
MIT
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file agimus_mcp-1.0.1.tar.gz.
File metadata
- Download URL: agimus_mcp-1.0.1.tar.gz
- Upload date:
- Size: 22.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.12.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
fd8efddf878db3a999305878593d4ea547573af8bfa8c9ffc9e61f5a213679a5
|
|
| MD5 |
08b9967120adb94f06104a0338f4ee28
|
|
| BLAKE2b-256 |
5888093f2fa924a852760c1967305d649d09949d105e5b269e11ae1b5abc1c33
|
File details
Details for the file agimus_mcp-1.0.1-py3-none-any.whl.
File metadata
- Download URL: agimus_mcp-1.0.1-py3-none-any.whl
- Upload date:
- Size: 26.8 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.12.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
992970be5efb2d411c2a2a4cd2a0d97d8ff848faeb8648f87c45da2fcb758bde
|
|
| MD5 |
c5e44c7c516f9031d45c2bf63a5178de
|
|
| BLAKE2b-256 |
2b096f1084276910d41fda1947ea65363181e6612f6d93b11c368b6fcea35978
|