> ## Documentation Index
> Fetch the complete documentation index at: https://docs.outlit.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP Integration
> Connect remote MCP clients to Outlit with your workspace URL, OAuth, or scoped API keys
## What is the Outlit MCP Server?
Outlit's MCP server lets MCP-compatible clients query customer data, manage customer ownership and access, and retrieve revenue metrics, timelines, facts, search results, and SQL analytics over a remote MCP connection.
The Outlit CLI is not required for MCP setup. Use the workspace MCP URL directly in your MCP client.
## Authentication Model
Outlit's remote MCP endpoint supports both OAuth and scoped Outlit API keys. Both authentication methods expose the same public tool catalog; the difference is how Platform decides what the caller may do:
* OAuth calls use the signed-in member's current workspace permissions and customer access.
* API-key calls use the key's current workspace and explicit grants.
For most interactive MCP clients, OAuth is the simplest setup. In practice that means:
* you add the workspace MCP URL to your client
* you do not paste API keys or bearer headers into config files
* the client opens an OAuth sign-in flow and stores the resulting session
Headless clients that cannot complete OAuth may send an Outlit API key as their bearer credential. A tool remains unavailable unless the member permissions or API-key grants authorize its underlying command.
## Connect Your MCP Client
Open [Settings > CLI & MCP](https://app.outlit.ai/settings/workspace/mcp) and copy the workspace-specific MCP URL for the workspace you want to connect.
It looks like:
```text theme={null}
https://mcp.outlit.ai/w//mcp
```
Use your client's remote MCP / connector / server settings and add the Outlit URL directly.
For clients that accept raw JSON config, the shape is typically:
```json theme={null}
{
"mcpServers": {
"outlit": {
"url": "https://mcp.outlit.ai/w//mcp"
}
}
}
```
No `Authorization` header is needed for OAuth-based customer-intelligence tools.
After you add the server, your client should prompt you to sign in to Outlit and authorize access for that workspace.
Ask your client:
```text theme={null}
Show me the available Outlit analytics views.
```
Use [Agent Skills](/ai-integrations/skills) for coding agents like Claude Code, Codex, and Gemini CLI. Use MCP when your primary surface is an MCP client such as Cursor, VS Code, or another remote-MCP connector.
## What Tools Are Available?
| Tool | What it does | Example prompt |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| `outlit_list_customers` | Filter customers by billing status, activity recency, revenue, and exact trait values | "Show me paying enterprise customers with `segment=enterprise` who haven't been active in 30 days" |
| `outlit_list_users` | Filter users by journey stage, activity, customer, and exact trait values | "Find all signed-up users at Acme Corp with `role=admin` who went inactive this week" |
| `outlit_list_workspace_users` | Browse internal workspace users such as CSMs, managers, account owners, and admins | "List workspace users who own customers in the enterprise segment" |
| `outlit_get_customer` | Get a complete customer profile with users, revenue, timeline, and metrics | "Get the full profile for acme.com including their users and revenue" |
| `outlit_assign_customer_owner` | Assign a customer's primary owner | "Make Alex the primary owner of Acme" |
| `outlit_grant_customer_access` | Share a customer with a workspace member as Viewer or Editor | "Give Alex Editor access to Acme" |
| `outlit_update_customer_access` | Change an existing collaborator between Viewer and Editor | "Change Alex's access to Acme to Viewer" |
| `outlit_revoke_customer_access` | Remove a collaborator's explicit access to a customer | "Remove Alex's access to Acme" |
| `outlit_get_timeline` | Get the activity timeline for a customer, filtered by channel and event type | "Show me Acme Corp's email and Slack activity from the last 7 days" |
| `outlit_list_facts` | Retrieve structured customer facts with status, source type, public fact type and category, occurrence time filters, pagination, and source provenance (`sourceMetadata` includes `sourceType`, `sourceId`, `sourceOccurredAt`, `sourceQuote`, and `permalink`) | "Show me active contact-departure facts for acme.com from calls last quarter" |
| `outlit_get_fact` | Retrieve one exact fact by ID, optionally expanding best-effort related data like evidence | "Get fact\_123 with evidence" |
| `outlit_get_source` | Retrieve one exact source record by generic `sourceType` and `sourceId` | "Open the support ticket source for ticket\_456" |
| `outlit_list_sources` | List concrete source records such as calls, emails, calendar events, support tickets, Slack conversations, or opportunities | "List Acme's support tickets and calls from January" |
| `outlit_search_customer_context` | Search across customer facts, emails, calls, calendar events, support tickets, Slack conversations, and CRM opportunities using natural language. Returns grouped artifact-level matches for `source` and `fact` results, with `sourceTypes` and time-range filters | "What pricing concerns does Acme have?" |
| `outlit_query` | Run read-only SQL queries against your customer data | "Which channels lead to the most revenue?" |
| `outlit_schema` | Get view schemas to help write accurate SQL queries | "Show me the available analytics views" |
| `outlit_list_features` | Read configured Features, historical evidence, sources, and ready, partial, or unavailable candidate discovery | "Show me our Features and their usage over the last 12 weeks" |
| `outlit_create_feature` | Create one Feature from an exact product-event rule | "Create a Feature for the `report_exported` event" |
| `outlit_archive_feature` | Archive a non-final Feature using its current opaque revision | "Archive this Feature after confirming another active feature remains" |
| `outlit_get_customer_features` | Read exact Feature usage for one authorized customer | "Which Features has Acme used in the last 12 weeks?" |
MCP registers the entire public catalog, including customer ownership/access, Features, and the safe destination, integration setup/status, activation, and workspace-settings capabilities described in [Platform Capabilities](/ai-integrations/platform-actions). Feature creation and archive still require the underlying workspace permission and feature availability. Generic agent, automation, signal, identity-merge, notification-send, credential, and destructive integration operations are not public tools.