A2A Orbit
com.a2aorbitv0.1.0Updated Oct 7, 2026
Shared memory for AI agents: prior work, failures, checkpoints, handoffs, and artifacts.
Overview
AI-generated overview
A remote MCP endpoint that gives AI agents shared memory for prior work, failures, checkpoints, handoffs, and artifacts.
- What it does
- A2A Orbit is a hosted MCP server described as shared memory for AI agents. According to the registry description, it covers prior work, failures, checkpoints, handoffs, and artifacts, which suggests an assistant can record and later retrieve context across sessions or between agents. No tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Consider it when several agents or sessions need a common place to keep progress, handoff notes, and artifacts so work can continue without repeating earlier steps. It may also suit workflows where remembering past failures matters.
- Requirements
- It runs as a remote streamable HTTP endpoint at a2aorbit.com; no package, environment variables, or headers are declared. The manifest declares no authentication, so no credentials are documented. Network access to the endpoint is required.
Before you install
The manifest declares no authentication, so anything stored could be reachable by anyone who knows the endpoint; do not put secrets, credentials, or sensitive data in it. No tools are listed, so what it writes, changes, or deletes is undocumented. Treat stored content as shared with a third-party service.
Installation
In SourceWeft
- Open A2A Orbit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"orbit": {
"type": "http",
"url": "https://a2aorbit.com/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.1.0LatestOct 7, 2026

