Skip to content

MCP Servers

The Model Context Protocol (MCP) extends AI capabilities with external tools. Connect MCP servers to give your AI access to specialized functions like web search, file operations, API integrations, and more.

MCP is a standard protocol that lets AI models interact with external tools and services. MCP servers provide:

  • Tools - Functions the AI can call (search, calculate, fetch data)
  • Resources - Data the AI can access (files, databases, APIs)
  • Prompts - Pre-built prompt templates

Catalyst supports three types of MCP servers:

Local processes that communicate via standard input/output. Good for:

  • Local development tools
  • File system access
  • Command-line utilities

Web-based servers accessed via HTTP requests. Good for:

  • Remote services
  • Cloud-hosted tools
  • REST API integrations

Real-time streaming connections. Good for:

  • Live data feeds
  • Long-running operations
  • Real-time updates
  1. Navigate to MCP Servers from the sidebar menu
  2. Click Add Server
  3. Configure the server:
    • Name - A friendly name
    • Type - STDIO, HTTP, or SSE
    • Configuration - Connection details (varies by type)
Name: My Web Search
Type: HTTP
URL: https://mcp.example.com
Name: Local Tools
Type: STDIO
Command: npx @modelcontextprotocol/server-filesystem

MCP servers may require authentication:

Enter your API token in the authentication section. The token is sent with each request.

Provide a username and password for basic authentication.

For servers requiring OAuth:

  1. Click Setup OAuth on the server page
  2. You’ll be redirected to authorize access
  3. Tokens are stored and refreshed automatically
  1. Open a chat session
  2. Click the Tools dropdown in the input area
  3. Select tools from your connected MCP servers
  4. The AI can now use those tools when responding
  1. Open a prompt template
  2. Click Add MCP Tool in the tools panel
  3. Select tools to make available
  4. Tool information is included in the template context

The server list shows connection status:

  • Active - Connected and ready
  • Inactive - Not connected
  • Error - Connection failed
  • Connecting - Establishing connection

Click Initialize to connect to an inactive server.

Test tools before using them in production:

  1. Open the server detail page
  2. Click Test on any tool
  3. Enter test parameters
  4. View the tool’s response

Click Disconnect to close the connection to a server. You can reconnect later.

Use the health check to verify a server is responding correctly.

Remove a server and all its stored configuration.

Some commonly used MCP servers:

  • Filesystem - Read and write local files
  • GitHub - Interact with GitHub repositories
  • Slack - Send messages and read channels
  • Google Drive - Access Google Drive files
  • PostgreSQL - Direct database queries

Check MCP Server Registry for more options.

  • Verify the URL or command is correct
  • Check authentication credentials
  • Ensure the server is running
  • Check network/firewall settings
  • Refresh the server connection
  • Check server logs for errors
  • Verify the server supports tool discovery
  • Re-authorize the connection
  • Check token expiration
  • Verify OAuth client configuration