# Cursor

> How to connect ZoomInfo MCP to Cursor using the mcp-remote bridge, which handles the browser OAuth sign-in and exposes ZoomInfo to Cursor's Agent.

**Date:** 2026-09-25  
**Source:** https://gtm.ai/docs/mcp/clients/cursor

---

## Overview

Cursor supports custom MCP servers, so you can give Cursor's Agent live ZoomInfo data alongside your code. Cursor connects to ZoomInfo through the **`mcp-remote` bridge**: a small local proxy (run via `npx`) that handles the browser sign-in and exposes ZoomInfo to Cursor over stdio. There is no developer app to register and no client secret to paste; you sign in with your normal ZoomInfo credentials on first use.

## Requirements

- **Node.js 18 or later** with `npx` on your `PATH`. Check with `node --version`. If you don't have it, install from [nodejs.org](https://nodejs.org) or via your package manager.

## Setup

  **Open your MCP config**

In Cursor, go to **Settings → Cursor Settings → Tools & Integrations** and open the MCP configuration, or edit `~/.cursor/mcp.json` directly.

  **Add the ZoomInfo server**

Add the `zoominfo` entry to the `mcpServers` block in `~/.cursor/mcp.json`:

    ```json
    {
      "mcpServers": {
        "zoominfo": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@0.1.38",
            "https://mcp.zoominfo.com/mcp",
            "46818",
            "--static-oauth-client-metadata",
            "{\"scope\":\"openid profile email offline_access zi_api zi_mcp api:data:mcp\"}"
          ]
        }
      }
    }
    ```

  **Restart Cursor**

Restart so Cursor picks up the new server entry.

  **Authenticate**

The first time Cursor uses the server, the bridge opens the ZoomInfo sign-in in your browser. Log in with your normal credentials or SSO and approve access. On success you'll land on a page reading **"Authorization successful! You may close this window and return to the CLI"** (the address bar will show `localhost:46818`). Close the tab and return to Cursor.

    Tokens are cached locally under `~/.mcp-auth/`, so you won't be prompted again until they expire. If Cursor still shows the server as connecting, toggle the MCP server off and on (or restart Cursor) so it picks up the authenticated bridge.

  **Verify the connection**

Open the Agent and ask: *"How many employees does Snowflake have?"* A healthy connection calls the matching ZoomInfo tool and returns live data.

**Next: run your first session.** Once the ZoomInfo server is authenticated, paste this into Cursor's Agent. It starts from your saved GTM context and asks before it spends credits:

## How Cursor Selects Tools

Cursor's Agent reads the ZoomInfo tool descriptions and picks the right tool for your request. You don't need to name a tool, though you can reference ZoomInfo explicitly to steer it. Ask it to *"research Acme Corp"* and it invokes **Account Research**; ask for VPs of Sales at companies like Salesforce and it chains **Find Similar Companies** into **Search Contacts**.

Direct tools (Search, Enrich, Lookup) return data straight into the Agent's context window, so narrow your filters before searching across thousands of records. Research tools synthesize large payloads before returning a summary, which keeps context manageable.

## Troubleshooting

**"Failed during live tool discovery" or the server errors immediately after you add it:** this usually means Cursor was configured with a native `{ "url": "..." }` entry instead of the bridge. Use the `mcp-remote` bridge config shown in Setup above, then restart Cursor.

**`npx` or "command not found" errors:** the bridge requires Node.js. Confirm `node --version` returns 18 or later and that `npx` is on your `PATH`, then restart Cursor.

**Authentication never completes or times out:** make sure you're signing in with your personal ZoomInfo credentials, not a shared or admin-only account. If the browser window didn't open, or the token has gone stale, toggle the server off and on to re-trigger the OAuth flow. You can also clear the cached tokens under `~/.mcp-auth/` and reconnect to force a fresh sign-in.

**The server shows as disconnected:** confirm the JSON in `~/.cursor/mcp.json` is valid (a trailing comma is the usual culprit) and that the endpoint is exactly `https://mcp.zoominfo.com/mcp`. Restart Cursor after any edit.

**No tools appear:** open the MCP settings and confirm `zoominfo` is enabled. Cursor refreshes the tool list when it reconnects to the server.

**Credit errors during enrichment:** check which credits your account has. MCP can't draw from recurring monthly credits, which some older subscriptions carry; free accounts and bulk data credits work. See [Which credits MCP uses](/docs/mcp/credits#which-credits-mcp-uses).

## What's Next

For the field-by-field defaults that apply to any custom MCP form, see [Add ZoomInfo as a Custom Connector](/docs/mcp/clients/custom). For the full tool list, see the [MCP Tools documentation](/docs/mcp/tools).