aif-mcp
PyPI distribution for AIF MCP adapters (aif-mcp-normbase, aif-mcp-eda, aif-mcp-schemo, aif-mcp-all).
This package is a thin layer over remote AIF HTTP APIs. It does not ship Normbase, EDA, Platform, or Facilitator server code.
Sibling package: aif-normative-agent (Python SDK / Runtime loop over the same HTTP APIs).
Install / run
uvx --from aif-mcp aif-mcp-all --transport stdio
uvx --from aif-mcp aif-mcp-normbase --transport stdio
uvx --from aif-mcp aif-mcp-eda --transport stdio
uvx --from aif-mcp aif-mcp-schemo --transport stdio
Node wrapper (same MCP entrypoints):
npx -y --package @langxai/aif-mcp aif-mcp-all
Tool names align with Norm-Native SDK (norm_*, eda_*, schemo_*, datumo_*, kb_*) plus org_list_tools / org_invoke_tool and role_list_held / runtime_request_active_role (Platform integrator proxies; handlers, Datumo, knowledge storage, and the active-role pin stay on the server). See docs/tool-parity-matrix.md and docs/mcp-migration-1.0.md.
Host configuration
| Variable | Required | Default |
|---|---|---|
AIF_AGENT_API_KEY |
Yes | — |
AIF_PLATFORM_URL |
No | https://www.norm.xin |
See .env.example. Local dev: set AIF_PLATFORM_URL=http://127.0.0.1:8020.
Monorepo note
Source lives under integrations/mcp only (Platform integrator HTTP client). Full-stack development uses the monorepo root editable install.
Publishing guide: docs/mcp-publishing.md.
Legacy PyPI name
Do not use aif-normbase on PyPI for MCP installs — older releases mistakenly bundled the full backend. Prefer aif-mcp.
1 maintainer
Metadata
1 maintainer
Release files for aif-mcp 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aif_mcp-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / aif_mcp-0.5.1-py3-none-any.whl
| Download URL | aif_mcp-0.5.1-py3-none-any.whl |
|---|---|
| Size | 46.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87c0b5735cc01f7fb833573602426c8e1d2fd4663261a47f4a142eca7590c15d
|
|
BLAKE2b-256 checksum How to use checksums |
f1d855dcca2685b7acc582466c6dc8d3bdadf88f46f9c97eb33fc2dc24519a54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.14
|
Security for aif-mcp 0.5.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
