القائمة
Dynamically manage MCP server limits by toggling disabled states in mcp_config.json. Use when hitting the 100-tool limit, or when needing a specific MCP server that is currently disabled.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.
Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, or checking props and examples. Triggers on "what component", "how do I make", "WDS", "show me props", or component names like Button, Card, Modal, Box, Text.
Creates HTTP endpoints for Wix CLI apps. Use only when the user specifically asks for a backend endpoint. Use when building REST API endpoints, backend HTTP handlers, or server-side logic. Triggers include backend API, HTTP endpoint, HTTP methods, form handling, file uploads.
Create backend event extensions that respond to Wix events. Use when implementing handlers that run when specific conditions occur on a site. Triggers include event extension, backend event, webhook handler.
| name | MCP Manager |
| description | Dynamically manage MCP server limits by toggling disabled states in mcp_config.json. Use when hitting the 100-tool limit, or when needing a specific MCP server that is currently disabled. |
The agent ecosystem relies on many Model Context Protocol (MCP) servers, each exposing multiple tools. AI LLMs have a hard limit of 100 tools per context window. When the combined tool count from all active MCP servers exceeds 100, the context rejects the overflow tools, meaning some servers silently fail to load.
You must dynamically manage the user's mcp_config.json file to keep the total tool count under 100. If you need an MCP server that is currently inactive, or if you notice tools missing, follow this workflow to "flip the switch."
Locate the Config
Read the user's MCP configuration file located at: /Users/brendan/.gemini/antigravity/mcp_config.json
Identify the Target & The Bloat
wix-mcp-remote, github-mcp-server, signnow).chrome-devtools-mcp is a primary target for disabling because it adds over 25 tools alone.Edit the JSON File
Use your file editing tools (multi_replace_file_content or replace_file_content) to toggle the "disabled": true flag on or off.
"disabled": true to its block."disabled": true from its block or set it to "disabled": false.Prompt for Context Refresh MCP tools are only injected at the start of a turn. Once you save the file, you MUST ask the user to respond (e.g., "I've swapped the MCP servers. Please reply with 'go ahead' to refresh my context.") before you attempt to use the newly enabled tools.
When disabling a server, your edit should look like this:
"chrome-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
],
"disabled": true
}