Settings > Developer (/settings/developer) is the home for everything programmatic: usage, API keys, logs, webhooks and the MCP server. It is available to workspace admins.
The pages
- Overview: today's API usage against your plan's daily limit, a 30-day request chart, 24-hour error rate and median latency, and links to the API reference.
- API keys: create service keys with per-object scopes, a description and an expiry; see when each was last used; rotate or revoke.
- Logs: every API call and webhook delivery, filterable by status, method, key, path, endpoint, event and date, with a detail drawer and CSV download.
- Webhooks: your endpoints with 24-hour delivery health; send a test, pause or resume, delete, and resend recent deliveries.
- MCP: the endpoint address, ready-to-paste configuration for Claude Code, Claude Desktop and generic HTTP clients, the tool and scope table and recent MCP calls.
Scoped service keys
A service key carries per-object scopes such as contacts:read, contacts:write, deals:read, tickets:read, notes:write, tasks:write and knowledge:read. Grant only what the integration needs. The secret is shown once, stored only as a hash, and every key event is recorded in the audit log. Expiry presets run from 30 days to 1 year, or never.
Trace ids and logs
Every API response carries an X-Limnn-Trace-Id header, and the same id is sent with webhook deliveries. Search a trace id in Logs to find the matching request or delivery. Logs record metadata only (never request bodies or secrets) and are kept for 30 days; daily usage counters are kept for 90 days.
X-Limnn-Trace-Id: <trace id>Rate limits
Each plan has a daily request allowance shared by the API and MCP. Going slightly over is logged but allowed; requests are refused with HTTP 429 and a Retry-After header only once usage passes 20% above the limit.
Connect an AI assistant with MCP
The Limnn MCP server lets AI tools that speak the Model Context Protocol work with your CRM. It uses Streamable HTTP and authenticates with a service key.
Endpoint: https://app.limnn.com/api/mcp
claude mcp add --transport http limnn https://app.limnn.com/api/mcp \
--header "Authorization: Bearer <your service key>"- Read tools: search_contacts, get_record, list_deals, list_tickets and search_knowledge.
- Write tools: create_note and create_task, available only when the key holds notes:write or tasks:write.
- Everything is scoped to your workspace, writes are attributed to the key's owner, and writes stop working if that user is deactivated.
- Every MCP call is logged with its trace id.
- 1Create a service key with only the scopes the assistant needs, for example contacts:read, deals:read and notes:write.
- 2Open Settings > Developer > MCP and copy the snippet for your client.
- 3Paste your key in place of the placeholder and add the server to Claude Code, Claude Desktop or another MCP client.
- 4Ask the assistant to search a contact, then check the call in Logs.