Skip to main content

Authentication

Fynd Boltic MCP supports token-based authentication to restrict access to your MCP server. When enabled, all incoming requests must include a valid bearer token or they will be rejected with a 401 Unauthorized response.

Add Authentication​

  • Go to the Overview page of your MCP server. Click Add Authentication.

  • A token is generated and displayed. Copy it and store it securely.

tip

The token is always visible from the Overview page of your MCP server.

Using the Token​

Pass the token in the Authorization header of every request to your MCP server:

Authorization: Bearer <your-token>

Client setup​

When connecting via Connect MCP, the token is automatically included in the setup instructions for each client.

HTTP Stream

{
    "mcpServers": {
        "My MCP Boltic MCP": {
            "url": "https://<your-mcp-url>/mcp",
            "headers": {
                "Authorization": "Bearer <your-token>"
            }
        }
    }
}

STDIO (mcp-remote)

{
    "mcpServers": {
        "My MCP Boltic MCP": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://<your-mcp-url>/mcp",
                "--header",
                "Authorization: Bearer <your-token>"
            ]
        }
    }
}

Cursor / Claude / Windsurf CLI

npx @boltic/cli@latest mcp setup <url> "<name>" --client cursor --header "Authorization: Bearer <your-token>"

Manage Authentication​

Once a token is set, click Manage Authentication on the Overview page to access the following options.

Rotate Token​

Generates a new token and immediately invalidates the existing one. Any integrations using the old token will stop working until updated with the new token.

Remove Authentication​

Removes the token entirely. Your MCP server becomes publicly accessible without any authentication.

warning

Rotating or removing a token takes effect immediately. Make sure to update all connected clients before rotating.