Local MCP is useful.
Remote MCP is a system boundary.
MetaMCP started as a way to reduce many MCP tools into a smaller tool surface. The next question was practical: can that surface live behind Cloud Run, get registered for agents, and leave evidence after tool calls?
Gateway
Many tools become one governed surface.
MetaMCP gives agents fewer, clearer entry points instead of exposing every tool directly.
Runtime
Cloud Run changes the transport problem.
A cloud agent cannot depend on local stdio. The useful path is Streamable HTTP.
Evidence
Tool calls need a memory trail.
Mentu ledgers make important agent work reviewable after the run.
The problem
Most MCP work begins on a laptop.
That is where the idea gets proven.
The production question is different.
Can another agent call it from a cloud runtime?
Can the endpoint be registered?
Can auth, secrets, tests, and evidence sit around the tool call?
That is the part worth building.
The system shape
MetaMCP keeps the local developer path intact.
Then it adds the parts needed for a remote MCP surface:
- stdio for local use.
- Streamable HTTP for Cloud Run.
- Docker and Cloud Build artifacts.
- Azure DevOps pipeline file.
- IAM and Secret Manager setup notes.
- Agent Registry toolspec and endpoint manifests.
- Google ADK sample for consuming the registered MCP toolset.
- Smoke tests for health, auth, initialize, and tools list.
- Mentu evidence export from
.metamcp/ledger.jsonl.
What this proves
| Agent question | System answer |
|---|---|
| Where are the tools? | Behind a smaller MetaMCP gateway. |
| How does a cloud agent call them? | Through Streamable HTTP on Cloud Run. |
| How are tools registered? | With Agent Registry metadata and a manual toolspec. |
| How does auth work? | Cloud Run caller identity plus app-level bearer auth. |
| How do we know what happened? | Logs, smoke tests, prompt fixtures, and Mentu evidence. |
Why it matters
Agents get interesting when they stop living in a demo window.
Then the boring parts become the product:
- endpoints
- service accounts
- secrets
- deployment scripts
- tests
- logs
- contracts
- evidence
MetaMCP is a small open-source way to show that path.
Related writing
- Getting Software to Talk to Each Other
- The Data Infrastructure Nobody Wants to Build
- How AI Should Analyze Your Data