FAQ

General

What is Voyage MCP?

Voyage MCP is a Model Context Protocol server that lets you connect AI assistants like Claude to your Voyage data. You can ask natural language questions about your conversations, workflows, analytics, and customer insights — and get answers backed by real data.

Which MCP clients are supported?

Voyage MCP works with any MCP client that supports HTTP transport, including:

Claude Code (CLI)
Claude Desktop
Cursor

See the quickstart guides for setup instructions.

Is my data safe?

Yes. Voyage MCP uses OAuth 2.1 with PKCE — the same security standard used by major platforms. Your credentials are never shared with the MCP client. All tools are read-only and scoped to the brand you select during authentication. See Authentication for details.

Brands & Access

Which brands can I access?

You can access the brand you select during the OAuth authentication flow. Your session is scoped to a single brand at a time.

Can I switch brands?

To switch brands, disconnect and reconnect with a different brand selection:

Claude Code: claude mcp remove voyage then claude mcp add voyage --transport http https://mcp.vyg.app/mcp
Claude Desktop / Cursor: Restart the application to trigger a new authentication flow

Can I access multiple brands at once?

Not in a single session. Each MCP connection is scoped to one brand. You would need separate sessions for different brands.

Troubleshooting

I’m getting “unauthorized” errors

Your access token may have expired. Try these steps:

Disconnect the MCP server
Reconnect and re-authenticate
Make sure to select a brand during the approval step

If the issue persists, check that your Voyage account is active and has access to at least one brand.

I’m getting “Brand context required” errors

This means authentication succeeded but no brand was selected. Reconnect and make sure to select a brand during the OAuth approval step.

What if my token expires?

Tokens refresh automatically in the background. If auto-refresh fails, you’ll be prompted to re-authenticate. You won’t lose any data.

The browser doesn’t open during authentication

Check your terminal output for a URL you can copy and paste into your browser manually. Some environments (SSH sessions, containers) don’t support automatic browser opening.

Tools are returning empty results

Make sure:

You selected the correct brand during authentication
The brand has active conversations and workflows
Your date filters (if any) match a period with data