--- title: "Vitally MCP server for AI agents - actionlake" description: "Give Claude 103 Vitally actions through one MCP server: meetings, custom object instances. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/vitally updated: 2026-10-23 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 103 actions in one signed file - 57 read look, never change - 31 write create and update - 15 wait for a yes destructive, 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_key` Vitally REST API secret token - `host` Where 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 call check { 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 2026[docs.vitally.io](https://docs.vitally.io/en/collections/10410457-rest-api) **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. - **57** read look, never change - **31** write create and update - **15** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `vitally.users.list` List Users | List Users. | read | `crm.contact.list` 177 connectors | | `vitally.accounts.list` List Accounts | List Accounts. | read | `crm.company.list` 162 connectors | | `vitally.tasks.list` List Tasks | List Tasks. | read | `work.task.list` 122 connectors | | `vitally.admins.list` List Admins | List Admins. | read | `identity.user.list` 474 connectors | | `vitally.projects.list` List Projects | List Projects. | read | `work.project.list` 109 connectors | | `vitally.users.create` Create a User | Create a User. | write | `crm.contact.create` 161 connectors | | `vitally.accounts.create` Create an Account | Create an Account. | write | `crm.company.create` 142 connectors | | `vitally.notes.list` List Notes | List Notes. | read | `crm.company_note.list` 14 connectors | | `vitally.tasks.create` Create a Task | Create a Task. | write | `work.task.create` 127 connectors | | `vitally.notes.create` Create a Note | Create a Note. | write | `crm.company_note.create` 18 connectors | | `vitally.users.delete` Delete a User | Delete a User. | destructive | `crm.contact.delete` 147 connectors | | `vitally.projects.create` Create a Project from a template | Create a Project from a template. | write | `work.project.create` 102 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. Read read Which Vitally tasks are overdue, and who owns each one? calls `vitally.tasks.list` 2. Write write Create a User in Vitally. Show me exactly what you will send before you save it. calls `vitally.users.create` 3. Across systems read Which Vitally companies have invoices in ConnectWise PSA, and how many each? calls `vitally.accounts.list` `connectwise_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](https://actionlake.com/connectors/connectwise-psa) - Which Vitally companies have invoices in NetSuite, and how many each? `vitally.accounts.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite) Also mapped by other connectors `identity.user` **517** `crm.company` **227** `crm.contact` **192** `work.project` **116** `work.task` **105** `crm.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 User `vitally.users.delete` - Delete an Account `vitally.accounts.delete` - Delete a Task `vitally.tasks.delete` - Delete a Project `vitally.projects.delete` - Delete a Note `vitally.notes.delete` - Delete a Conversation `vitally.conversations.delete` - Delete a Message `vitally.messages.delete` - Delete a Meeting `vitally.meetings.delete` - Delete an NPS Response `vitally.nps_responses.delete` - Delete an Organization `vitally.organizations.delete` - Unlink a Task from a Project `vitally.projects.unlink_task` - Remove a participant from a Meeting `vitally.meetings.remove_participant` - Delete a Custom Object Instance `vitally.custom_object_instances.delete` - Unlink an Account from a Custom Object Instance `vitally.custom_object_instances.unlink_account` - Unlink an Organization from a Custom Object Instance `vitally.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. do vitally.users.delete confirm_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: "lead@example.com" }, { match: "vitally.accounts.delete", approver: "lead@example.com" }, { match: "vitally.tasks.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 103 Vitally actions - 103 actions page each page of a long list is one call - 57 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Vitally action. 103 actions by area: the id your agent calls, what it does, and its effect. **Meetings 13** - `vitally.meetings.add_participant` Add a participant to a Meeting write - `vitally.meetings.create` Create a Meeting write - `vitally.meetings.delete` Delete a Meeting destructive - `vitally.meetings.find` Find a Meeting read - `vitally.meetings.get` Get a Meeting read - `vitally.meetings.get_transcript` Get a Meeting's transcript read - `vitally.meetings.list` List Meetings read - `vitally.meetings.list_for_account` List Meetings for an Account read - `vitally.meetings.list_for_organization` List Meetings for an Organization read - `vitally.meetings.put_transcript` Create or replace a Meeting's transcript write - `vitally.meetings.remove_participant` Remove a participant from a Meeting destructive - `vitally.meetings.update` Update a Meeting write - `vitally.meetings.upsert_transcript` Find a Meeting and create or update its transcript write **Custom object instances 11** - `vitally.custom_object_instances.create` Create a Custom Object Instance write - `vitally.custom_object_instances.delete` Delete a Custom Object Instance destructive - `vitally.custom_object_instances.link_account` Link an Account to a Custom Object Instance write - `vitally.custom_object_instances.link_organization` Link an Organization to a Custom Object Instance write - `vitally.custom_object_instances.list` List Custom Object Instances read - `vitally.custom_object_instances.list_for_account` List Custom Object Instances for an Account read - `vitally.custom_object_instances.list_for_organization` List Custom Object Instances for an Organization read - `vitally.custom_object_instances.search` Search Custom Object Instances read - `vitally.custom_object_instances.unlink_account` Unlink an Account from a Custom Object Instance destructive - `vitally.custom_object_instances.unlink_organization` Unlink an Organization from a Custom Object Instance destructive - `vitally.custom_object_instances.update` Update a Custom Object Instance write **Projects 11** - `vitally.projects.create` Create a Project from a template write - `vitally.projects.delete` Delete a Project destructive - `vitally.projects.get` Get a Project read - `vitally.projects.link_task` Link a Task to a Project write - `vitally.projects.list` List Projects read - `vitally.projects.list_for_account` List Projects for an Account read - `vitally.projects.list_for_organization` List Projects for an Organization read - `vitally.projects.move_from_account` Move an Account's Project write - `vitally.projects.move_from_organization` Move an Organization's Project write - `vitally.projects.unlink_task` Unlink a Task from a Project destructive - `vitally.projects.update` Update a Project write **Users 8** - `vitally.users.create` Create a User write - `vitally.users.delete` Delete a User destructive - `vitally.users.get` Get a User read - `vitally.users.list` List Users read - `vitally.users.list_for_account` List Users for an Account read - `vitally.users.list_for_organization` List Users for an Organization read - `vitally.users.search` Search Users read - `vitally.users.update` Update a User write **Accounts 7** - `vitally.accounts.create` Create an Account write - `vitally.accounts.delete` Delete an Account destructive - `vitally.accounts.get` Get an Account read - `vitally.accounts.get_health_scores` Get an Account's health score breakdown read - `vitally.accounts.list` List Accounts read - `vitally.accounts.list_for_organization` List Accounts for an Organization read - `vitally.accounts.update` Update an Account write **Conversations 7** - `vitally.conversations.create` Create a Conversation write - `vitally.conversations.delete` Delete a Conversation destructive - `vitally.conversations.get` Get a Conversation read - `vitally.conversations.list` List Conversations read - `vitally.conversations.list_for_account` List Conversations for an Account read - `vitally.conversations.list_for_organization` List Conversations for an Organization read - `vitally.conversations.update` Update a Conversation write **Notes 7** - `vitally.notes.create` Create a Note write - `vitally.notes.delete` Delete a Note destructive - `vitally.notes.get` Get a Note read - `vitally.notes.list` List Notes read - `vitally.notes.list_for_account` List Notes for an Account read - `vitally.notes.list_for_organization` List Notes for an Organization read - `vitally.notes.update` Update a Note write **NPS responses 7** - `vitally.nps_responses.create` Create an NPS Response write - `vitally.nps_responses.delete` Delete an NPS Response destructive - `vitally.nps_responses.get` Get an NPS Response read - `vitally.nps_responses.list` List NPS Responses read - `vitally.nps_responses.list_for_account` List NPS Responses for an Account read - `vitally.nps_responses.list_for_organization` List NPS Responses for an Organization read - `vitally.nps_responses.update` Update an NPS Response write **Tasks 7** - `vitally.tasks.create` Create a Task write - `vitally.tasks.delete` Delete a Task destructive - `vitally.tasks.get` Get a Task read - `vitally.tasks.list` List Tasks read - `vitally.tasks.list_for_account` List Tasks for an Account read - `vitally.tasks.list_for_organization` List Tasks for an Organization read - `vitally.tasks.update` Update a Task write **Organizations 5** - `vitally.organizations.create` Create an Organization write - `vitally.organizations.delete` Delete an Organization destructive - `vitally.organizations.get` Get an Organization read - `vitally.organizations.list` List Organizations read - `vitally.organizations.update` Update an Organization write **Custom objects 4** - `vitally.custom_objects.create` Create a Custom Object write - `vitally.custom_objects.get` Get a Custom Object read - `vitally.custom_objects.list` List Custom Objects read - `vitally.custom_objects.update` Update a Custom Object write **Admins 3** - `vitally.admins.get` Get an Admin read - `vitally.admins.list` List Admins read - `vitally.admins.search` Search Admins by email read **Messages 3** - `vitally.messages.create` Create a Message in a Conversation write - `vitally.messages.delete` Delete a Message destructive - `vitally.messages.get` Get a Message read **Meeting transcripts 2** - `vitally.meeting_transcripts.get` Get a Meeting Transcript read - `vitally.meeting_transcripts.list` List Meeting Transcripts read **Custom traits 1** - `vitally.custom_traits.list` List custom traits by model read **Note categories 1** - `vitally.note_categories.list` List Note Categories read **Project categories 1** - `vitally.project_categories.list` List Project Categories read **Project templates 1** - `vitally.project_templates.list` List Project Templates read **Survey questions 1** - `vitally.survey_questions.get` Get a Survey Question read **Survey responses 1** - `vitally.survey_responses.get` Get a Survey Response read **Surveys 1** - `vitally.surveys.list_responses` List responses to a Custom Survey read **Task categories 1** - `vitally.task_categories.list` List Task Categories read 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 - [Adobe Workfront 18](https://actionlake.com/connectors/adobe-workfront) - [Manatal 17](https://actionlake.com/connectors/manatal) - [Clockify 16](https://actionlake.com/connectors/clockify) - [Toggl Track 16](https://actionlake.com/connectors/toggl-track) - [Fieldwire 12](https://actionlake.com/connectors/fieldwire) - [Microsoft Planner 10](https://actionlake.com/connectors/microsoft-planner) Joins with, on shared entities - [ScalePad 6](https://actionlake.com/connectors/scalepad) - [Odoo 5](https://actionlake.com/connectors/odoo) - [ERPNext (Frappe) 5](https://actionlake.com/connectors/erpnext-frappe) - [Productive.io 5](https://actionlake.com/connectors/productive-io) - [ServiceTitan 5](https://actionlake.com/connectors/servicetitan) - [Insightly CRM 5](https://actionlake.com/connectors/insightly-crm) Browse - [All Work & projects connectors](https://actionlake.com/connectors/category/work-and-projects) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/vitally More: https://actionlake.com/llms.txt