MCP server

The Combeenation MCP server connects your AI agent to the Combeenation platform via the Model Context Protocol. With it, your agent can explore your configurator and make changes to its drafts.

Connection details

Setting	Value
URL	https://portal.combeenation.com/mcp
Transport	HTTP
Authentication	Authorization: Bearer <token>

<token> is a Combeenation API token. See here for how to create one.

An API token belongs to a single company. Use the token of the company that owns the configurator you're working on.

Setup in VS Code

The MCP server is configured per project in the file .vscode/mcp.json:

1. Open your project in VS Code.
2. Run the command MCP: Open Workspace Folder MCP Configuration from the command palette.
3. Add the following configuration:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "combeenation-api-token",
      "description": "Combeenation API token",
      "password": true
    }
  ],
  "servers": {
    "cbn-mcp": {
      "type": "http",
      "url": "https://portal.combeenation.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:combeenation-api-token}"
      }
    }
  }
}

4. Start the server: run the command MCP: List Servers, select your server and then Start Server. VS Code asks for your API token and stores it securely.

With this setup, the file contains no secret and can safely be committed to version control.

Token prompt not working

The inputs approach may not work in VS Code. If you aren't asked for your token or the server fails to authenticate, replace ${input:combeenation-api-token} with your actual token and remove the inputs section.

The file now contains a secret and must be removed from version control:

1. Add .vscode/mcp.json to your .gitignore file.
2. If the file is already tracked, run git rm --cached .vscode/mcp.json.

Never commit your API token

Anyone with access to your repository could use a committed token to access your company's data. Removing the token later doesn't help, as it stays in the git history. If a token was ever committed, revoke it immediately and create a new one.

Setup in other agents

Some agents, such as Claude Code or Cursor, don't read .vscode/mcp.json or can't prompt for the token. Add the connection details to the agent's own MCP configuration instead. Refer to your agent's documentation for the exact format.

As the configuration then contains your token, store it in one of these places:

• Project-level configuration (recommended): a configuration file in your project that is listed in .gitignore.
• User-level configuration: applies to all your projects. As a token belongs to a single company, this doesn't work if you work on configurators of several companies.

Check the connection

1. Make sure the server is running. In VS Code, run the command MCP: List Servers and check the status of cbn-mcp.
2. Check that the Combeenation tools are available in your agent's tool list.
3. Ask your agent something like "List the components of my configurator".

For the best results, also install the AI skills.