OptixLog Docs
Integrations

Cursor

Add OptixLog to Cursor with a private user-level MCP configuration.

This configuration was verified with Cursor 3.10.20. Cursor listed all six tools and completed a project knowledge search.

Keep this file private

The tested Cursor version sent a literal bearer value correctly, but ${env:OPTIXLOG_API_KEY} in a remote HTTP header was sent without a usable token and fell into OAuth discovery. Store the literal key only in your user-level config, never in a repository.

Add the user configuration

Edit ~/.cursor/mcp.json and merge in the optixlog entry:

~/.cursor/mcp.json
{
  "mcpServers": {
    "optixlog": {
      "type": "http",
      "url": "https://api.optixlog.com/mcp",
      "headers": {
        "Authorization": "Bearer sk-opt-REPLACE_ME"
      }
    }
  }
}

On macOS or Linux, restrict the file to your user:

chmod 600 ~/.cursor/mcp.json

Approve and inspect the tools

Use Cursor Settings → Tools & MCP to enable optixlog, or verify from the terminal:

cursor agent mcp enable optixlog
cursor agent mcp list-tools optixlog

The second command should report six tools.

In Agent mode, ask Cursor to use optixlog_search_project_knowledge with a project ID, or optixlog_search_knowledge for the organization-wide Microsoft 365 corpus.

On this page