a2a-meta-clones
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@a2a-meta-clonesshow me the status of all clone slots"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
a2a-meta-clones
Canonical policy (binding): This repo is orchestrated by A2A-Meta (sibling of
!A2A-Meta-Repos/). SeeA2A-Meta/docs/repo_topology.mdfor the relationship, andA2A-Meta/docs/clone_repo_architecture_v0_DRAFT.mdfor the spec this repo implements.
A2A-Meta/docs/repo_topology.mdis the canonical policy document. This README is a convenience mirror, not a second authority. If they conflict, the root side wins.
Deployable MCP clone services for A2A-Meta. Hosts 3 Railway
service slots (slot-a, slot-b, slot-c) for the 5
PENDING_CLONES MCP clones catalogued in
A2A-Meta/api/middleware/live_clone_catalog.py.
The catalog in A2A-Meta is the single source of truth for
which clones are LIVE. This repo vendors a snapshot (via
sync_catalog.py) and serves the clones via the multiplexer
vendored from A2A-Meta/api/multiplexer.py.
Status (Phase A — local scaffold)
Phase A (local scaffold): in progress, see
docs/parallel_prep_runlog.md(mirror) andA2A-Meta/docs/a2a_meta_clones_v1_implementation_plan_v0_DRAFT.md(canonical plan)Phase B (GitHub + CI): not started
Phase C (Railway provisioning): not started
Phase D (deploy + promotion): not started
Related MCP server: MCP Manager
Local layout
a2a-meta-clones/
├── README.md # this file
├── LICENSE # MIT
├── .gitignore
├── .env.example # shows expected env vars
├── pyproject.toml # package metadata
├── Dockerfile # shared, used by all 3 slots
├── railway.toml # shared template
├── requirements.txt
├── services/
│ ├── slot-a/ # 2 clones: agent-lens, audit-bazaar
│ ├── slot-b/ # 2 clones: agent-fabric-oversight, agent-ledger
│ ├── slot-c/ # 1 clone: compliance-lens (+ 2 free capacity)
│ └── shared/
│ ├── multiplexer/ # vendored from A2A-Meta/api/multiplexer.py
│ ├── catalog_client/ # HTTP client for the A2A-Meta catalog
│ └── middleware/ # shared middleware
├── clone_specs/ # 10 files: 5 PENDING + 5 backlog
├── server_manifests/ # 10 directories
├── scripts/
│ ├── pipeline.py # 9 commands: init / scaffold / test / package / review / verify / promote / demote / status
│ ├── smoke_gate.py # 8 BLOCKED checks (--dry-run safe)
│ ├── check_no_legacy_slug.py # token-aware static check
│ ├── verify_endpoint.py # 4-probe HTTP 200 verify
│ └── sync_catalog.py # one-way copy of A2A-Meta catalog
├── tests/ # 9 test files + conftest
└── docs/
├── README.md
├── env_contract.md
├── promotion_log.md
└── rollback_runbook.mdQuick start (Phase A only)
# 1. Install dependencies
pip install -r requirements.txt
# 2. Run local tests
python -m pytest tests/ -v
# 3. Run the 8 smoke checks (--dry-run is safe; no network)
python scripts/smoke_gate.py --dry-run
# 4. Verify the legacy-slug static check
python scripts/check_no_legacy_slug.py
# 5. Show pipeline status
python scripts/pipeline.py statusWhat is NOT here
No
git initin this folder (Phase B's responsibility)No GitHub remote (Phase B)
No Railway services (Phase C)
No deploys (Phase D)
No promotion_request_*.json (Phase D)
This folder is a local scaffold. It will become a Git repo in Phase B.
Cross-references
Topology: A2A-Meta/docs/repo_topology.md
Pipeline: A2A-Meta/docs/clone_pipeline_v0_DRAFT.md
Plan: A2A-Meta/docs/a2a_meta_clones_v1_implementation_plan_v0_DRAFT.md
Aug 2 capture backend: A2A-Meta/docs/aug2_opus_spec.md
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceA MCP server do create and deploy backend applications using https://heim.devLast updated6363MIT
- Alicense-qualityAmaintenanceSelf-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.Last updated16MIT
- Alicense-qualityAmaintenanceA meta-MCP server that acts as a single connection point to lazily spawn and proxy multiple MCP servers, reducing context bloat and process overhead.Last updatedMIT
- AlicenseAqualityBmaintenanceMCP server exposing CS Executive Services dispatch platform and airplanes.live flight tracking as portable, agent-agnostic tools.Last updated25MIT
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
MCP server for the FFmpeg Micro video transcoding API — create, monitor, download transcodes.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Amondieu/a2a-meta-clones'
If you have feedback or need assistance with the MCP directory API, please join our Discord server