AI for Customer Success: Stripe, Slack and Linear in One Agent

📖 TL;DR

Three official MCP servers: Stripe (mcp.stripe.com), Slack (mcp.slack.com/mcp), Linear (mcp.linear.app/sse)
One agent that sees billing health, conversation history and open tickets simultaneously
Use a restricted Stripe key with read-only scopes — never a full secret key for a shared agent
Start with the Customer Success template — pre-wired, under 3 minutes to set up

Customer success work is inherently cross-tool. Understanding a customer's health means looking at their billing status in Stripe, their support history in Slack, and their open feature requests in Linear — simultaneously. Most CSMs do this by switching tabs and building a mental picture from fragments.

This guide shows you how to connect all three to a single AI agent so you can ask "Give me the full picture on Acme Corp" and get billing health, recent Slack activity and open Linear tickets in one answer.

What You Can Do With This Agent

Customer health snapshot

"Give me the full picture on Acme Corp — subscription, last payment, recent Slack activity, and open Linear tickets."

Churn risk identification

"Which customers had a failed payment this week and also messaged us in Slack about billing?"

Renewal preparation

"List accounts renewing in 30 days, their plan, and any open Linear issues to address before the call."

Ticket creation from Slack

"Find the Slack thread where Acme asked about the export feature and create a Linear ticket tagged as a customer request."

Billing triage

"Which customers have had more than two failed payments this month and also messaged us in Slack about it?"

Weekly CS summary

"Summarise this week: new subscriptions, churns, billing issues, top Slack support topics, and Linear customer requests."

The Three Official MCP Servers

Tool	MCP Server URL	Transport	Token
Stripe	https://mcp.stripe.com/	HTTP	Restricted key (rk_live_ or rk_test_)
Slack	https://mcp.slack.com/mcp	HTTP	Bot token (xoxb-…)
Linear	https://mcp.linear.app/sse	SSE	Personal API key

⚠️ Use a restricted Stripe key, not a full secret key

Create a restricted key in Stripe Dashboard → Developers → API keys → Create restricted key. Grant read access only to Customers, Subscriptions, and Invoices. Restricted keys start with rk_live_ and can be revoked instantly without rotating your full secret key.

Step 1 — Get Your Three Tokens

Stripe restricted API key

In Stripe go to Developers → API keys → Create restricted key
Name it (e.g. "CS Agent MCP") and grant read access to: Customers, Subscriptions, Invoices, Payment intents
Click Create key — it starts with rk_live_ or rk_test_

Slack bot token

Go to api.slack.com/apps → create a new app → OAuth & Permissions → Bot Token Scopes
Add: channels:read, channels:history, groups:history, search:read, users:read
Install to workspace, copy the Bot User OAuth Token (xoxb-…)
Invite the bot to relevant channels: /invite @your-bot-name

⚠️ Two Slack caveats CS teams should know:

groups:history is needed to read private channels (CS teams often have per-customer private channels). For DMs add im:history and mpim:history.
search:read requires a paid Slack plan (Pro, Business+, or Enterprise). On Free workspaces, message-search prompts will fail; channel-by-channel lookups still work.

Linear personal API key

In Linear go to Settings → API → Personal API keys → Create key and copy it

⚠️ Linear key note: Linear personal API keys are not scope-limited — they grant full read and write access to everything that Linear user can see (all teams, all projects, all issues). Treat them like a password. For shared agents, consider creating a dedicated Linear user with restricted team membership rather than using a personal key from an admin account.

Step 2 — Connect in Agent Studio

Fastest path: use the pre-built template

The Customer Success template has Stripe, Slack and Linear pre-wired with the right system prompt. Click it, paste your three tokens (one per server slot), and start chatting.

Use Customer Success Template →

To set up manually in MCP Agent Studio:

Click + Add Server → https://mcp.stripe.com/, select HTTP, paste Stripe restricted key
Add second server → https://mcp.slack.com/mcp, select HTTP, paste Slack bot token
Add third server → https://mcp.linear.app/sse, select SSE, paste Linear API key
Choose a model — Claude Haiku 4.5 handles most routine CS queries at lower cost; use Claude Sonnet 4.6 for complex churn analysis that spans all three tools

The Churn Signal Workflow

The highest-value use for CS teams is early churn detection. A practical weekly routine:

Monday check: "Which customers had a failed payment in the last 7 days and also sent a Slack message to our support channel?" — surfaces the intersection of billing trouble and active frustration.
Renewal prep: "List all accounts renewing in the next 30 days with their Stripe plan, last Slack contact date, and any open Linear bugs." — everything you need for a renewal call in one response.
Escalation triage: "Which customers sent more than 3 Slack messages this week and have a subscription over $500/month?" — catches high-value customers struggling before they file a cancellation.

Which Model to Use

Claude Haiku 4.5 — handles most routine CS queries reliably at lower credit cost. Good for queries your team runs multiple times per day: "pull up Acme's subscription", "what did they ask about this week".
Claude Sonnet 4.6 — worth the extra cost for complex cross-tool analysis like churn risk scoring or renewal preparation that needs to reason across all three data sources accurately.
DeepSeek V4 Pro — strong alternative to Sonnet for structured data queries. Considerably cheaper and accurate on well-defined lookups.

Set up your Customer Success agent in under 3 minutes

Official Stripe · Slack · Linear MCP servers · Any AI model · Free credits on sign-up

Use Customer Success Template → Open Agent Studio

Frequently Asked Questions

Is it safe to connect Stripe to an AI agent? +

Use a restricted API key with read-only permissions scoped to Customers, Subscriptions and Invoices only. Restricted keys are created in Stripe Dashboard under Developers → API keys. They can be revoked instantly without rotating your full secret key.

Can the agent see Stripe card numbers or PCI data? +

No. Stripe's API never returns full card numbers — they are tokenised at the point of capture. The agent sees the same data as the Stripe Dashboard: last 4 digits, card brand, expiry, and billing status.

Can I share this agent with my whole CS team? +

Yes. Save the agent and set visibility to Team. Team members open the saved agent with pre-configured servers and model. Each member supplies their own Slack bot token; the Stripe restricted key and Linear key can be shared if your team policy allows.

What if I use Intercom or Zendesk instead of Slack? +

Replace the Slack server with your support tool's MCP server if one exists. MCP Agent Studio supports up to 4 servers per agent, so you can also add Intercom or Zendesk alongside Stripe and Linear. Check the MCP server registry for community-built connectors for those platforms.