OuterSignal MCP Connector

Last updated: 2026-10-31

What it does

The OuterSignal MCP connector lets an AI assistant read analytics about your own OuterSignal organization: personas, products, and aggregate facts about your customer base. Every tool is read-only. The connector cannot create, change, or delete anything in your OuterSignal account or your store.

Server URL: https://app.outersignal.com/api/mcp

For what each returned number counts, see the MCP metric dictionary.

Tools

Most tools accept an optional date range (YYYY-MM-DD) and an organization identifier, which the Connection tool returns. Without one, a tool answers for the default organization chosen at consent. Each group lists the permission its tools require.

Every tool is read-only and declares readOnlyHint to the assistant. None creates, changes, or deletes data.

Persona analytics (requires `mcp:read.personas`)

list_active_personas · List active personas: IDs, names, and descriptions of every persona that has assigned customers.
get_persona_summary · Persona summary metrics: Customer count, revenue, AOV, lifetime LTV, and lifetime repeat rate for each persona, plus brand-level totals.
get_persona_comparison · Compare personas: All personas side by side: customer count, revenue share, AOV, lifetime LTV, lifetime repeat rate, and return rate.
get_revenue_distribution · Revenue distribution by persona: How revenue is split across personas.
get_persona_overview · Persona overview: Customer count, revenue metrics, and behavioral data for one persona.
get_persona_demographics · Persona demographics: Age distribution, gender split, and other demographic attributes for one persona.
get_persona_geographic · Persona geographic distribution: Where one persona’s customers are located, by country, state, and city.
get_persona_professional · Persona professional profile: Top job titles, employers, industries, and schools for one persona, and a distribution of estimated property value.
get_persona_revenue · Persona revenue analytics: Revenue trends, order frequency, and monetary distribution for one persona.
get_persona_radar · Persona radar metrics: Normalized scores for one persona across dimensions such as spending, loyalty, and engagement.
get_persona_products · Persona product affinity: Top purchased products and purchase patterns for one persona.
export_persona_summary · Export persona summary: Persona summary data as structured JSON, including revenue net of refunds, refunded revenue, and return rate. Can be limited to chosen personas.

Customer base (requires `mcp:read.personas`)

Aggregate counts only: these tools return no individual customer, name, email, handle, or exact follower count. A tool refuses when the brand has fewer than 30 enriched customers in scope, and a group of fewer than 25 customers is withheld.

get_audience_professions · Customer base professions: Top job titles, industries, employers, and schools across all enriched customers, with a count and percent for each.
get_audience_follower_distribution · Customer base follower distribution: Enriched customers grouped by their largest follower count on Instagram, TikTok, YouTube, or X.
get_audience_platform_presence · Customer base platform presence: Share of enriched customers with a profile on Instagram, TikTok, YouTube, X, LinkedIn, and Facebook.
get_audience_executive_share · Customer base executive share: Share of enriched customers whose current job title names an executive, founder, or C-suite role.

Discounts (requires `mcp:read.personas`)

Aggregate counts only. A group of fewer than 25 buyers is withheld.

get_discount_split_by_demographic · Discount split by demographic: Discounted and full-price buyers grouped by age bracket or gender, with the discounted share and discount depth for each group.

Products (requires `mcp:read.products`)

search_products · Search products: Up to 50 products with buyer counts, revenue, AOV, and persona breakdowns, optionally filtered by product name.
get_product_detail · Product detail analytics: Analytics for one product: buyer demographics, professional attributes, social profiles, and purchase behavior.
compare_products · Compare products: Two or three products side by side across demographic, professional, and behavioral dimensions, with audience overlap between them.
get_product_next_purchases · Predicted next purchase: What buyers of one product purchase next, by age, gender, affluence, or persona, with conversion rate, lift, and median days to the next purchase.

Product intelligence (requires `mcp:read.products`)

get_product_intelligence_stats · Product intelligence stats: Brand-level totals: products, revenue, average order value, unique buyers, the share of buyers researched, and the span of order history.

Connection (requires `mcp:read`)

list_organizations · List available organizations: The organizations this connection can access, the identifier to pass as the organization argument, and which one is the default.

Setup

Claude.ai and Claude Desktop

Open connectors. In Claude, go to Customize, then Connectors.
Add a custom connector. Select + Add, then Add custom connector.
Enter the server. Name it OuterSignal, enter https://app.outersignal.com/api/mcp as the server URL, and select Continue.
Keep the detected authentication. Claude detects OuterSignal’s OAuth settings. Keep them, choose to sign in, and select Add.
Sign in. Sign in to OuterSignal and approve the consent screen. To use the connector in a chat, select +, then Connectors, and turn OuterSignal on.

On Team and Enterprise plans, an owner adds the connector under Organization settings, then Connectors. Members then select Connect under Customize, then Connectors.

Claude Code

