# Skalin MCP

> Skalin MCP Server connects your AI client directly to Skalin's customer success data. Use it to list accounts, check real-time health scores, retrieve usage metrics, and track every interaction or alert without switching apps. It gives your agent a single source of truth for account management.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** customer-success, churn-prevention, health-scores, account-management, customer-insights, task-tracking

## Description

**Skalin MCP Server** connects your agent straight into Skalin's customer success data layer. You don't gotta switch apps anymore; you can run complex account management operations—checking health scores or logging tasks—all through a natural conversation with your AI client.

This server gives your agent direct access to the system of record for accounts, contacts, and usage. It exposes twelve tools that let your agent take action right on the platform. You'll start by using `list_cs_accounts` to grab a comprehensive rundown of every customer success account in your system. If you need details about who runs those accounts or who handles the day-to-day work, run `list_success_managers` to see all the designated Customer Success Managers.

When it comes to monitoring risk, you've got tools for immediate visibility: use `get_account_health` to fetch a client’s current health score and status. You can also check system-wide issues by running `list_cs_alerts`, which shows active, critical alerts demanding attention across your entire client base. For deeper dives into usage, you'll pull detailed metrics (like logins or specific features used) with `get_account_metrics`. The server even lets you verify the backend connection itself using `get_api_status` to confirm Skalin is running smoothly.

Managing an account means more than just checking a score. You can use `list_account_contacts` against any given account ID to pull every person attached to that client record. If your agent needs to build out the full history, they'll run `list_account_interactions`, which gives them the chronological log of every recorded communication for that client. To keep the team organized, you can check outstanding work using `list_cs_tasks` to see all pending customer success tasks assigned across accounts. If a task needs adjusting—maybe changing the owner or updating the due date—your agent uses `update_cs_task`; and if a brand new client pops up in the pipeline, they'll add it into the system with `create_cs_account`.

Recording activity is simple. After you talk to a client, your agent runs `log_interaction`, creating a brand-new record of that call or email against the correct account ID. Completing the circle means revisiting all these data points: by grouping calls to check basic visibility (`list_cs_accounts`), pull contacts (`list_account_contacts`), track history (`list_account_interactions`), assess risk (`get_account_health`), and then log a follow-up meeting using `log_interaction`, your agent maintains a single, consistent source of truth without ever leaving the chat window. This lets you manage everything from account setup to task closure in one conversational flow.

## Tools

### create_cs_account
Adds a brand new customer success account record into Skalin.

### log_interaction
Creates a new record of an interaction (like a call or email) against a specific account ID.

### get_api_status
Checks the connectivity and operational status of the Skalin API itself.

### get_account_health
Retrieves the current health score and status for a specified client account.

### get_account_metrics
Fetches detailed usage metrics (e.g., logins, features used) for an account.

### list_cs_accounts
Returns a list of all managed customer success accounts in your system.

### list_cs_alerts
Lists active, critical alerts that require immediate attention across the client base.

### list_account_contacts
Lists all people (contacts) associated with a given account ID.

### list_success_managers
Lists all user accounts designated as Customer Success Managers within Skalin.

### list_account_interactions
Retrieves the chronological history of all recorded interactions for an account.

### list_cs_tasks
Shows a list of all outstanding or pending customer success tasks assigned to the team.

### update_cs_task
Modifies the status, owner, or details of an existing customer success task.

## Prompt Examples

**Prompt:** 
```
List all accounts with a health score below 50 in Skalin.
```

**Response:** 
```
I've retrieved the at-risk accounts. You have 3 accounts with health scores below 50: 'Acme Corp' (35), 'Globex Inc' (42), and 'Initech' (48). Would you like to see recent alerts for any of them?
```

**Prompt:** 
```
Show me the customer health scores for all enterprise accounts with churn risk indicators.
```

**Response:** 
```
34 enterprise accounts analyzed. Healthy (22, 65%): Avg health score 87, strong product adoption, regular engagement. At-risk (8, 24%): Avg score 52. Top concerns: Meridian Corp (score 38, login drop 67%), TechVentures (score 45, support tickets +200%), DataFlow (score 51, feature adoption 12%). Churning (4, 12%): 2 confirmed non-renewal, 2 in negotiation. Net Revenue Retention: 108%. Key risk signals: declining logins (5 accounts), reduced feature usage (3), negative NPS (2). CSM action items: 12 tasks overdue.
```

**Prompt:** 
```
Generate a quarterly business review report for the Meridian Corp account.
```

**Response:** 
```
QBR Report: Meridian Corp (Q1 2025). Health score: 38/100 (Critical). Contract value: $180,000/year (renewal: August 15). Usage: 45 active users of 100 licenses (45% adoption, down from 67%). Feature adoption: 4 of 12 modules active. Support: 23 tickets (vs 8 last quarter, +188%). NPS: 6 (Passive, was 8). Key wins: API integration completed, custom dashboard deployed. Concerns: Champions left the company (2), executive sponsor unresponsive. Recommended actions: Executive alignment meeting, adoption workshop, contract review.
```

