An Agent that acts as an MCP client — dynamically connects to remote MCP servers, handles OAuth authentication, and aggregates tools, prompts, and resources from all connected servers.
addMcpServer/removeMcpServer— managing MCP server connections from an AgentonMcpUpdate— real-time state updates pushed to the React frontend via WebSocket- OAuth popup flow —
configureOAuthCallbackwith a custom handler that closes the popup after auth agentFetch— making HTTP requests to the Agent's custom endpoints from the client
npm install
npm run devThe UI lets you add MCP server URLs, see their connection state, and browse their tools, prompts, and resources.
To test with an authenticated server, run the mcp-worker-authenticated example alongside this one and add its URL.
Copy .env.example to .env if you need to override the OAuth callback host:
cp .env.example .envThe Agent manages MCP connections via the built-in mcp property:
export class MyAgent extends Agent {
onStart() {
this.mcp.configureOAuthCallback({
customHandler: (result) => {
if (result.authSuccess) {
return new Response("<script>window.close();</script>", {
headers: { "content-type": "text/html" }
});
}
return new Response(`Auth failed: ${result.authError}`, {
status: 400
});
}
});
}
async onRequest(request) {
// Custom endpoints for the frontend
if (url.pathname.endsWith("add-mcp")) {
const { name, url } = await request.json();
await this.addMcpServer(name, url);
return new Response("Ok");
}
}
}The React frontend uses useAgent with onMcpUpdate to receive real-time server state:
const agent = useAgent({
agent: "my-agent",
name: sessionId,
onMcpUpdate: (mcpServers) => setMcpState(mcpServers),
onOpen: () => setConnected(true)
});mcp— stateful MCP server (good target to connect to)mcp-worker-authenticated— authenticated server (tests the OAuth flow)