Outlit

What Outlit MCP server does

The Outlit MCP server gives agent workflows access to customer intelligence collected and modeled by Outlit. Outlit is designed for customer-success teams that need to monitor account activity, identify churn risk, find expansion opportunities, and review attention items with supporting evidence.

The repository at github.com/OutlitAI/outlit-sdk is not the hosted MCP implementation. It contains the public SDK and integration packages used to send customer signals to Outlit and query customer context from agent workflows. The hosted MCP service and its discovery metadata are published separately under mcp.outlit.ai.

How it works

Applications can send identity information and product events through the browser, Node.js, core, or Rust SDK surfaces. Browser tracking can include page views, while server-side integrations can record events from APIs, jobs, webhooks, CLIs, and other JavaScript runtimes. Events may include customer IDs, user details, traits, and event properties.

Agent integrations can use the typed contracts and client helpers in @outlit/tools. The @outlit/pi package provides Outlit customer intelligence tools and skill guidance for Pi agents. The hosted MCP connection uses Outlit's remote service and OAuth metadata; the repository directs implementers to Outlit's canonical MCP documentation and discovery endpoints rather than embedding generated server metadata.

Setup and configuration

Use the package that matches the application surface:

• Install @outlit/browser for browser applications and supported frontend frameworks.
• Install @outlit/node for Node.js servers and server-side runtimes.
• Install @outlit/core for lower-level custom SDK implementations.
• Install @outlit/tools for custom API or agent integrations using typed Outlit tool contracts.
• Install @outlit/pi for Pi agents.
• Install @outlit/cli for terminal-based Outlit workflows.
• Add the outlit Rust crate for Rust backends, CLIs, and Tauri backends.

Browser and Node examples initialize the SDK with an Outlit public key. Applications then identify users or customer accounts and track relevant events. Node applications can call flush() before shutdown so queued events are sent. Remote MCP clients should follow Outlit's MCP guide for workspace URLs and OAuth rather than treating this SDK repository as the server package.

Tools and capabilities

The Outlit MCP server fits workflows that need to:

• Query customer context from agent workflows.
• Send customer identities and product activity into Outlit through SDK integrations.
• Track browser page views and application events.
• Provide customer IDs, user traits, and customer traits.
• Use typed customer-intelligence tool contracts in custom integrations.
• Build Pi agents with Outlit tools and associated skill guidance.
• Inspect customer-success attention items related to churn risk or expansion opportunities.

The SDK also supports event queueing, batching and flushing, persistent identity, browser auto-tracking, middleware integration, and TypeScript type definitions. These are SDK capabilities rather than claims about additional MCP tools exposed by the hosted service.

Limitations and notes

The repository does not contain the hosted remote MCP server implementation. It is a public SDK and developer integration monorepo, so installing one of its packages does not by itself run an MCP server. Use Outlit's canonical documentation, MCP registry entry, server metadata, and server card for remote MCP discovery and connection details.

The supplied material does not enumerate the hosted MCP server's individual tool names, transport requirements, authentication variables, or supported client applications. It also does not provide a license declaration for the repository. Billing status should come from verified integrations such as Stripe rather than authoritative SDK commands.