Vitally MCP server
Vitally in any MCP client, through Memtro: Vitally does not publish this server. Memtro's Vitally connector reads Vitally through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Vitally customer success: customer accounts with MRR, health and NPS scores, renewal dates and segments, the notes and tasks the CS team keeps on each account, and end users with their last activity. Can, when asked, add, edit, complete or delete a task, add, edit or delete a note, create or edit an account, user or organization, and start or update a project from a template.
Reads
vitally_list_accountsCustomer accounts in Vitally, most recently updated first: MRR, health score, NPS, user count, next renewal date, churn date, last seen…vitally_list_notesNotes the customer-success team has written in Vitally, newest first: subject, text, note date, author, account, category and tags.vitally_list_tasksTasks in Vitally, newest first: name, description, due date, whether and when completed, assignee and account.vitally_list_usersEnd users of your product as Vitally knows them: name, email, accounts, first known and last seen, last NPS score and feedback, deactivation.vitally_list_categoriesThe note or task categories defined in Vitally, with their ids, for filing a new note or task under one.
Acts, when you ask
These change something in Vitally. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
vitally_create_noteAdd a note to a customer account in Vitally, as the CS team would after a call or meeting.vitally_create_taskAdd a task to a customer account in Vitally (a follow-up for the CS team), optionally with a due date and tags.vitally_update_taskChange a Vitally task: rename it, reassign it, change its description, due date, category or tags (tags given replace the list), or mark it complete.vitally_delete_taskDelete a Vitally task (Vitally archives it; no restore through the API).vitally_update_noteEdit a Vitally note: its text, subject, date, category or tags (tags given replace the list).vitally_delete_noteDelete a Vitally note (Vitally archives it; no restore through the API).vitally_create_accountCreate a customer account in Vitally with your own external id and a name, optionally under an organization.vitally_update_accountRename a Vitally account, move it to another organization, or take it out of its organization.vitally_create_userAdd an end user (a person at a customer) to Vitally under one or more accounts or organizations, with your own external id.vitally_update_userChange a Vitally end user's name or email, or link them to more accounts or organizations (Vitally cannot unlink through the API).vitally_create_organizationCreate an organization (a parent grouping of accounts) in Vitally with your own external id and a name.vitally_create_projectStart a Vitally project for an account or organization from a project template (the API can only create from a template, which may add its own tasks).vitally_update_projectChange a Vitally project's name, status, category, owner or target dates.
Connect it
First connect Vitally on Dashboard → Connections, then add Memtro to your client once. The Vitally tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Vitally connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which accounts renew in the next 60 days with a health score under 6?
- › What did the CS team note about Northwind last month?
- › Which open tasks are overdue for my accounts?
- › Add a note to Brightwave Ltd: QBR held, they want SSO before renewal
- › Start an onboarding project for Globex from our standard template
Questions
- Is this an official Vitally MCP server?
- No. It is Memtro's MCP server with Memtro's Vitally connector behind it: the connector reads Vitally through its API with the credentials you connect on Dashboard → Connections, and Vitally publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Vitally?
- Only when you ask, and only what it has been granted: add a note to a customer account; add a task to a customer account; edit, reassign or complete a Vitally task; delete (archive) a Vitally task; edit a Vitally note; delete (archive) a Vitally note; create a Vitally customer account; rename a Vitally account or move it to another organization; add an end user to a Vitally account or organization; edit a Vitally end user; create a Vitally organization; start a Vitally project from a template; update a Vitally project's status, owner or dates. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.