niwashi-mcp
MCP server for Cisco ACI (APIC). It reads the fabric's own object model rather than a fixed list of endpoints, so an LLM agent can navigate all 15,452 ACI classes through five generic tools — with no hardcoded class knowledge.
uvx niwashi-mcp
No repository to clone, no schema bundle to download. The object model ships
inside the niwaki dependency as an
embedded catalogue.
Configure
Three variables, in a .env file or the environment:
APIC_HOST=10.0.0.1
APIC_USER=admin
APIC_PASSWORD=…
Optional: APIC_VERIFY_SSL (default false), MCP_PORT (default 8000),
MCP_API_KEYS (comma-separated bearer tokens — unset means no
authentication, and the server says so loudly at startup),
NIWASHI_MCP_ENV_FILE (explicit path to the .env).
The five tools
| Tool | Purpose |
|---|---|
search_classes |
find the exact ACI class name from a keyword |
get_schema |
identifiers, containment, relations, properties of a class |
query |
filtered class query against the APIC |
get_by_dn |
fetch one object directly by DN |
count |
count objects without transferring them |
The intended order is search_classes → get_schema → query. Skipping the
first two returns empty results silently, because the APIC answers 200 OK with
an empty list for an unknown class or attribute — it does not error.
Documentation
Full documentation, architecture notes and deployment guides: https://github.com/k3l0-dev/niwashi-mcp
The repository also carries mcp/client/SKILL.md — the operating guide to give
an LLM client alongside the server. It teaches the ACI object model, the
mandatory tool order, and how to read a relation without concluding wrongly.
Requirements
Python ≥ 3.12. A reachable APIC and a read-only service account.
Licence
PolyForm Noncommercial 1.0.0 — free for personal, research and noncommercial use. Commercial deployment or integration requires a commercial licence: monark.aiops@pm.me.
Cisco, Cisco ACI and APIC are trademarks of Cisco Systems, Inc. niwashi-mcp is an independent project, not affiliated with or endorsed by Cisco Systems, Inc.
Release files for niwashi-mcp 2.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 | |
|---|---|---|---|
| niwashi_mcp-2.1.1.tar.gz | 472.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| niwashi_mcp-2.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 533.0 kB
Release files / niwashi_mcp-2.1.1.tar.gz
| Download URL | niwashi_mcp-2.1.1.tar.gz |
|---|---|
| Size | 472.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18de94d7972bc8d5c633a03850b584d98e74d10eb95f70a5083500ce4808f19e
|
|
BLAKE2b-256 checksum How to use checksums |
0c001ee1c12919359a3a872c86ab2d0d3d42a2bfe586d5a61ec5927978d2a457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 9, 2026.
Transparency logRelease files / niwashi_mcp-2.1.1-py3-none-any.whl
| Download URL | niwashi_mcp-2.1.1-py3-none-any.whl |
|---|---|
| Size | 60.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2665092bed2982ef02dce0dd2ece522a3a87bc2d78a105312c85bb07a064ac5
|
|
BLAKE2b-256 checksum How to use checksums |
decd29147485163ad95b9a723fcb2cc96fa56432ea14945c5a321dee025e97c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 9, 2026.
Transparency log