The learn/guides/ai/AgentAgnosticMcpConfig.md guide was significantly outdated. It described a manual, agent-driven process for discovering and managing MCP servers based on the now-deleted .github/mcp-servers.json file.
This guide has been completely updated to reflect the current architecture, which relies on the @modelcontextprotocol/sdk and a client-managed lifecycle.
Key changes include:
- New Protocol: The guide now explains the modern "Lifecycle Protocol," where the agent's client environment (e.g., Gemini CLI) is responsible for launching servers via
command and args from its local configuration (e.g., .gemini/settings.json).
- Updated Schema: The
Server Definition table has been updated to be a more comprehensive, conceptual schema that includes properties like name, command, args, type, and instructions, clarifying the purpose of each.
- SDK-First Architecture: A new "Server-Side Implementation" section has been added to explain why the client configuration can be so simple. It details the roles of
StdioServerTransport, openapi.yaml for tool definitions, and the generic toolService.mjs.
- Cleanup: All obsolete sections describing the old implementation (e.g.,
healthCheck objects, connection objects, manual fetch/spawn examples) have been removed to avoid confusion.
- Content Restoration: The valuable "See Also" section with relevant links was re-added.
The updated guide now accurately represents the current, more robust, and simplified SDK-based approach to MCP server integration.
The
learn/guides/ai/AgentAgnosticMcpConfig.mdguide was significantly outdated. It described a manual, agent-driven process for discovering and managing MCP servers based on the now-deleted.github/mcp-servers.jsonfile.This guide has been completely updated to reflect the current architecture, which relies on the
@modelcontextprotocol/sdkand a client-managed lifecycle.Key changes include:
commandandargsfrom its local configuration (e.g.,.gemini/settings.json).Server Definitiontable has been updated to be a more comprehensive, conceptual schema that includes properties likename,command,args,type, andinstructions, clarifying the purpose of each.StdioServerTransport,openapi.yamlfor tool definitions, and the generictoolService.mjs.healthCheckobjects,connectionobjects, manualfetch/spawnexamples) have been removed to avoid confusion.The updated guide now accurately represents the current, more robust, and simplified SDK-based approach to MCP server integration.