Run this in a terminal:

claude mcp add --transport http outersignal https://app.outersignal.com/api/mcp

Then run /mcp in Claude Code, select OuterSignal, and sign in to approve the connection.

ChatGPT

Open Plugins. Go to ChatGPT Plugins at chatgpt.com/plugins.
Add a custom MCP server. Select the plus button, then Add custom MCP server. Enter OuterSignal as the name and a short description.
Enter the server. Under Connection, enter https://app.outersignal.com/api/mcp as the server URL.
Configure authentication. Configure authentication (OuterSignal uses OAuth), review the risk warning, and select I understand and want to continue.
Create and install. Select Create as a plugin, review the tools ChatGPT discovered, and install the plugin.
Use it. Start a new chat, type @, and select OuterSignal. Sign in to OuterSignal and approve the consent screen when asked.

Your ChatGPT account and workspace policies decide whether you can add a custom MCP server.

Authentication and permissions

The connector uses the OAuth 2.1 authorization code flow with PKCE (S256 only) and dynamic client registration, so an assistant registers itself and needs no client secret. Assistants discover the endpoints at https://app.outersignal.com/.well-known/oauth-authorization-server.

When you connect, you sign in to OuterSignal and see a consent screen. It shows the assistant’s name, your account, and your organization. If you belong to more than one, you pick the default brand; the connection can reach every brand listed there. You then choose which permissions to grant. At least one is required.

The assistant also receives your email address and an account identifier, and the consent screen says so. It reads them from the userinfo endpoint, https://app.outersignal.com/api/mcp/oauth/userinfo, to know which OuterSignal user is connected.

Permissions the connector can be granted
Scope	Name	Allows
mcp:read.personas	Persona analytics	Read persona summaries, demographics, geography, and revenue by persona
mcp:read.products	Product analytics	Search your products and read product details and comparisons
mcp:read	Persona and product analytics	Grants both scopes above. Not a separate toggle on the consent screen; Claude.ai requests it, and list_organizations needs it

No permission to change data can be granted. The assistant only sees the tools its granted permissions allow; list_organizations needs both Persona analytics and Product analytics.

Token lifetimes

Authorization codes expire after 10 minutes and work once.
Access tokens expire after 7 days.
Refresh tokens expire after 30 days and are replaced each time they are used.

Revoking access

In OuterSignal, go to Settings, then Integrations, open the connected assistant, and choose Revoke access. Do this from the organization you were in when you connected.
An assistant can revoke its own tokens at https://app.outersignal.com/api/mcp/oauth/revoke (OAuth token revocation, RFC 7009).
A revoked token stops working immediately.
To stop using the connector, remove OuterSignal from the assistant: in Claude, under Customize, then Connectors; in ChatGPT, in the plugin's settings. To be sure its tokens end, also revoke access in OuterSignal.

Who can use it

You need an OuterSignal account that belongs to an organization.
AI tool connections must be enabled for that organization.
Tools are listed only for an organization on a paid OuterSignal plan. On a free plan the connector lists no tools.
These 8 tools stay hidden until persona tagging is active: Revenue distribution by persona, Persona overview, Persona demographics, Persona geographic distribution, Persona professional profile, Persona revenue analytics, Persona radar metrics, Persona product affinity.

Example prompts

Which personas brought in the most revenue since January 1?
Compare the demographics of my two largest personas.
What do buyers of my best-selling product purchase next, by age?
What share of my customers hold executive titles?
Do discounted buyers skew younger than full-price buyers?

Limits and troubleshooting

Rate limits

60 requests per minute for each connection.
20 requests per minute from one IP address, counted before sign-in is checked.
Over a limit, the connector answers HTTP 429 with JSON-RPC error -32001 and a Retry-After header giving the seconds to wait.

Common problems

Sign-in says AI tool connections are not enabled for your organization: The connector is not turned on for that organization. Contact your account manager, or email support below.
The assistant lists no OuterSignal tools: The organization is on a free plan, or no permission was granted at consent. Check the plan, then remove the connector and connect again, granting at least one permission.
Some persona tools are missing: Those tools appear once persona tagging is active. See Who can use it for the list.
A customer base tool refuses to answer: It needs at least 30 enriched customers in scope. Widen the date range or ask about the whole customer base.
Answers come from the wrong brand: Ask the assistant to run list_organizations, then name the brand you want. Without one, tools answer for the default brand chosen at consent.
The assistant asks you to sign in again: The connection was revoked, or it went unused until its refresh token expired after 30 days. Sign in and approve the consent screen again.
A tool call fails with error -32001 or HTTP 429: A rate limit was reached. Wait the number of seconds in Retry-After and try again.

Privacy

What the connector collects, how long it is kept, and who receives it are covered in the AI Assistant Connectors section of the Privacy Policy.

Support

Email engineering@outersignal.com for product questions and to report a security issue.