RemoteA2aAgent to MCP repository documentation: interoperability findings and a free pilot

[Gazou9111]

I maintain AgentBridge, an experimental hosted bridge between A2A and MCP. I am looking for one independent pilot with an actual need to access public repository documentation through A2A, without adding an MCP client to the consumer.

We tested RemoteA2aAgent directly with InMemoryRunner using google-adk 2.12.0, a2a-sdk 1.2.3 and google-genai 2.32.0. This uncovered a bug in our server: it rejected the optional Part metadata that ADK adds. We fixed our validation. Text discovery, structured discovery and a structured documentation request now complete over public HTTPS. The documentation result was cached. These are internal interoperability checks, not evidence of adoption or full ADK compatibility; no paid model was used.

The current execution path uses a structured A2A data part with an advertised free_* action and its input schema. Text-only messages return discovery, not a documentation answer. Generic natural-language delegation is not implemented.

Public Agent Card:
https://sympathy-myself-jogger.ngrok-free.dev/.well-known/agent-card.json

Guest guide:
https://sympathy-myself-jogger.ngrok-free.dev/public/usage

Current tool schemas:
https://sympathy-myself-jogger.ngrok-free.dev/public/services?protocol=mcp

Use the ngrok-skip-browser-warning: 1 header if your reader receives the tunnel warning page. The advertised guest tools require no signup, wallet or payment. The service is experimental and quota-limited, with no uptime guarantee. Inputs and cached results must be public: please do not send private repositories, prompts or credentials.

If this addresses a real task in your setup, choose your own public repository question and try the advertised contract. A useful report would include the executionId, whether the result answered your question, any integration obstacle, and why A2A access is useful to you compared with direct MCP. This would be a solicited pilot; a useful cached result is acceptable. DeepWiki is already free via MCP directly, so this invitation is specifically about the protocol boundary.

The server and client source remain private. This post contains no source code and makes no contribution or licensing commitment. If this category is not appropriate, please let me know.