MCP Client Setup

This guide shows how to connect MCP clients to Mission Control.

MCP server URL

Use the Setup MCP flow to get the MCP server URL for your Mission Control tenant.

1. In Mission Control, open the user menu and select Setup MCP.

2. Copy the MCP server URL from the setup dialog.

The MCP server URL uses one of these formats:

• SaaS users: https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp
• Self-hosted users: https://your.domain.com/api/mcp

Choose an authentication method

Mission Control supports two MCP authentication flows:

• OAuth: Use an MCP client that supports OAuth for remote MCP servers.
• Access token: Create a Mission Control access token and add it to your MCP client configuration.

OAuth

OAuth

Use this approach when your MCP client supports OAuth for remote MCP servers.

Point the client at the MCP server URL.

Mission Control prefers Client ID Metadata Documents (CIMD) for OAuth client registration. Compatible clients use an HTTPS metadata URL as the client ID. Mission Control fetches that document during authorization.

Clients that do not support CIMD fall back to Dynamic Client Registration (DCR) at /oauth/register.

The client discovers the authorization server, registers with CIMD or DCR, and opens a browser for you to sign in. On the consent screen, check the client name and redirect address before you allow access.

The authenticating user needs the mcp:use permission.

Claude Code

Create or edit .mcp.json in your project root and add the Mission Control MCP server.

.mcp.json
{
  "mcpServers": {
    "mission-control": {
      "name": "mission-control",
      "type": "http",
      "url": "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
    }
  }
}

VS Code

Create or edit .vscode/mcp.json in your project root and add the Mission Control MCP server.

.vscode/mcp.json
{
  "servers": {
    "mission-control": {
      "url": "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
    }
  },
  "inputs": []
}

Claude Desktop Connectors

Claude Desktop supports remote MCP servers through Connectors.

1. In Claude Desktop, open Settings → Connectors.
2. Select Add → Custom connector.

The Connectors page lists existing web connectors and custom connectors.

The Add custom connector dialog creates a remote MCP connector.

3. In Name, enter Mission-Control.
4. In Remote MCP server URL, enter your MCP server URL.
5. Leave OAuth Client ID and OAuth Client Secret empty.
6. Select Add.
7. On the Connectors page, select Connect for the Mission Control connector.
8. Complete the authentication flow.

Mission Control tools appear in Claude Desktop after the OAuth flow completes.

Access Token

Access token

Use this approach when your MCP client does not support OAuth, or when you want to pass a Mission Control access token in the client configuration.

Create an access token

Use the Setup MCP flow to create an access token with MCP permissions.

1. In Mission Control, open the user menu and select Setup MCP.

2. Enter a token name.

3. Copy the generated config for your MCP client, or copy the token value.

info

Some MCP clients use the access token as a bearer token. Other MCP clients use Basic authentication with username token and password <token value>.

When you use the Authorization: Basic <base64_token> header, encode token:<token_value> as the base64_token value.

Configure a client

Claude Desktop

Use the Claude Desktop configuration file when you need to pass an MCP bearer token directly from Claude Desktop.

1. Open Claude Desktop settings.
2. Select Developer → Edit Config.
3. Add the Mission Control MCP server configuration.

