Viva in your AI assistant

Talk to your Chief Marketing Agent from Claude, ChatGPT or any MCP client. Ask how marketing is going, give it orders, and approve its team's work, from the chat you already use.

Connect your assistant

Every client uses the same URL, https://mcp.goviva.ai/mcp, and the same Viva sign-in. Clients marked Tested have been connected end to end; the others follow their published setup steps and haven't been checked by us yet.

Claude Tested

Works in Claude on the web, desktop and mobile. A connector added in one shows up in all of them.

  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it Viva and paste https://mcp.goviva.ai/mcp. Leave the OAuth client ID and secret empty.
  3. Choose Connect, sign in to Viva, pick the permissions and select Allow.
  4. In a chat, make sure Viva is turned on in the tools menu, then ask "Which Viva account are you connected to?"

ChatGPT Not yet tested

ChatGPT adds remote MCP servers as custom connectors. Depending on your plan this may need developer mode turned on.

  1. Open Settings → Apps & Connectors and create a new connector.
  2. Paste https://mcp.goviva.ai/mcp and choose OAuth as the authentication.
  3. Sign in to Viva and approve the permissions.

Claude Code Not yet tested

Sign in through the browser:

claude mcp add --transport http viva https://mcp.goviva.ai/mcp

Then run /mcp inside Claude Code and choose Authenticate for viva.

Or use an API key, for example on a server with no browser:

claude mcp add --transport http viva https://mcp.goviva.ai/mcp \
  --header "Authorization: Bearer vsk_YOUR_KEY"

Other MCP clients

Any client that supports remote servers over Streamable HTTP can connect. If it supports MCP sign-in (OAuth), give it the URL and it will find everything else from /.well-known/oauth-protected-resource/mcp. If it doesn't, send an API key as an Authorization: Bearer header.

Troubleshooting

It connected to the wrong Viva account

Disconnect it in Viva (Settings → AI assistants), then connect again. On the sign-in screen, check the account name at the top and use Not this account? Switch if it's wrong.

The assistant says it needs another permission

The connection doesn't have that permission. Changing data needs Make changes; approving runs and follow-ups needs Approve things that send email. Claude offers to reconnect: say yes, and tick every box you want on the Viva sign-in screen, because it doesn't remember the ones you ticked before. In other assistants, disconnect and connect again with the box ticked. Nothing is approved until you ask again after reconnecting.

The assistant says it needs confirmation before going ahead

That tool would use credits. Viva tells the assistant the cost and waits. Reply that you agree and it will continue; say no and nothing is spent.

New tools don't show up

Most clients read the tool list when a conversation starts. Start a new chat, or turn the connector off and on again.

"Invalid or revoked API key"

The key was deleted, mistyped, or is missing its vsk_ prefix. Create a new one in Settings → AI assistants → API keys.

Sign-in opens but never finishes

Allow pop-ups for the assistant's site and for business.goviva.ai, then try again. If you denied the request by mistake, start the connection again from the assistant.