AgentBridge Nexus MCP Server
Python MCP server that exposes AgentBridge backend actions as tools for AI coding agents.
Status
The backend/MCP terminal MVP is implemented and live-tested. The package currently provides:
- backend HTTP client
- testable tool functions
- MCP
FastMCPentrypoint - core lifecycle, artifact, coordination, audit, memory, and validation tools
Environment
Set these before running the MCP server:
export AGENTBRIDGE_API_URL="http://localhost:8000"
export AGENTBRIDGE_AGENT_KEY="abk_your_agent_key"
AGENTBRIDGE_AGENT_KEY should be one of the keys printed by:
cd services/api
.venv/bin/python scripts/seed_dev.py --apply
Tools
agentbridge_heartbeatagentbridge_create_handoffagentbridge_list_handoffsagentbridge_claim_handoffagentbridge_submit_artifactagentbridge_get_artifactagentbridge_get_artifact_contentagentbridge_request_reviewagentbridge_create_approvalagentbridge_submit_reviewagentbridge_complete_handoffagentbridge_acquire_file_lockagentbridge_release_file_lockagentbridge_list_file_locksagentbridge_list_file_conflictsagentbridge_resolve_file_conflictagentbridge_list_audit_logsagentbridge_create_project_memoryagentbridge_list_project_memoryagentbridge_search_project_memoryagentbridge_update_project_memoryagentbridge_delete_project_memoryagentbridge_start_work_sessionagentbridge_list_work_sessionsagentbridge_checkpoint_progressagentbridge_resume_project
Resume workflow tools:
agentbridge_start_work_sessionstarts tracking a feature/task in progress.agentbridge_checkpoint_progressrecords where the agent is before stopping.agentbridge_resume_projectgenerates the continuation packet and prompt for another agent.
Run
From this directory:
python -m agentbridge_mcp.server
When installed as a package:
agentbridge-mcp
One-Command Resume
Record the current stopping point before switching agents or hitting a usage limit:
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.checkpoint_cli \
--project-id <project_id> \
--summary "Implemented backend slice and verified focused tests." \
--current-step "Ready to hand off" \
--next-step "Continue from the recorded checkpoint"
When installed as a package:
agentbridge-checkpoint \
--project-id <project_id> \
--summary "Implemented backend slice and verified focused tests." \
--next-step "Continue from the recorded checkpoint"
The checkpoint command reads local git state by default: branch, latest commit,
worktree path, and dirty files. Use --no-git to disable auto-detection.
Generate a resume packet for another agent:
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.resume_cli \
--project-id <project_id> \
--target-agent antigravity
Save it locally:
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.resume_cli \
--project-id <project_id> \
--target-agent antigravity \
--output .agentbridge/resume-antigravity.md
When installed as a package:
agentbridge-resume --project-id <project_id> --target-agent antigravity
The command reads AGENTBRIDGE_API_URL and AGENTBRIDGE_AGENT_KEY from the
environment, calls the resume packet API, prints the generated prompt, and
optionally saves it. It also prints safety_status and should_continue so
the next agent can pause when locks or conflicts are present. If expires_at
has passed, it prints a stale packet warning and the agent should regenerate the
packet before continuing. It never prints agent keys.
With --json, the command also adds a local is_expired boolean so scripts can
block continuation without parsing timestamps themselves.
Test
The tool layer can be tested without a live backend:
PYTHONPATH=src pytest tests -q
Terminal Demo
Mock mode works without a backend:
PYTHONPATH=src python -m agentbridge_mcp.demo
Live mode uses AGENTBRIDGE_API_URL and AGENTBRIDGE_AGENT_KEY, then prompts for the Antigravity key, project ID, and agent IDs. Use the Codex key as AGENTBRIDGE_AGENT_KEY.
PYTHONPATH=src python -m agentbridge_mcp.demo --live
Live Backend Validation
Run these after the API is running on http://127.0.0.1:8000:
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.live_artifact_validation
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.live_coordination_validation
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.live_resume_validation
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.live_cli_resume_validation \
--output /tmp/agentbridge-cli-resume.md
PYTHONPATH=src ../api/.venv/bin/python -m agentbridge_mcp.live_reverse_resume_validation
Required environment variables:
export AGENTBRIDGE_API_URL="http://127.0.0.1:8000"
export AGENTBRIDGE_AGENT_KEY="<codex_agent_key>"
export AGENTBRIDGE_PROJECT_ID="<project_id>"
export AGENTBRIDGE_CODEX_AGENT_ID="<codex_agent_id>"
export AGENTBRIDGE_ANTIGRAVITY_AGENT_ID="<antigravity_agent_id>"
export AGENTBRIDGE_ANTIGRAVITY_AGENT_KEY="<antigravity_agent_key>"
live_reverse_resume_validation uses AGENTBRIDGE_ANTIGRAVITY_AGENT_KEY to
create/checkpoint a handoff targeting Codex, then uses AGENTBRIDGE_AGENT_KEY
as Codex to generate the resume packet and verify the latest Antigravity
checkpoint is preserved.
IDE Validation Checklist
Use the adapter configs in adapters/codex and adapters/antigravity.
-
Start the API:
cd services/api .venv/bin/uvicorn main:app --port 8000
-
Confirm health:
curl http://127.0.0.1:8000/api/v1/health -
Configure Codex with the Codex agent key and Antigravity with the Antigravity agent key.
-
From Codex, call
agentbridge_heartbeat. -
From Codex, create a handoff assigned to Antigravity.
-
From Antigravity, list assigned handoffs and claim the new handoff.
-
From Antigravity, submit an artifact and request Codex review.
-
From Codex, fetch the artifact content, submit the review, and complete the handoff.
-
If any MCP tool fails in the IDE but works from terminal validation, record the exact tool name, payload, and API error before changing backend behavior.
Metadata
Release files for agentbridge-mcp-server 0.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 | Provenance | Actions |
|---|---|---|---|---|
| agentbridge_mcp_server-0.1.1.tar.gz | 26.7 kB | Without provenance | Details for agentbridge_mcp_server-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentbridge_mcp_server-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for agentbridge_mcp_server-0.1.1-py3-none-any.whl |
Total release size: 57.8 kB
Release files / agentbridge_mcp_server-0.1.1.tar.gz
| Download URL | agentbridge_mcp_server-0.1.1.tar.gz |
|---|---|
| Size | 26.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02cdadb6c556eeee36cf03e10fb0f24b1c6a810e2917810c44033d894444039a
|
|
BLAKE2b-256 checksum How to use checksums |
8385f28ebbc9d30b588ed5858e485ffeab680c3ffafecf9d262b05a5ddfc4167
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / agentbridge_mcp_server-0.1.1-py3-none-any.whl
| Download URL | agentbridge_mcp_server-0.1.1-py3-none-any.whl |
|---|---|
| Size | 31.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd287e00060aafcde7435407c86e6e529510d3dc3511187b889f8f58d28a13c4
|
|
BLAKE2b-256 checksum How to use checksums |
6bec357480113ab0ec419b6fbb467403a27d4d92ccd3cf8bcce11ff88db6c083
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for agentbridge-mcp-server 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.
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.