Skip to main content

MCP Configuration

The Model Context Protocol (MCP) is an open standard that allows AI assistants to connect to external tools and data sources. Calmo Local Bridge supports MCP servers, enabling you to extend Calmo’s capabilities with documentation lookup, specialized tools, and more.

What is MCP?

MCP provides a standardized way for AI applications to:
  • Access External Tools - Connect to specialized tools and services
  • Retrieve Documentation - Fetch up-to-date docs and code examples
  • Enable New Capabilities - Add sequential thinking, file access, and more
MCP Servers panel showing connected servers and tools

Viewing MCP Servers

The MCP Tools tab shows all configured servers:
  • Server Name - Identifier for the MCP server
  • Type - HTTP or STDIO transport
  • Tools Count - Number of tools provided by the server
  • Status - Connection status (green = connected)

Configuring MCP Servers

Accessing the Configuration

Click Edit MCP Config to open the configuration file:
MCP configuration file in editor
The configuration file is located at:
  • macOS: ~/Library/Application Support/Calmo Bridge/mcp.json
  • Windows: %APPDATA%\Calmo Bridge\mcp.json

Configuration Format

The configuration uses JSON format with an mcpServers object:
{
  "mcpServers": {
    "server-name": {
      // Server configuration
    }
  }
}

Server Types

Stdio Servers

Local processes that communicate via stdin/stdout. Best for npm packages and local tools.
{
  "mcpServers": {
    "mastra": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "@mastra/mcp-docs-server"],
      "env": {
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}
Configuration Fields:
FieldRequiredDescription
commandPath to executable (e.g., /usr/local/bin/npx)
argsArray of command arguments
envEnvironment variables for the process
disabledSet to true to disable without removing

HTTP/HTTPS Servers

Remote servers accessed over the network. Best for cloud-hosted services.
{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp",
      "headers": {
        "CONTEXT7_API_KEY": "your-api-key-here"
      }
    }
  }
}
Configuration Fields:
FieldRequiredDescription
urlFull URL to the MCP server endpoint
headersHTTP headers (e.g., API keys)
disabledSet to true to disable without removing

Example Configurations

Documentation Server (Context7)

Provides up-to-date documentation for any library:
{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp",
      "headers": {
        "CONTEXT7_API_KEY": "ctx7sk-xxxx-xxxx-xxxx"
      }
    }
  }
}
Tools Provided: resolve-library-id, get-library-docs

Mastra Documentation

Access Mastra.ai documentation, examples, and migration guides:
{
  "mcpServers": {
    "mastra": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "@mastra/mcp-docs-server"],
      "env": {
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}
Tools Provided: mastraDocs, mastraExamples, mastraBlog, mastraChanges, mastraMigration, and more

Sequential Thinking

Enables structured problem-solving through step-by-step reasoning:
{
  "mcpServers": {
    "sequential-thinking": {
      "command": "/usr/local/bin/npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sequential-thinking"
      ],
      "env": {
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}
Tools Provided: sequentialthinking

Complete Example

A full configuration with multiple servers:
{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp",
      "headers": {
        "CONTEXT7_API_KEY": "ctx7sk-xxxx-xxxx-xxxx"
      }
    },
    "mastra": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "@mastra/mcp-docs-server"],
      "env": {
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    },
    "sequential-thinking": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
      "env": {
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}

Managing Servers

Reloading Configuration

After editing the configuration:
  1. Save the mcp.json file
  2. Click Reload Servers in the MCP Tools tab
  3. Or wait for auto-detection (changes are automatically detected)
Reload Servers button

Disabling a Server

To temporarily disable a server without removing it:
{
  "mcpServers": {
    "server-name": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "some-server"],
      "disabled": true
    }
  }
}

Viewing Server Logs

Check the Logs tab for MCP server activity:
[15:36:34] [MCP Config] Found server: context7 (http)
[15:36:34] [MCP Config] Found server: mastra (stdio)
[15:36:35] [MCP:context7] Connected with 2 tools
[15:36:37] [MCP:mastra] Connected with 10 tools
[15:36:38] [MCP Registry] Active servers: 3
ServerTypeDescription
context7HTTPLibrary documentation and code examples
@mastra/mcp-docs-serverStdioMastra.ai documentation and examples
@modelcontextprotocol/server-sequential-thinkingStdioStructured reasoning and problem-solving
@modelcontextprotocol/server-filesystemStdioFile system read/write access
@modelcontextprotocol/server-githubStdioGitHub API integration
@modelcontextprotocol/server-slackStdioSlack messaging integration
Find more servers at the Awesome MCP Servers repository.

Windows Troubleshooting

On Windows, npx is a script that requires shell access. Wrap calls with cmd /c:
{
  "mcpServers": {
    "server-name": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@some/mcp-server"
      ]
    }
  }
}

Security Considerations

MCP servers run with your user permissions and may have network access. Only configure servers you trust.
Best Practices:
  • Review Server Code - Understand what servers do before adding them
  • Limit Permissions - Some servers request file system or network access
  • Secure API Keys - Keep API keys private; don’t commit config files to git
  • Monitor Logs - Watch for unexpected behavior in the Activity Log

Troubleshooting

Server Won’t Connect

  1. Check the command path - Ensure the executable exists at the specified path
  2. Verify npx - Run which npx to confirm location
  3. Check environment - Some tools need specific PATH configuration
  4. Review logs - Check the Logs tab for error messages

Server Connected But No Tools

  1. Wait for initialization - Some servers take time to load
  2. Check stderr - Look for startup errors in logs
  3. Verify package - Ensure the npm package name is correct

API Key Issues

  1. Check header format - Headers must be in the correct structure
  2. Verify key validity - Ensure the API key is active and has proper permissions
  3. Check URL - Confirm the server URL is correct

For MCP configuration help, contact our support team at [email protected].