https://api.atlan.com/mcp. A client that connected with ?tools=full keeps working, but new clients use search mode unless you pass the parameter. This page covers what to change when you move an existing client over.
Before you begin
Before you start, make sure you have:- An existing client on full mode: a client connected with
?tools=fullwhose approvals and permission rules match individual tool names.
Update approvals and reconnect
1
Replace tool-name approvals with runner approvals
In full mode, approvals match each tool’s own name. In search mode, calls go through a runner — For other clients, replace per-tool rules with the equivalent runner names. See Tool approvals for the full list and what each runner covers.If you are not ready to update approvals yet, keep
mcp__call_read_tool, mcp__call_write_tool, or mcp__call_tool — so a rule that matches a tool’s name no longer fires.Replace per-tool rules with runner approvals. For Claude Code with a server named atlan, update .claude/settings.json:?tools=full on the URL until you are.2
Reconnect the client
Remove
?tools=full from the URL, then reconnect the client so it picks up the new tool list. In Claude Code:3
Verify search mode is active
After reconnecting,
tools/list should return five tools instead of every tool. The agent uses mcp__search_tools and mcp__describe_tools to find and inspect tools before calling them. If you still see the full tool list, check that ?tools=full is no longer in the URL.Next steps
- How search mode works: Runners, tiers, and how the agent finds the right tool.
See also
- Tool approvals: Runner names and what each one covers.
- Connect client to MCP Gateway: Full setup for a new client.