Integrations
Connect supported external AI tools to OptixLog over the Model Context Protocol (MCP).
OptixLog runs a remote Model Context Protocol server so supported AI tools can search and read your indexed Microsoft 365 and project knowledge. The MCP tools use the same retrieval paths as the product.
Endpoint and authentication
| Setting | Value |
|---|---|
| Endpoint | https://api.optixlog.com/mcp |
| Transport | Streamable HTTP, JSON-RPC 2.0 |
| Authentication | Static OptixLog API key in Authorization: Bearer sk-opt-... |
Self-hosted deployments use their own API host with the same /mcp path.
OAuth is not available yet
The MCP endpoint does not currently publish OAuth protected-resource metadata or accept OAuth access tokens. Native cloud connectors that require OAuth, including Claude Desktop remote connectors and ChatGPT apps, cannot connect to this bearer-only endpoint. Do not select an authless option: OptixLog rejects unauthenticated requests.
Verified client support
The following matrix was evaluated on July 10, 2026. Supported rows were exercised against a running OptixLog server, a real sk-opt- key, and a populated project corpus: each completed initialize, listed all six tools, and ran optixlog_search_project_knowledge successfully. Unsupported rows have no valid bearer configuration to execute.
| Client | Result | Verified path |
|---|---|---|
| Claude Code 2.1.195 | Supported | Direct HTTP with an environment-expanded Authorization header |
| Codex CLI 0.144.0 | Supported | Direct HTTP with --bearer-token-env-var |
| Cursor 3.10.20 | Supported with caveat | Direct HTTP with a literal bearer value in private mcp.json; remote-header environment interpolation failed in the tested version |
| Claude Desktop 1.19367.0 | Not supported | Native remote connectors require OAuth or authless; the tested mcp-remote bearer bridge returned 401 |
| ChatGPT Developer mode | Not supported | The native app flow cannot supply the OptixLog static bearer and OptixLog does not expose OAuth |
See each client guide for the exact tested configuration. The detailed evidence and auth rationale live in the repository's docs/integrations/mcp-auth-client-matrix.md.
Make an API key
Generate a key in Dashboard → API Keys → Create new key. The value is shown once and is prefixed sk-opt-. See Authentication for the difference between user and service keys.
Treat the key like a password
An OptixLog API key delegates the key owner's allowed actions and may expose indexed content. Keep it out of version control, use the narrowest practical scope, and rotate it if it leaks.
Tool surface
The server exposes four first-class tools plus two compatibility shims.
| Tool | Purpose |
|---|---|
optixlog_search_knowledge | Hybrid search across the organization's indexed Microsoft 365 corpus. |
optixlog_search_project_knowledge | Project-scoped imported-knowledge search, with optional routed GraphRAG. |
optixlog_get_document | Metadata and optional chunks for an indexed Microsoft 365 document. |
optixlog_list_sources | Microsoft 365 sites and drives indexed for the organization. |
search | Compatibility search result shape: id, title, url, and snippet. |
fetch | Fetch a chunk or joined document text by ID. |
Set up a supported client
Claude Code
Use an environment-expanded bearer header in .mcp.json.
Codex CLI
Register the server with --bearer-token-env-var.
Cursor
Use a private user-level mcp.json with the API key.
Claude Desktop
Not available until OptixLog supports MCP OAuth.
ChatGPT
Not available until OptixLog supports MCP OAuth.
Verify the endpoint
Replace sk-opt-REPLACE_ME with your key.
curl -fsS -X POST https://api.optixlog.com/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer sk-opt-REPLACE_ME" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jqThe response contains six tools. A 401 means the header is missing, malformed, expired, revoked, or was signed with a different deployment's API-key hash secret.