The Vitally MCP (Model Context Protocol) server connects an MCP-compatible AI client to your Vitally workspace. Once connected, you can ask the AI questions about your customer data in plain language and have it query Vitally on your behalf. The integration also supports "write" actions, so the AI can create records such as Tasks, Notes, and Custom Objects directly in Vitally.

MCP is an open standard for connecting AI clients to external tools and data. Any client that supports MCP can connect to Vitally, including Claude, ChatGPT, and Cursor. The AI runs inside the client you already use; Vitally exposes a set of tools that the client can call.

The MCP server is currently in Beta. The available tools will continue to grow, and some behavior may change during the Beta period. If something does not work as expected, contact your CSM and share the chat transcript.

Vitally Copilot runs natively inside Vitally and has pre-built knowledge of your workspace configuration. The MCP server is the reverse: it brings Vitally data into an outside AI tool you already use for other work. This gives you more flexibility, because you are not limited to the Vitally interface, but it also means the AI does more work to interpret your workspace's specific terminology. A few minutes of setup, described below, closes most of that gap.

Setup is a one-time process in your AI client. The exact screen varies by client, but the connection details are the same everywhere.

You'll need permissions to add a Custom Connector. If you are on a Team or Enterprise plan with your AI client, your Workspace Owner will need to enable the Connector at which point individual users within the organization will be able to connect and enable the Connector for themselves. If you have an individual paid plan, you can do this yourself.

Add the Vitally MCP server to your AI client using this URL:

https://mcp.vitally.io/mcp/v0

Some clients provide a simple connector field where you paste the URL directly (for example, Claude.ai under Settings, then Connectors). Other clients use a configuration file (for example, Claude Desktop or Cursor). The URL is the same in both cases; consult your client's own documentation for where the connector setting or configuration file lives.

After you add the server, your AI client opens a browser window and prompts you to sign in to Vitally and authorize access. This is a standard OAuth consent flow, the same kind used when connecting any other app to your accounts. The consent screen shows the permission scopes the client is requesting. Approve them, and the connection is live.

There is no API key to generate and no credentials to copy and paste. Your client handles registration and authorization automatically the first time you connect.

Access is tied to your Vitally user account. The MCP server respects your existing permissions in Vitally, including Access Groups, so the AI can only see and do what you can do. Any record the AI creates is attributed to you, the same as if you had created it in Vitally directly.

Ask your AI client a simple question, such as "What accounts do I have in Vitally?" If it returns real data from your workspace, the connection is working.

Once connected and configured, you can ask the AI to look up, analyze, and (in some cases) create Vitally records — all in plain language. Here is the complete list of currently supported tools:

Read-Only Tools

Write Tools

The AI can search for and retrieve details about accounts, organizations, and users. You can search by name or by external ID, and you can scope a search to a specific account or organization. Examples:

Tool names adapt to your workspace's terminology. If your workspace calls accounts something else, the AI's account-lookup tool is named to match, so you can refer to your records using the same words you use inside Vitally.

The AI can summarize an account's recent activity and history, including notes, meetings, and product feedback. Examples:

Your workspace's Custom Objects, such as Risks, Product Requests, or Commitments, are accessible by name. You do not need to know internal IDs. The AI reads each Custom Object's description from your Vitally configuration to understand how to use it. Examples:

The AI can create records directly in Vitally, including Tasks, Notes, and Custom Object records. Creating a record requires an Account or Organization to attach it to. Examples:

Write actions run directly, without a separate confirmation step built into the tool. Review what the AI is about to create before you ask it to proceed, the same way you would for any other AI-assisted action with real consequences. This matters most for customer-facing records.

If a question about a custom field is answered oddly, the cause is usually that the field's description in Vitally does not give the AI enough context to interpret it. Add or improve descriptions on your Traits and Custom Objects in Vitally so the AI has more context about how each one is meant to be used.

Multi-step requests work, but you can improve results by breaking them down. A request like, "Find accounts at risk, then check their open tasks, then draft a follow-up plan" asks the AI to chain several actions together on its own. This generally works well, but if a complicated request returns an incomplete or confusing answer, split it into smaller, sequential questions.

You can also prompt the AI to iterate. Ask it directly why something did not work, or ask it to try a different approach, with prompts such as, "Do a deeper analysis on this," "What else can you tell me about X," "Did you miss anything important," or "Try again and take a closer look at the conversations."

When you connect the Vitally MCP server, you use your own AI client and its subscription. Any tokens consumed by a conversation are billed through your client (for example, your Claude, ChatGPT, or Cursor plan), not through Vitally. This is the same for any MCP server or connector you attach to your AI client, whether it is Vitally, Notion, or another tool. Connecting to Vitally through the MCP does not change how your AI client bills you.

The MCP server is in Beta, and it is actively being improved based on how you use it. If something does not work the way you expect, or you hit a wall doing something that feels like it should be possible, tell your CSM and share the chat transcript. That feedback goes directly into what gets built next.