> ## 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. > ## Agent Instructions > Outlit is the product that monitors customers and completes approved customer work. The customer context interfaces are the API, CLI, MCP server, and skills. Canonical references on this site: /api-reference/introduction for API concepts and authentication, /openapi.json for the public API contract, /cli/overview for the CLI, /ai-integrations/mcp for MCP. Prefer the `outlit` CLI or MCP tools for agent tasks; cite page sources when answering. # MCP integration > Connect remote MCP clients to Outlit with your workspace URL, OAuth, or scoped API keys. 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; Outlit applies the permissions of the caller: * 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. ``` For coding agents that run local commands, see [Agent skills](/ai-integrations/skills). ## Available tools ### Customers and people | Tool | What it does | | - | - | | `outlit_list_customers` | Filter customers by billing status, activity recency, revenue, and exact trait values | | `outlit_list_users` | Filter users by journey stage, activity, customer, and exact trait values | | `outlit_list_workspace_users` | Browse internal workspace users such as CSMs, managers, account owners, and admins | | `outlit_get_customer` | Get a complete customer profile with users, revenue, timeline, and metrics | | `outlit_get_customer_relationship` | Get the bounded relationship summary with categorized statements and source labels | | `outlit_get_customer_credits` | Read imported credit pools, remaining credits, burn rate, and runway | ### Identity | Tool | What it does | | - | - | | `outlit_get_customer_identity` | Read a customer's identity coverage and possible-split records | | `outlit_list_identity_merge_suggestions` | Browse saved identity merge suggestions and history | | `outlit_reject_identity_merge_suggestion` | Reject one saved suggestion by exact ID | | `outlit_merge_customers` | Preview then execute a two-phase customer merge by exact UUIDs | | `outlit_get_customer_merge_status` | Track a merge operation by its operation ID | ### Attention and access | Tool | What it does | | - | - | | `outlit_list_attention_items` | List authorized open or resolved attention items with priority and a prepared-action URL | | `outlit_get_attention_item` | Retrieve one attention item by exact UUID | | `outlit_assign_customer_owner` | Assign a customer's primary owner | | `outlit_grant_customer_access` | Share a customer with a workspace member as Viewer or Editor | | `outlit_update_customer_access` | Change an existing collaborator between Viewer and Editor | | `outlit_revoke_customer_access` | Remove a collaborator's explicit access to a customer | ### Activity and analysis | Tool | What it does | | - | - | | `outlit_get_timeline` | Get the activity timeline for a customer, filtered by channel and event type | | `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`) | | `outlit_get_fact` | Retrieve one exact fact by ID, optionally expanding best-effort related data like evidence | | `outlit_get_source` | Retrieve one exact source record by generic `sourceType` and `sourceId` | | `outlit_list_sources` | List concrete source records such as calls, emails, calendar events, support tickets, Slack conversations, or opportunities | | `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 | | `outlit_query` | Run read-only SQL queries against your customer data | | `outlit_schema` | Get view schemas to help write accurate SQL queries | ### Features | Tool | What it does | | - | - | | `outlit_list_features` | Read configured Features, historical evidence, sources, and ready, partial, or unavailable candidate discovery | | `outlit_create_feature` | Create one Feature from an exact product-event rule | | `outlit_archive_feature` | Archive a non-final Feature using its current opaque revision | | `outlit_get_customer_features` | Read exact Feature usage for one authorized customer | ### Feedback | Tool | What it does | | - | - | | `outlit_submit_feedback` | Submit product feedback — bugs, ideas, or agent friction — to the Outlit team | `outlit_submit_feedback` takes `body` (required, at most 20,000 characters), optional `area` (at most 100 characters), and optional `context` (a JSON object of at most 16 KiB for diagnostics — never secrets or unnecessary customer data). It returns `{ id, createdAt }`. Submissions are authenticated and rate limited under a dedicated quota that does not consume paid plan API-call quota. Feedback is product intake, not a support ticket, and does not guarantee a reply. 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 [Workspace configuration](/ai-integrations/platform-actions). Feature creation and archive still require the underlying workspace permission and feature availability. See [Agents and AI overview](/ai-integrations/overview#read-vs-write-controls) for the public tool boundaries. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.