## Capabilities

### Check Account Status
List all managed accounts or retrieve detailed metrics and health scores for a specific client.

### Manage Customer Records
List contacts, track historical interactions, and assign/update success tasks within an account.

### Monitor Alerts & Health
Retrieve active system alerts or check the real-time health score to gauge a client's risk level.

### Log Account Activity
Record new interactions (emails, meetings) or update task status directly from your AI agent chat.

## Use Cases

### The QBR Prep Problem
A CSM needs to prep for a Quarterly Business Review (QBR) with Acme Corp. Instead of pulling data from three different tabs—metrics, contacts, and alerts—they simply ask their agent: 'Give me the status on Acme Corp.' The agent runs `get_account_health`, pulls recent activity using `list_account_interactions`, and summarizes all key risks in one response.

### The New Client Onboarding
An Account Executive just finished the kickoff call. They don't want to open Skalin, find the account, then manually type up a note. They tell their agent: 'Log this meeting with John Doe for Acme Corp.' The agent uses `log_interaction` and instantly records the activity against the correct client profile.

### The Overdue Task Check
An Ops Analyst needs to see if any accounts are slipping through the cracks. They ask: 'Which accounts have overdue tasks?' The agent runs `list_cs_tasks` and flags all items marked as past due, letting the analyst know exactly where to focus their time.

### The Quick Status Check
A manager needs to quickly check if the API is okay before running a major report. They ask: 'What's the Skalin API status?' The agent calls `get_api_status` and provides an immediate confirmation, preventing wasted time on failed reports.

## Benefits

- Stop bouncing between dashboards. You check client data—like running `get_account_health` or calling `list_cs_alerts`—and get all the critical details instantly from your AI agent.
- Build a full audit trail without leaving the chat window. Use `log_interaction` to record meeting notes and calls immediately, keeping account history current for every team member.
- Identify risk proactively. Instead of waiting for complaints, you can ask the server to run `get_account_metrics` or check the score via `get_account_health` before a renewal date.
- Coordinate assignments easily. Run `list_success_managers` and view task status using `list_cs_tasks`. You'll know exactly who owns what, eliminating internal finger-pointing.
- Keep data clean and accurate. When a client changes their core contact list, you just run `list_account_contacts` to verify the latest details, every time.

## How It Works

The bottom line is: Your AI client calls specific functions, which pulls live data from Skalin, giving you immediate, actionable insights into customer accounts.

1. Subscribe to the server and provide your Skalin API Key in the integration settings.
2. Your AI client sends a request (e.g., 'Show me accounts with low health scores') to the MCP Server's exposed toolset.
3. The server runs the necessary tools (`get_account_health`, `list_cs_accounts`) and returns structured data that your agent uses to formulate an answer.

## Frequently Asked Questions

**How do I check if my account has critical issues using list_cs_alerts?**
You simply ask your agent to 'list active alerts'. The server calls `list_cs_alerts` and returns a clean summary of any system warnings or changes that need attention.

**Can I get usage data for specific clients using get_account_metrics?**
Yes. You ask the agent to 'show me the usage metrics for Acme Corp'. The server runs `get_account_metrics` and provides detailed stats like logins or feature adoption rates.

**What's the difference between list_account_interactions and list_cs_alerts?**
They track different things. `list_account_interactions` shows human-generated history (meetings, emails). `list_cs_alerts` tracks system-level issues or critical account status changes.

**How do I update a task using the update_cs_task tool?**
You tell your agent, 'Mark the Q3 review task for Acme Corp as complete.' The server uses `update_cs_task` to change the status in Skalin's system.

**How do I use the `create_cs_account` tool to add a new account?**
You pass the necessary details like the account name and owner ID. The agent sends this data directly to Skalin, creating the record in your system. This handles the entire initial setup process for you.

**What information do I provide when using `log_interaction`?**
The tool requires details about the interaction, such as whether it was a meeting or an email. You must also include key notes and the associated account ID to correctly log the activity.

**How can I get all people associated with an account using `list_account_contacts`?**
Simply call `list_account_contacts` for a given account. The output delivers a list of people linked to that client, including their roles and contact information.

**What does the `get_api_status` tool check regarding connectivity?**
This tool confirms your server's connection status with Skalin. It reports on API key validity and tells you when the last successful sync occurred, letting you troubleshoot potential outages.

**How do I find my Skalin API Key?**
Log in to your Skalin account, navigate to **Settings** > **Integrations**, and you will find your unique secret API Bearer Token there.