MCP Server FAQ

A Catalyst Dynamic MCP Server dynamically loads only the tools required to fulfill your prompt, querying its directory at the time of invocation. This means you do not need to manually configure tools beforehand, and all 100+ Catalyst MCP tools remain accessible without hitting LLM tool limits. A Catalyst Custom MCP Server, on the other hand, requires you to manually select and configure the exact tools you need via the MCP console. Use a Custom MCP server when you have a well-defined, predictable set of operations.

No. The Catalyst MCP Server is designed specifically to let your LLM interact with and perform operations in the Catalyst console directly from your coding environment. Once connected and authorized, your LLM receives the context it needs through the configured MCP tools and can carry out your prompted actions without switching interfaces.

You can connect a Catalyst Custom MCP Server to Claude.ai, ChatGPT, Cursor, GitHub Copilot, and Windsurf. You can also connect it to any custom MCP client, provided it supports remote MCP servers and connects through HTTP or Streamable Transport.

The Dynamic MCP Server removes three common friction points: tool overload that causes hallucinations, the manual effort of selecting tools in the MCP console, and tool count limitations imposed by LLMs. Since only the tools relevant to your prompt are loaded at any given time, your LLM operates with focused context, resulting in more accurate and reliable outputs.

Neither server is inherently better than the other. Each is designed for a specific use case, and the right choice depends on the nature of your operation.

The Catalyst Dynamic MCP Server is best suited for exploratory or dynamic workflows where the full scope of required tools is not known in advance. It automatically identifies and loads only the tools needed for your prompt, giving your LLM access to all 100+ Catalyst MCP tools without manual configuration or the risk of tool overload causing hallucinations.

The Catalyst Custom MCP Server is best suited for targeted, well-defined operations where you know exactly which tools are required. By configuring only the necessary tools upfront via the MCP console, you keep the server lean, predictable, and optimized for that specific workflow.

In short, use the Dynamic MCP Server when you need flexibility and broad coverage. Use the Custom MCP Server when you need precision and control. Evaluate your use case first, and let that guide your choice.