Skip to main content
Every client uses the same server URL:
In Claude, Versive is listed in the connector directory, so you can add it without pasting anything. For every other client, add the URL as a remote MCP server (sometimes called a “custom connector”). Either way, sign in to Versive and approve access when your client opens the browser. No API keys are involved.
You can also find this guide in the app, under MCP in the sidebar.

Discovery for integrators

MCP clients discover OAuth automatically from the server’s protected-resource metadata. Agents and connector catalogs can inspect the public Versive capability manifest for tool names, descriptions, required scopes, prompts, and resources before a user connects. These discovery documents are descriptive and do not grant access. The live MCP tools/list method, tool schemas, and tool calls require OAuth, and every request remains subject to the connected user’s organization role and study permissions.

Client-specific instructions

Versive is in the Claude connector directory. Works in claude.ai and the Claude desktop app.
1

Browse connectors

In any chat, click the + button next to the message box, then Browse connectors.
2

Find Versive

Search for Versive and click Connect.
3

Sign in and approve

Your browser opens Versive — sign in and approve the requested access.
4

Enable it in a chat

In any conversation, enable Versive from the search and tools menu, then ask about your research.
You can also add Versive manually: go to Settings → Connectors, click Add custom connector, name it “Versive”, and paste https://mcp.getversive.com/mcp. Custom connectors require a paid Claude plan.

Disconnecting

Removing the connector from your client stops it from reaching Versive. To fully revoke a grant on the Versive side, ask an organization admin or contact [email protected]. Access also ends automatically if you leave the organization.

Troubleshooting

Connections made before late 2025 used an older grant format that no longer registers tools. Remove the connector and add it again to re-run the sign-in.
Versive runs separate US and EU data regions. Pick the region where your Versive account lives — if you’re unsure, it’s the region in your app URL (getversive.com for US, eu.getversive.com for EU).
Your client may have cached old credentials. Remove and re-add the connector; for mcp-remote bridges, also clear the local cache with rm -rf ~/.mcp-auth.
Access tokens are short-lived and normally refresh on their own. If calls keep failing, your grant may have been revoked or your organization membership changed — reconnect, or check with your organization admin.