🔌 Fixing MCP Tool Count Differences in Claude Code

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

When you connect the Search Atlas MCP (Model Context Protocol) server to Claude Code, you may notice that the number of available tools is lower than the full published count. For example, you might see 475 tools instead of 607, and a specific tool or skill such as /onboard-client may appear to be missing. This is almost always expected behavior caused by client-side limits and configuration, not a fault with your account. This article explains why the difference happens and how to restore access to the tools you need.

🔎 Why the Tool Count Looks Lower

The Search Atlas MCP server exposes a large catalog of tools and skills. The number that actually appears in Claude Code can be smaller for several common reasons:

  • Client tool limits: Claude Code caps how many MCP tools it loads at once to protect performance. When the catalog exceeds that cap, some tools are not registered.

  • Multiple connected servers: If you have other MCP servers connected, they share the same tool budget, leaving fewer slots for Search Atlas tools.

  • Permission scope: Your plan, role, or workspace permissions may hide tools you are not entitled to use.

  • Version mismatch: An outdated Claude Code build or MCP server version may not expose newly added tools.

  • Filtering or allowlists: Project or user settings can explicitly enable or disable specific tools, which changes the visible count.

    💡 Why a Specific Tool Is Missing

A tool like /onboard-client disappearing usually points to one of these causes:

  • It falls outside the loaded tool limit and was dropped when the catalog was truncated.
  • It is gated behind a permission or feature your current workspace does not have enabled.
  • It was renamed or grouped under a different skill in a newer release, so an older client no longer recognizes it.

🛠️ How to Restore Missing Tools

Work through these steps in order. Most customers regain full access after the first two.

  1. Update everything: Make sure Claude Code and the Search Atlas MCP connection are on their latest versions. Restart Claude Code after updating so the tool list reloads.
  2. Reduce connected servers: Temporarily disconnect other MCP servers you are not using. This frees space in the tool budget so more Search Atlas tools can load.
  3. Raise the tool limit: In your Claude Code configuration, increase the maximum number of MCP tools allowed if your setup permits it, then reconnect.
  4. Reconnect the MCP server: Remove and re-add the Search Atlas MCP connection to force a fresh sync of the full catalog.
  5. Check your permissions: Confirm your Search Atlas plan and workspace role include the tools you expect. Some tools are only available on specific tiers.
  6. Search directly: If a tool is not shown in the list but you know its name, try calling it directly (for example, /onboard-client). Some clients keep tools available even when they are not displayed in the visible count.

✅ Confirming the Fix

After making changes, reload Claude Code and review the tool count again. It is normal for the number to still be slightly lower than the full published total because of client limits. What matters is that the specific tools you need — including /onboard-client — are now reachable. Test the tool you were missing to confirm it works end to end.

📌 Good to Know

  • A tool count that is lower than the maximum is not a bug on its own; it reflects client-side limits.
  • Keeping only the MCP servers you actively use gives Search Atlas tools the best chance to load fully.
  • Tool availability can change between releases, so staying updated is the most reliable way to keep the full catalog.