Skip to main content
Connect to the production MCP server using your LithoBlocks account. See Environments and availability for the separate staging environment.

​
Connect

Use a client that supports remote MCP over HTTP. Add:
Choose OAuth when supported. Sign in to the matching LithoBlocks environment, review consent, and enable the connection in your client. For API-key authentication, configure an Authorization: Bearer header using the client’s secure credential mechanism. In Claude’s web or desktop app, use Settings → Connectors → Add custom connector where available. Plan and organization policies determine whether custom connectors are enabled; see the client’s connector documentation. For Claude Code, add the server:
Complete authentication through the client before calling protected tools. Do not assume a separately published plugin is required or available.

​
Capabilities

Use the server’s tool listing as the current inventory rather than a fixed count. Each protected tool checks the relevant API scopes and organization access.

​
Work safely

Discover the template and input schema before supplying data. Confirm the intended destination and content before a send. Tool annotations help clients identify effects; your client/application must still enforce its confirmation policy. Preserve the operation’s idempotency_key and body when retrying a write. A timeout or uncertain result needs reconciliation before another send. Read/validate first, then inspect history after an action. validate_template returns free diagnostics without rendered output. Use compile_template for a rendered preview (one credit).

​
Disconnect and troubleshoot

Review authorized connections under Integrations → Connected apps and revoke the relevant client. API-key connections are revoked through API Keys instead. OAuth revocation and API-key cache lifetimes are different; see API keys. For authentication failures, check the environment, account, and client transport. For missing tools, refresh discovery. For 403 responses, inspect the required scope. Report the request ID and client version to support without sending credentials.