claude_desktop_config.json
{
  "mcpServers": {
    "mission-control": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

4. Restart Claude Desktop.
5. Mission Control tools appear in the tools menu.

Claude Code

Claude Code CLI supports MCP through the .mcp.json configuration file.

Setup Steps

1. Create or edit the .mcp.json file in your project root or home directory
2. Add the Mission Control MCP server configuration:

.mcp.json
{
  "mcpServers": {
    "mission-control": {
      "name": "mission-control",
      "type": "http",
      "url": "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

3. Save the file and restart Claude Code
4. Mission Control tools will be available in your sessions

VS Code Copilot

GitHub Copilot Chat in VS Code supports MCP through the Copilot extensibility API.

Setup Steps

1. Ensure you have GitHub Copilot Chat installed in VS Code

2. Install the MCP extension for Copilot:

   code --install-extension github.copilot-mcp

3. Open VS Code settings (Cmd/Ctrl + ,)

4. Search for "Copilot MCP"

5. Add Mission Control configuration:

{
  "github.copilot.mcp.servers": {
    "mission-control": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-http",
        "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
      ],
      "env": {
        "AUTHORIZATION": "Basic YOUR_TOKEN_HERE"
      }
    }
  }
}

6. Reload VS Code window
7. In Copilot Chat, type @mcp to access Mission Control tools

Using MCP in Copilot Chat

• Use @mcp list to see available tools
• Use @mcp mission-control <command> to execute specific tools
• Example: @mcp mission-control query-catalog namespace=production

Cline

Cline supports MCP through its settings configuration.

Setup Steps

1. Install Cline extension in VS Code
2. Open VS Code settings (Cmd/Ctrl + ,)
3. Search for "Cline MCP"
4. Add Mission Control server configuration:

{
  "cline.mcpServers": {
    "mission-control": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-http",
        "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
      ],
      "env": {
        "AUTHORIZATION": "Basic YOUR_TOKEN_HERE"
      }
    }
  }
}

5. Reload VS Code window
6. Mission Control tools will be available in Cline chat

Continue.dev

Continue.dev supports MCP servers through its configuration file.

Setup Steps

1. Open Continue configuration

   • Click the gear icon in Continue sidebar
   • Or edit ~/.continue/config.json directly

2. Add Mission Control to the mcpServers section:

{
  "mcpServers": [
    {
      "name": "mission-control",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-http",
        "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
      ],
      "env": {
        "AUTHORIZATION": "Basic YOUR_TOKEN_HERE"
      }
    }
  ]
}

3. Restart Continue
4. Mission Control tools will be available in chat

Zed Editor

Zed supports MCP through its assistant configuration.

Setup Steps

1. Open Zed settings (Cmd/Ctrl + ,)
2. Navigate to Assistant settings
3. Add Mission Control MCP configuration:

{
  "assistant": {
    "mcp": {
      "servers": {
        "mission-control": {
          "command": "npx",
          "args": [
            "-y",
            "@modelcontextprotocol/server-http",
            "https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp"
          ],
          "env": {
            "AUTHORIZATION": "Basic YOUR_TOKEN_HERE"
          }
        }
      }
    }
  }
}

4. Restart Zed
5. Mission Control tools will be available in the assistant

Direct HTTP

For custom integrations or clients that support direct HTTP connections:

Connection Details

• Base URL: https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp
• Protocol: HTTP with SSE (Server-Sent Events)
• Authentication: Basic token in Authorization header

Example Request

curl -X POST https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp \
  -H "Authorization: Basic YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {}
    },
    "id": 1
  }'

WebSocket Connection

For clients supporting WebSocket:

const ws = new WebSocket(
  'wss://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp/ws',
  {
    headers: {
      Authorization: 'Basic YOUR_TOKEN_HERE'
    }
  }
)

ws.on('open', () => {
  ws.send(
    JSON.stringify({
      jsonrpc: '2.0',
      method: 'initialize',
      params: {
        protocolVersion: '2024-11-05',
        capabilities: {}
      },
      id: 1
    })
  )
})

Troubleshooting

Common Issues

1. Connection Refused

   • Verify the server URL is correct
   • Check if you're behind a firewall or proxy
   • Ensure the token has proper permissions

2. Authentication Failed

   • Verify token is valid and not expired
   • Ensure the user or token has the mcp:use permission
   • Check if Basic prefix is included

3. Tools Not Appearing

   • Restart the client application
   • Check client logs for errors
   • Verify MCP server is properly configured

Testing Connection

You can test your MCP connection using the MCP CLI:

npx @modelcontextprotocol/cli connect \
  --transport http \
  --url https://mc.<org-id>.workload-prod-eu-02.flanksource.com/mcp \
  --header "Authorization: Basic YOUR_TOKEN_HERE"

Next Steps

Once connected, explore the available tools:

• Catalog Tools - Query and manage configuration items
• Connection Tools - Manage connections and integrations
• Playbook Tools - Execute and manage playbooks