Skip to content
actionlake
Start free

Connectors · Work & projects

Vitally MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Vitally and the rest of your systems. It gives your agent 103 Vitally actions (57 reads, 31 writes and 15 that wait for a confirmation) and holds the Vitally credential itself, so the agent never does. It paces Vitally's limits and records every call.

Connect Vitally freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "vitally.users.list",  intent: "check which Vitally account is connected"}# List Users · read · 1 upstream call
  • 103actionsin one signed file
  • 57readlook, never change
  • 31writecreate and update
  • 15wait for a yesdestructive, confirmed first

Set up

Connect Vitally in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Vitally.

    Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyVitally REST API secret token
    • hostWhere your Vitally lives: your host
    account { op: "connections.requirements", service: "vitally" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "vitally.users.list" }# list users · read · 1 upstream callcheck { action: "vitally.users.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Vitally at a glance

Sign-in
Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Setup fields
host
Limits we pace to
1,000 calls a minute, per connection
API covered
Vitally REST API (resources), at your Vitally instance's API base URL, which you enter when connecting
Built from
Vitally's documentation, read 23 October 2026docs.vitally.io
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
57 of 57 reads, for up to 5 minutes; a write clears what it affects
Shared entities
6, so ask can line Vitally up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Vitally.

103 actions in 22 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 57readlook, never change
  • 31writecreate and update
  • 15destructivewait for a confirmation

  1. Meetings

    13

    6 read · 5 write · 2 destructive

    Create or replace a Meeting's transcript · Add a participant to a Meeting · Create a Meeting · Find a Meeting

  2. Custom object instances

    11

    4 read · 4 write · 3 destructive

    Create a Custom Object Instance · Link an Account to a Custom Object Instance · Link an Organization to a Custom Object Instance · List Custom Object Instances

  3. Projects

    11

    4 read · 5 write · 2 destructive

    List Projects · Create a Project from a template · Get a Project · Update a Project

  4. Users

    8

    5 read · 2 write · 1 destructive

    List Users · Create a User · Get a User · Update a User

  5. Accounts

    7

    4 read · 2 write · 1 destructive

    List Accounts · Create an Account · Get an Account · Update an Account

  6. Conversations

    7

    4 read · 2 write · 1 destructive

    List Conversations · Create a Conversation · Get a Conversation · Update a Conversation

  7. Notes

    7

    4 read · 2 write · 1 destructive

    List Notes · Create a Note · Update a Note · Delete a Note

  8. NPS responses

    7

    4 read · 2 write · 1 destructive

    Create an NPS Response · List NPS Responses · List NPS Responses for an Account · List NPS Responses for an Organization

14 more areas · 32 actions
  • Tasks 7
  • Organizations 5
  • Custom objects 4
  • Admins 3
  • Messages 3
  • Meeting transcripts 2
  • Custom traits 1
  • Note categories 1
  • Project categories 1
  • Project templates 1
  • Survey questions 1
  • Survey responses 1
  • Surveys 1
  • Task categories 1

Top actions

The Vitally API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 45 of Vitally's 45 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
vitally.users.listList UsersList Users.readcrm.contact.list177 connectors
vitally.accounts.listList AccountsList Accounts.readcrm.company.list162 connectors
vitally.tasks.listList TasksList Tasks.readwork.task.list122 connectors
vitally.admins.listList AdminsList Admins.readidentity.user.list474 connectors
vitally.projects.listList ProjectsList Projects.readwork.project.list109 connectors
vitally.users.createCreate a UserCreate a User.writecrm.contact.create161 connectors
vitally.accounts.createCreate an AccountCreate an Account.writecrm.company.create142 connectors
vitally.notes.listList NotesList Notes.readcrm.company_note.list14 connectors
vitally.tasks.createCreate a TaskCreate a Task.writework.task.create127 connectors
vitally.notes.createCreate a NoteCreate a Note.writecrm.company_note.create18 connectors
vitally.users.deleteDelete a UserDelete a User.destructivecrm.contact.delete147 connectors
vitally.projects.createCreate a Project from a templateCreate a Project from a template.writework.project.create102 connectors

Try it

Prompts to paste into Claude.

Each one names the Vitally actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Vitally tasks are overdue, and who owns each one?

    callsvitally.tasks.list

  2. Writewrite

    Create a User in Vitally. Show me exactly what you will send before you save it.

    callsvitally.users.create

  3. Across systemsread

    Which Vitally companies have invoices in ConnectWise PSA, and how many each?

    callsvitally.accounts.listconnectwise_manage.invoices.list

Across your systems

Vitally, joined to the rest of your business.

One ask fetches from Vitally and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which Vitally companies have invoices in ConnectWise PSA, and how many each?

    vitally.accounts.list + connectwise_manage.invoices.list, on crm.company · ConnectWise PSA

  • Which Vitally companies have invoices in NetSuite, and how many each?

    vitally.accounts.list + netsuite.views.invoices, on crm.company · NetSuite

