App-Based Tool Filtering

The MCP server intelligently filters which tools are available based on the apps enabled in your workspace. Instead of exposing all 86 tools, it only registers tools for the apps you actually use.

How It Works

At startup, the server goes through these steps:

1. Authenticates your API key
2. Lists all workspaces you belong to
3. Queries enabled apps per workspace (respecting beta-tester visibility)
4. Computes the union of enabled app IDs across all your workspaces
5. Registers only the matching tool groups

Example

If your workspace has 4 apps enabled — BookMe, Stackr, Changelog, and Workflows — you will see approximately 25 tools instead of the full 86. Tools for disabled apps like CRM, Assets, or Tickets are not exposed to the AI agent at all.

This keeps the tool list focused and reduces noise for your AI assistant, leading to more accurate tool selection.

Refreshing Tool Visibility

When app visibility changes in Settings → Apps, you need to restart the MCP server for the change to take effect. The server reads enabled apps once at startup and caches the result for the session.

How to Restart

• Cursor — open the Command Palette and run "MCP: Restart Server", or restart the IDE
• Claude Code — stop and re-run the claude CLI
• Windsurf / Antigravity — restart the IDE or the MCP process

Common Tools

Three tools are always available regardless of app configuration:

The search tool respects app visibility — it only returns results from enabled modules.