fix(gemini): use marker instead of name prefix for MCP servers #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Gemini MCP server names were prefixed with
ai-rules-generated-to distinguish them from user-configured servers. This breaks MCP tool calls:mcp__agent-task-queue__run_taskai-rules-generated-agent-task-queuemcp__agent-task-queue__run_task()doesn't match the serverOther agents (Cursor, Roo, Claude) use
ExternalMcpGeneratorwhich preserves server names.Solution
Use
_aiRulesGenerated: truemarker in the server config instead of prefixing the name:{ "mcpServers": { "agent-task-queue": { "command": "uvx", "args": ["agent-task-queue@latest"], "_aiRulesGenerated": true } } }This allows MCP tools to work correctly while still distinguishing generated from user servers for clean/update operations.
Changes
prefix_server_names()withmark_as_generated()is_generated()helper to check for markerTest plan
cargo test geminipasses