agloop-mcp
MCP server providing 14 agent introspection tools for AgLoop — the VS Code Copilot custom agent framework.
Quick Start
Add to your .vscode/mcp.json:
For claude desktop or cli users use
mcpserversinstead ofservers
{
"servers": {
"agloop": {
"command": "uvx",
"args": ["agloop-mcp"]
}
}
}
Or run directly:
uvx agloop-mcp
Tools
Read Tools (10)
| Tool | Description |
|---|---|
agloop_get_state |
Full AgLoop state: phase, tasks, iteration, compaction context |
agloop_get_task |
Single task details by ID |
agloop_list_tasks |
All tasks with optional status/dependency filter |
agloop_get_logs |
Execution log entries with agent/task/limit filters |
agloop_get_plan |
Current plan (YAML or Markdown) |
agloop_get_compaction_context |
Compaction recovery context |
agloop_search_logs |
Full-text search through execution logs |
agloop_get_agent_info |
Agent definition file (.agent.md) content |
agloop_get_next_task |
Topological-sort next task recommendation |
agloop_list_agents |
All available agent names |
Write Tools (4)
| Tool | Description |
|---|---|
agloop_update_task |
Update task status and result log |
agloop_append_log |
Append structured entry to execution log |
agloop_create_checkpoint |
Snapshot current state for recovery |
agloop_set_phase |
Transition to a new phase |
Configuration
The server uses the current working directory as the workspace root. Override with:
uvx agloop-mcp --workspace /path/to/project
State Files
The server reads/writes from .agloop/ in the workspace root:
.agloop/
├── state.json # Phase, tasks, iteration
├── log.json # Execution log (JSON Lines)
├── plan.yaml # Current plan
└── checkpoints/ # State snapshots
Requirements
- Python 3.11+
- No additional dependencies beyond
mcp
License
MIT
Metadata
Release files for agloop-mcp 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 |
|---|---|---|---|---|
| agloop_mcp-0.1.0.tar.gz | 8.5 kB | With provenance | Details for agloop_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agloop_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agloop_mcp-0.1.0-py3-none-any.whl |
Total release size: 18.9 kB
Release files / agloop_mcp-0.1.0.tar.gz
| Download URL | agloop_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1071b6bda9f35b62f9dc27f72bceeb74d145ed3a0270f6051059e6663f7a1b0
|
|
BLAKE2b-256 checksum How to use checksums |
4dcf83bc44480ae899a539ff3f18f9d5802cd4cf74f04c06ee6fbf333eaae406
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 2, 2026.
Transparency logRelease files / agloop_mcp-0.1.0-py3-none-any.whl
| Download URL | agloop_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
caefac3dd54f3012ddd8f2db883a282da60c539d49883d7b5f64babd0dbf8539
|
|
BLAKE2b-256 checksum How to use checksums |
7668510292c3fa32decdda4a61bc0e40c6bf69fec5c90ff8b0a7f78049fe5ad3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 2, 2026.
Transparency logSecurity for agloop-mcp 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agloop_mcp-0.1.0.tar.gz
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 Mar 2, 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.