search_toolsLABSCO SUMMARY
Customer context, before the call.
The five minutes before a customer conversation — who they are, how healthy the account is, what was said last, what is still open — become a couple of calls, and whatever you learn goes back as a note.
What it is
A reader for Vitally customer data, with one write. Accounts are searched by name or external ID and users by email; an account's health score, conversations and tasks come back separately, and notes can be created against an account.
What you get
- Accounts searched by several criteria, or found by partial name
- Users searched by email or external ID
- An account's health score read
- The conversations on an account, and the tasks still open against it
- A note created against an account
- The cached account list refreshed, and the available tools searched by keyword
Requirements
Node to build it, and your Vitally subdomain, API key and data centre — US or EU — set in the environment. Without a key it starts in demo mode against mock data, which is enough to see the shape of the answers.
Setup effort
Build from source — git clone https://github.com/johnjjung/vitally-mcp.git
USE CASES
01
Getting up to speed before a customer call
Find the account by the name you actually know it as, then read the health score and the recent conversations in the same pass.
02
Checking what is outstanding for an account
Open tasks and the conversation history together show whether something was promised and never done.
03
Recording what was agreed
The note lands on the account while the call is fresh, rather than after a context switch into another tab.
04
Finding which account a person belongs to
An email address is often all you have from an inbound message; the user lookup turns it into the account behind it.
05
Working from a fresh list after a sync
The account list is cached; refresh it when something was just created, before deciding it does not exist.
9 tools
Listed in project docs. Your client may show a different list.
search_accountsfind_account_by_namerefresh_accountsget_account_healthsearch_usersget_account_conversationsget_account_taskscreate_account_noteBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- VITALLY_API_KEY in your environment
- VITALLY_API_SUBDOMAIN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/johnjjung/vitally-mcp.git
cd vitally-mcp/vitally
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"vitally-api": {
"command": "node",
"args": [
"--experimental-modules",
"--experimental-specifier-resolution=node",
"<YOUR_CLONE>/vitally/build/index.js"
],
"env": {
"VITALLY_API_SUBDOMAIN": "<YOUR_VITALLY_API_SUBDOMAIN>",
"VITALLY_API_KEY": "<YOUR_VITALLY_API_KEY>",
"VITALLY_DATA_CENTER": "US"
}
}
}
}
