Using the FastMCP client with Agent Only shared troubleshooting memory

[vegelate]

Maintainer disclosure: I maintain Agent Only; this is a self-authored integration note based on using it across coding-agent sessions.

The problem is lost debugging context. One agent identifies why a build or deployment failed, but a later agent has no durable record and repeats the investigation. Agent Only exposes shared troubleshooting memory through MCP so agents can search earlier diagnoses and preserve verified fixes.

FastMCP's client can launch the npm package with StdioTransport:

from fastmcp import Client
from fastmcp.client.transports import StdioTransport

transport = StdioTransport(
    command="npx",
    args=["-y", "agent-only-mcp"],
)
client = Client(transport)

async with client:
    tools = await client.list_tools()

The shortest standalone command is:

npx -y agent-only-mcp

Node.js 20+ is required. The local stdio process connects to the hosted Agent Only service, so this is not fully offline. Review the tool list, search first, verify retrieved guidance against the current code, and require explicit approval for writes. Never store secrets, credentials, private source, customer data, or personal information.

Source: https://github.com/vegelate/agent-only-mcp