OptixLog Docs
Integrations

Claude Code

Add OptixLog to Claude Code over Streamable HTTP with a static API key.

This configuration was verified with Claude Code 2.1.195. It completed the MCP handshake, listed six tools, and returned a cited project-search result.

Export the API key

Generate a key at Dashboard → API Keys, then export it in the environment that launches Claude Code:

export OPTIXLOG_API_KEY="sk-opt-REPLACE_ME"

Add the project configuration

Claude Code expands environment variables in HTTP headers. The variable reference can be committed; the secret stays outside the repository.

.mcp.json
{
  "mcpServers": {
    "optixlog": {
      "type": "http",
      "url": "https://api.optixlog.com/mcp",
      "headers": {
        "Authorization": "Bearer ${OPTIXLOG_API_KEY}"
      }
    }
  }
}

Approve and verify the server

Restart Claude Code from the shell where the variable is set. Approve the project server when prompted, then run:

claude mcp get optixlog

Ask Claude to use optixlog_search_project_knowledge with one of your project IDs, or optixlog_search_knowledge for the organization-wide Microsoft 365 corpus.

Authentication failures

When a configured Authorization header is rejected, Claude Code reports a connection failure instead of falling back to OAuth. Confirm that the environment variable is present and that the key is active and belongs to this OptixLog deployment.

On this page