McpPlug (Python)
Built for LoopEngine — a
runtime for defining and running AI agents through a transparent ReAct
loop — as a ToolSource wrapping Composio's
1000+ app gateway behind the same ToolDefinition shape LoopEngine
agents already use. Works standalone too, no dependency on LoopEngine
itself.
Ported line-for-line from the TypeScript implementation. See the root README for the pitch and the scope decisions — this file only covers what's specific to running the Python code.
Install
pip install -e ".[dev]"
Quickstart
Requires the composio CLI installed and
authenticated (composio link <toolkit>) for whichever tools you list.
from mcpplug import ComposioSourceOptions, connect_composio_source
github = await connect_composio_source(
"gh", ComposioSourceOptions(slugs=["GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER"])
)
tools = await github.load_tools()
# -> [ToolDefinition(name='gh_GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER', ...)]
result = await tools[0].execute({"per_page": 5})
Merge tools into any agent's tool list — each ToolDefinition is the
same shape a loopengine-style AgentConfig.tools expects.
Test
pytest
Status
The ToolSource protocol and the Composio-backed source are real and
tested (tests/test_composio_source.py uses a stand-in CLI script, not a
live network call). Not yet published to PyPI.
Metadata
Release files for mcpplug 0.0.2
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 |
|---|---|---|---|---|
| mcpplug-0.0.2.tar.gz | 4.7 kB | Without provenance | Details for mcpplug-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcpplug-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for mcpplug-0.0.2-py3-none-any.whl |
Total release size: 9.8 kB
Release files / mcpplug-0.0.2.tar.gz
| Download URL | mcpplug-0.0.2.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45b69e64451d2d082f0b5c3a00a3708929745666976f4615098fb2cb0473248d
|
|
BLAKE2b-256 checksum How to use checksums |
b9db74b3950c95b237d448af52f7be983d54ab6ce6b620ab1023cad2077779f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Release files / mcpplug-0.0.2-py3-none-any.whl
| Download URL | mcpplug-0.0.2-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
253a0cd93daf11ceeee7eecaf8839111557b4ee851d472e877a218d44a2322e7
|
|
BLAKE2b-256 checksum How to use checksums |
818d63090abef6ec61aa58a79b8f9dfe1641c749a1d6a60024d42645fe033c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.8
|
Security for mcpplug 0.0.2
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.