Set up the MCP server

Every client uses the same server URL:

https://mcp.getversive.com/mcp

Setup is the same everywhere: add the URL as a remote MCP server (sometimes called a “custom connector”), then 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.

Client-specific instructions

Claude
Claude Code
ChatGPT
Cursor
Other clients

Works in claude.ai and the Claude desktop app (custom connectors require a paid Claude plan).

Open connector settings

Go to Settings → Connectors.

Add the connector

Click Add custom connector, name it “Versive”, and paste https://mcp.getversive.com/mcp.

Connect and approve

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

Enable it in a chat

In any conversation, enable Versive from the search and tools menu, then ask about your research.

Add the server from your terminal:

claude mcp add --transport http versive https://mcp.getversive.com/mcp

Then, inside Claude Code, run /mcp and select versive to sign in and approve access. Tools become available immediately after authentication.

Custom MCP plugins in ChatGPT require Developer Mode.

Enable Developer Mode

Go to Settings → Plugins → Developer Mode and turn on Developer Mode.

Add the plugin

Back in Plugins, click + in the top right. Name it “Versive”, set the server URL to https://mcp.getversive.com/mcp, and choose OAuth for authentication.

Approve access

Use it in a chat

Enable the Versive plugin in a new conversation.

ChatGPT can take a few minutes to load the tool list after you connect. If the plugin shows no tools right after setup, use Refresh on the plugin’s connection page or wait a moment and check again. Plugins are enabled per conversation, so make sure Versive is turned on in the chat you’re testing.

Add Versive to .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make it available everywhere:

{
  "mcpServers": {
    "versive": {
      "url": "https://mcp.getversive.com/mcp"
    }
  }
}

Then open Cursor Settings → MCP and click the authentication prompt next to Versive to sign in and approve access.

Versive works with any MCP client that supports remote servers over Streamable HTTP with OAuth — just add https://mcp.getversive.com/mcp wherever your client accepts a remote MCP server and complete the sign-in when prompted. A legacy SSE endpoint is available at https://mcp.getversive.com/sse for older clients.If your client only supports local (stdio) servers, bridge it with mcp-remote:

{
  "mcpServers": {
    "versive": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.getversive.com/mcp"]
    }
  }
}

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

The connection succeeds but no tools appear

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.

I'm asked to choose between US and EU

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).

Tool calls fail after working earlier

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.

​Client-specific instructions

​Disconnecting

​Troubleshooting

Client-specific instructions

Disconnecting

Troubleshooting