Also mapped by other connectorsidentity.user 517crm.company 227crm.contact 192work.project 116work.task 105crm.company_note 3
ask
ask {  intent: "which Vitally companies have invoices in ConnectWise PSA, and how many each",  steps: [    { action: "vitally.accounts.list", as: "co", input: {}, limit: 100, max_pages: 5 },    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "co",        right: "inv",        on: "crm.company",        group_by: "co.name",        select: ["co.name", "count(inv.id) as invoices"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Vitally

Destructive actions wait for a yes.

15 Vitally actions are destructive. These are all of them:

  • Delete a Uservitally.users.delete
  • Delete an Accountvitally.accounts.delete
  • Delete a Taskvitally.tasks.delete
  • Delete a Projectvitally.projects.delete
  • Delete a Notevitally.notes.delete
  • Delete a Conversationvitally.conversations.delete
  • Delete a Messagevitally.messages.delete
  • Delete a Meetingvitally.meetings.delete
  • Delete an NPS Responsevitally.nps_responses.delete
  • Delete an Organizationvitally.organizations.delete
  • Unlink a Task from a Projectvitally.projects.unlink_task
  • Remove a participant from a Meetingvitally.meetings.remove_participant
  • Delete a Custom Object Instancevitally.custom_object_instances.delete
  • Unlink an Account from a Custom Object Instancevitally.custom_object_instances.unlink_account
  • Unlink an Organization from a Custom Object Instancevitally.custom_object_instances.unlink_organization

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dovitally.users.deleteconfirm_policy: human

Delete a User?

intent: the user asked me to delete a User

run suspended · waiting for a named person · key vitally-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "vitally-agent",  allowed_actions: ["vitally.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "vitally.users.delete", approver: "[email protected]" },    { match: "vitally.accounts.delete", approver: "[email protected]" },    { match: "vitally.tasks.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Vitally only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Vitally costs on actionlake.

Every Vitally action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Vitally refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 103 Vitally actions
  • 103actions pageeach page of a long list is one call
  • 57reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Vitally action.

103 actions by area: the id your agent calls, what it does, and its effect.

Meetings13
  • vitally.meetings.add_participantAdd a participant to a Meetingwrite
  • vitally.meetings.createCreate a Meetingwrite
  • vitally.meetings.deleteDelete a Meetingdestructive
  • vitally.meetings.findFind a Meetingread
  • vitally.meetings.getGet a Meetingread
  • vitally.meetings.get_transcriptGet a Meeting's transcriptread
  • vitally.meetings.listList Meetingsread
  • vitally.meetings.list_for_accountList Meetings for an Accountread
  • vitally.meetings.list_for_organizationList Meetings for an Organizationread
  • vitally.meetings.put_transcriptCreate or replace a Meeting's transcriptwrite
  • vitally.meetings.remove_participantRemove a participant from a Meetingdestructive
  • vitally.meetings.updateUpdate a Meetingwrite
  • vitally.meetings.upsert_transcriptFind a Meeting and create or update its transcriptwrite
Custom object instances11
  • vitally.custom_object_instances.createCreate a Custom Object Instancewrite
  • vitally.custom_object_instances.deleteDelete a Custom Object Instancedestructive
  • vitally.custom_object_instances.link_accountLink an Account to a Custom Object Instancewrite
  • vitally.custom_object_instances.link_organizationLink an Organization to a Custom Object Instancewrite
  • vitally.custom_object_instances.listList Custom Object Instancesread
  • vitally.custom_object_instances.list_for_accountList Custom Object Instances for an Accountread
  • vitally.custom_object_instances.list_for_organizationList Custom Object Instances for an Organizationread
  • vitally.custom_object_instances.searchSearch Custom Object Instancesread
  • vitally.custom_object_instances.unlink_accountUnlink an Account from a Custom Object Instancedestructive
  • vitally.custom_object_instances.unlink_organizationUnlink an Organization from a Custom Object Instancedestructive
  • vitally.custom_object_instances.updateUpdate a Custom Object Instancewrite
Projects11
  • vitally.projects.createCreate a Project from a templatewrite
  • vitally.projects.deleteDelete a Projectdestructive
  • vitally.projects.getGet a Projectread
  • vitally.projects.link_taskLink a Task to a Projectwrite
  • vitally.projects.listList Projectsread
  • vitally.projects.list_for_accountList Projects for an Accountread
  • vitally.projects.list_for_organizationList Projects for an Organizationread
  • vitally.projects.move_from_accountMove an Account's Projectwrite
  • vitally.projects.move_from_organizationMove an Organization's Projectwrite
  • vitally.projects.unlink_taskUnlink a Task from a Projectdestructive
  • vitally.projects.updateUpdate a Projectwrite
Users8
  • vitally.users.createCreate a Userwrite
  • vitally.users.deleteDelete a Userdestructive
  • vitally.users.getGet a Userread
  • vitally.users.listList Usersread
  • vitally.users.list_for_accountList Users for an Accountread
  • vitally.users.list_for_organizationList Users for an Organizationread
  • vitally.users.searchSearch Usersread
  • vitally.users.updateUpdate a Userwrite
Accounts7
  • vitally.accounts.createCreate an Accountwrite
  • vitally.accounts.deleteDelete an Accountdestructive
  • vitally.accounts.getGet an Accountread
  • vitally.accounts.get_health_scoresGet an Account's health score breakdownread
  • vitally.accounts.listList Accountsread
  • vitally.accounts.list_for_organizationList Accounts for an Organizationread
  • vitally.accounts.updateUpdate an Accountwrite
Conversations7
  • vitally.conversations.createCreate a Conversationwrite
  • vitally.conversations.deleteDelete a Conversationdestructive
  • vitally.conversations.getGet a Conversationread
  • vitally.conversations.listList Conversationsread
  • vitally.conversations.list_for_accountList Conversations for an Accountread
  • vitally.conversations.list_for_organizationList Conversations for an Organizationread
  • vitally.conversations.updateUpdate a Conversationwrite
Notes7
  • vitally.notes.createCreate a Notewrite
  • vitally.notes.deleteDelete a Notedestructive
  • vitally.notes.getGet a Noteread
  • vitally.notes.listList Notesread
  • vitally.notes.list_for_accountList Notes for an Accountread
  • vitally.notes.list_for_organizationList Notes for an Organizationread
  • vitally.notes.updateUpdate a Notewrite
NPS responses7
  • vitally.nps_responses.createCreate an NPS Responsewrite
  • vitally.nps_responses.deleteDelete an NPS Responsedestructive
  • vitally.nps_responses.getGet an NPS Responseread
  • vitally.nps_responses.listList NPS Responsesread
  • vitally.nps_responses.list_for_accountList NPS Responses for an Accountread
  • vitally.nps_responses.list_for_organizationList NPS Responses for an Organizationread
  • vitally.nps_responses.updateUpdate an NPS Responsewrite
Tasks7
  • vitally.tasks.createCreate a Taskwrite
  • vitally.tasks.deleteDelete a Taskdestructive
  • vitally.tasks.getGet a Taskread
  • vitally.tasks.listList Tasksread
  • vitally.tasks.list_for_accountList Tasks for an Accountread
  • vitally.tasks.list_for_organizationList Tasks for an Organizationread
  • vitally.tasks.updateUpdate a Taskwrite
Organizations5
  • vitally.organizations.createCreate an Organizationwrite
  • vitally.organizations.deleteDelete an Organizationdestructive
  • vitally.organizations.getGet an Organizationread
  • vitally.organizations.listList Organizationsread
  • vitally.organizations.updateUpdate an Organizationwrite
Custom objects4
  • vitally.custom_objects.createCreate a Custom Objectwrite
  • vitally.custom_objects.getGet a Custom Objectread
  • vitally.custom_objects.listList Custom Objectsread
  • vitally.custom_objects.updateUpdate a Custom Objectwrite
Admins3
  • vitally.admins.getGet an Adminread
  • vitally.admins.listList Adminsread
  • vitally.admins.searchSearch Admins by emailread
Messages3
  • vitally.messages.createCreate a Message in a Conversationwrite
  • vitally.messages.deleteDelete a Messagedestructive
  • vitally.messages.getGet a Messageread
Meeting transcripts2
  • vitally.meeting_transcripts.getGet a Meeting Transcriptread
  • vitally.meeting_transcripts.listList Meeting Transcriptsread
Custom traits1
  • vitally.custom_traits.listList custom traits by modelread
Note categories1
  • vitally.note_categories.listList Note Categoriesread
Project categories1
  • vitally.project_categories.listList Project Categoriesread
Project templates1
  • vitally.project_templates.listList Project Templatesread
Survey questions1
  • vitally.survey_questions.getGet a Survey Questionread
Survey responses1
  • vitally.survey_responses.getGet a Survey Responseread
Surveys1
  • vitally.surveys.list_responsesList responses to a Custom Surveyread
Task categories1
  • vitally.task_categories.listList Task Categoriesread

Questions

The Vitally MCP server, answered.

Is there a Vitally MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 103 Vitally actions across meetings, custom object instances, projects and users, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Vitally.

What do I need to connect Vitally?

Vitally REST API secret token. Plus your host. The free call account { op: "connections.requirements", service: "vitally" } lists exactly what to paste.

Can an AI agent delete or change things in Vitally?

Only if its key allows it, and only with an explicit confirmation. 15 Vitally actions are destructive, including delete a User, delete an Account and delete a Task. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Vitally API limit?

actionlake paces every call to the limits in the Vitally service file: 1,000 calls a minute per connection. Repeated reads are answered from cache (57 Vitally actions can be), which never reaches Vitally.

What does a Vitally action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (103 Vitally actions page). Cache hits, searches, dry runs and calls Vitally refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Vitally API does it cover?

The Vitally REST API (resources) at your Vitally instance's API base URL, which you enter when connecting. It is built from Vitally's documentation as read on 23 October 2026. 103 actions in 22 areas, each one in the signed service file (version 1.0.0).

Can I combine Vitally with my other systems?

Yes. ask joins Vitally to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Vitally maps crm.company, which 227 other connectors also map.

Does actionlake keep my Vitally data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Vitally credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Vitally

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Vitally; the name is the vendor's own. Counts are from the Vitally service file, version 1.0.0.

Give your agent Vitally today.

Connect Vitally freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.