A connection that survives a restart.
Tool services can restart during an open conversation. MCP Stub remembers their last discovered tools and attempts to reconnect. A listed tool can still fail during the outage; after recovery, verify a small read before relying on the connection.
The stub forwards supported tool, resource, prompt and skills requests. It adds no task tools or account sign-in of its own. The connected service determines which capabilities and permissions are available. A failed operation is reported, not automatically repeated.
What you gain over a direct connection.
Remembered tools
The conversation keeps its tools; a visible name is not proof that a call can succeed
- Typical alternative
- A tool list that empties when the service restarts
- Here
- The last discovered definitions remain available during recovery
Reconnection
After recovery, refresh tools and perform a permitted read before relying on the connection
- Typical alternative
- Reopening the connection by hand after every restart
- Here
- Recovery attempts continue while the stub runs
Tool changes
Your agent acts on the signal or refreshes explicitly
- Typical alternative
- Discovering a changed tool when a call fails
- Here
- A successful refresh can announce revised definitions
Rich results
The agent must support the returned content; linked content can require a later read
- Typical alternative
- Losing images, audio or linked content in transit
- Here
- Supported text, images, audio, embedded resources and resource links are retained
Skills
Confirm the expected skill is available in this connection
- Typical alternative
- Copying skill instructions into each client
- Here
- Compatible upstream skills can be listed and read
Failed calls
Check the destination before repeating an interrupted change
- Typical alternative
- A retry that silently repeats a change
- Here
- The stub does not replay a failed call
Ready in the image, one entry to add.
The stub comes with the MAIT image, next to MCP Registry, and updates with it (mait-image). The person who sets up your workspace adds one entry to your agent's settings that points the stub at the service, or lets it start a registry when needed. You then open the connection through your agent's normal controls.
The stub remembers connection information and discovered capabilities while it runs. Tool data and account sign-in belong to the connected service; reopening the stub does not restore remote work.
Where it sits in the MAIT toolkit.
It is the link between your agent and the shared registry.
Where to read on.
- Get started, Use cases and Tools