imcp-addon
The SDK for one containerised MCP capability: an addon declares tools, serves pages, knows who is
calling, and keeps its own SQLite storage. Install the server extra for uvicorn, which run() needs:
pip install imcp-addon[serve]
A minimal addon — server.py
from imcp_addon import Addon, Request, ToolRequest, html
app = Addon(name="notes", title="Notes", schema=["CREATE TABLE note (account TEXT, text TEXT)"])
@app.tool("note_add", "Save a note for the current caller.")
async def note_add(request: ToolRequest, text: str) -> dict[str, str]:
request.store.insert("note", {"account": request.identity.account or "", "text": text})
return {"saved": text}
@app.page("/", title="Notes")
async def notes_page(request: Request) -> str:
notes = request.store.fetch_all("SELECT text FROM note")
body = html.card(None, *[html.el("p", text=row["text"]) for row in notes])
return html.page("Notes", body, base=request.base).render()
app.run()
Set IMCP_ADDON_DATA to a data directory and PORT to a free port, then python server.py. That
path is for local work only: in production the gateway starts the container, passes the caller's
signed identity in headers and proxies the pages and /mcp, so an addon implements no routing,
authentication or billing of its own.
The contract, storage rules and the page kit are in docs/ADDONS.md.
Metadata
Release files for imcp-addon 0.1.0
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 | Actions |
|---|---|---|---|---|
| imcp_addon-0.1.0.tar.gz | 18.8 kB | Without provenance | Details for imcp_addon-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| imcp_addon-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for imcp_addon-0.1.0-py3-none-any.whl |
Total release size: 39.9 kB
Release files / imcp_addon-0.1.0.tar.gz
| Download URL | imcp_addon-0.1.0.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18208d519d007ed4a6e9a3afda784aee966d4e463460274f7e52ab0c313029b8
|
|
BLAKE2b-256 checksum How to use checksums |
5fb8188301877c8bdd8bcbbea7dc55f565a09658250fc9a5a293be559c76220e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / imcp_addon-0.1.0-py3-none-any.whl
| Download URL | imcp_addon-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9606ded0c2dc1fe8514b9f4a2783e161adb906437118041fff441d9c605046d6
|
|
BLAKE2b-256 checksum How to use checksums |
e5b0c88c198313146f3380aed1d7e960591ead61dd6e21401f3382517bf0de2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for imcp-addon 0.1.0
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.