The repository or configuration that created this release differ from a previous release. View details.
compos-mcp
MCP (Model Context Protocol) server for Compos — gives AI builders architectural context about your codebase.
Install
Easiest path — Claude Code plugin (auto-configures this server):
/install-plugin github:fer46/compos-plugin
Manual install for other MCP clients:
uv tool install compos-mcp
compos-mcp # starts the server (stdio transport)
Wire into your MCP client's config; the server auto-discovers .compos/ by walking up from its working directory.
Requires Python 3.13+ and a project with compos init already run (use compos-cli for that).
Tools exposed
Read (orient before changes): get_component_context, get_blast_radius, list_components, get_component, list_versions, get_snapshot, get_constraints_for_components, get_decisions_for_component, get_relationships_for_component, get_system_map.
Write (log architectural reality as you work): register_component / update_component / remove_component, same pattern for relationship / constraint / risk. Decisions use log_decision / update_decision / remove_decision.
Evaluate: evaluate_proposed_change — pre-flight check for structural changes.
Documentation
Full tool reference: https://github.com/fer46/compos.
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for compos-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| compos_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for compos_mcp-0.1.1-py3-none-any.whl |
Release files / compos_mcp-0.1.1-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | compos_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 45.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47454e4c676d7e96d5108cc58c3c3d69389cb3f5834449a5f5cba8bec594a150
|
|
BLAKE2b-256 checksum How to use checksums |
d2d909de407f62f782cb57698c901886f7dbdb74fa77e0c24d6bbfbcdda2b08e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Apr 16, 2026.
Transparency logSecurity for compos-mcp 0.1.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.
Change of provenance
The repository and configuration that created this release differ from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
- Removed 0.1.0 github.com/fer46/Compos
- Added 0.1.1 github.com/fer46/compos-platform
Attestation for compos_mcp-0.1.1-py3-none-any.whl
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 Apr 16, 2026.
Transparency logA 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.
