Connect your assistant

Server details

Setting	Value
Endpoint	`https://connect.neetorecord.com/mcp/messages`
Transport	HTTP
Authentication	OAuth, or `Authorization: Bearer YOUR_API_KEY`

How you connect decides what the assistant can see, so pick the method before the client. See Authentication for what the two mean in practice.

Your assistant	OAuth, scoped to you	API key, scoped to the workspace
Claude, ChatGPT	Yes	Not supported
Claude Code, Codex, Cursor, Gemini CLI, VS Code, Windsurf	Yes	Yes

Claude and ChatGPT only ever act as you. The editor and terminal clients support both, and the difference is one line of config: leave the credential out and the client signs you in over OAuth, supply one and the client reaches the whole workspace.

OAuth, scoped to you

Nothing to create in NeetoRecord beforehand. You give the client the server URL and approve the connection in the browser.

Custom connectors work on claude.ai, in the Claude desktop app, and in Cowork. The steps below are the same in all three, and a connector you add in one shows up in the others.

Open Settings > Connectors.
Click Add, then Add custom connector.
Give it a name and paste the server URL:
https://connect.neetorecord.com/mcp/messages
Leave Advanced settings alone. The OAuth client ID and secret there are for servers that cannot register clients on their own, and NeetoRecord does that automatically.
The Add custom connector dialog, ready to submit.
Click Add, then Connect to start the sign in.

If connectors are managed centrally in your organization, an Owner adds it once under Organization settings > Connectors, after which everyone else connects from their own Connectors list.Anthropic documents the current steps in Get started with custom connectors using remote MCP.

Custom MCP servers are added through developer mode.

Open Settings → Security and login and turn on Developer mode. The Plugins settings section links straight to it.
Go to Plugins, click Browse plugins, then the plus button.
In New Plugin, enter a name, set Connection to Server URL, and paste:
https://connect.neetorecord.com/mcp/messages
Leave Authentication on OAuth. ChatGPT reads NeetoRecord’s OAuth settings from the URL, so Advanced OAuth settings needs nothing from you.
Tick I understand and want to continue, then click Create and approve the NeetoRecord sign in.
The New Plugin dialog with OAuth discovered from the server URL.

OpenAI documents the current steps in Building MCP servers for plugins and API integrations. They renamed the app directory to the plugin directory in July 2026, so older walkthroughs may say “apps” or “connectors” where the UI now says “plugins”.

Add the server without a header. The missing credential is what makes Claude Code sign you in rather than send a key.

claude mcp add --transport http neetorecord https://connect.neetorecord.com/mcp/messages

Run claude mcp list and the server reads Needs authentication. Start Claude Code, run /mcp, pick neetorecord, and complete the sign in in the browser.

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json for a single project, with no headers block:

{
  "mcpServers": {
    "neetorecord": {
      "url": "https://connect.neetorecord.com/mcp/messages"
    }
  }
}

Restart Cursor, then approve the NeetoRecord sign in when it prompts.

Add the server to ~/.gemini/settings.json, or to .gemini/settings.json for a single project, with no headers block. Streamable HTTP servers go under httpUrl, not url, which Gemini CLI reserves for SSE:

{
  "mcpServers": {
    "neetorecord": {
      "httpUrl": "https://connect.neetorecord.com/mcp/messages"
    }
  }
}

Gemini CLI starts the sign in when the server answers with a 401 and registers itself automatically.

Codex uses TOML rather than JSON. Add the server to ~/.codex/config.toml, or to .codex/config.toml for a single project, with no credential fields. OAuth is what Codex falls back to when none are given:

[mcp_servers.neetorecord]
url = "https://connect.neetorecord.com/mcp/messages"

Then start the sign in:

codex mcp login neetorecord

Create .vscode/mcp.json with no headers block. VS Code nests servers under servers, not mcpServers:

{
  "servers": {
    "neetorecord": {
      "type": "http",
      "url": "https://connect.neetorecord.com/mcp/messages"
    }
  }
}

Needs VS Code 1.99 or later with GitHub Copilot in Agent mode. Approve the NeetoRecord sign in when it prompts.

Add the server to ~/.codeium/windsurf/mcp_config.json with no headers block. Windsurf uses serverUrl rather than url:

{
  "mcpServers": {
    "neetorecord": {
      "serverUrl": "https://connect.neetorecord.com/mcp/messages"
    }
  }
}

Enable the server under Settings → Cascade → MCP Servers, then approve the NeetoRecord sign in when it prompts.

Whichever client you started from, NeetoRecord runs the same steps.

Choose your workspace

Enter the subdomain of the workspace you want the assistant to reach. For acme.neetorecord.com, enter acme. See Workspace subdomain.

NeetoRecord dialog headed 'Connect your workspace' with a field for the workspace subdomain and a Continue button — The first screen of the NeetoRecord OAuth flow.

Pick the workspaces to connect

Workspaces to connect lists every workspace your email belongs to. The one you just signed in to is ticked and cannot be unticked. Tick any others you want the same connection to reach.This section only appears when your email belongs to more than one workspace. With a single workspace, the screen goes straight to the details and the buttons.

Authorize

Click Authorize. The assistant is granted access as you, with your permissions, to each workspace you ticked.

There is no API key to create for this route, and nothing to paste back into the assistant. Once connected, name the workspace in a prompt when you want a specific one. To add a workspace later, run the sign in again and tick it.

API key, scoped to the workspace

The same six clients, configured with a key instead. Every tool call then reaches the whole workspace rather than just your own recordings, which is what you want for automation and not what you want on a shared machine.

Add the server to ~/.claude.json under mcpServers:

{
  "mcpServers": {
    "neetorecord": {
      "type": "http",
      "url": "https://connect.neetorecord.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Code after saving.

Add the server to ~/.cursor/mcp.json under mcpServers:

{
  "mcpServers": {
    "neetorecord": {
      "url": "https://connect.neetorecord.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Cursor, or reload the window from the command palette.

Add the server to ~/.gemini/settings.json under mcpServers. Streamable HTTP servers go under httpUrl, not url:

{
  "mcpServers": {
    "neetorecord": {
      "httpUrl": "https://connect.neetorecord.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Codex uses TOML rather than JSON, and takes the name of an environment variable rather than the key itself, which keeps the key out of the file:

[mcp_servers.neetorecord]
url = "https://connect.neetorecord.com/mcp/messages"
bearer_token_env_var = "NEETORECORD_API_KEY"

Export NEETORECORD_API_KEY in the environment Codex runs in.

Create .vscode/mcp.json in your workspace. VS Code nests servers under servers, not mcpServers:

{
  "servers": {
    "neetorecord": {
      "type": "http",
      "url": "https://connect.neetorecord.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

This needs VS Code 1.99 or later with GitHub Copilot in Agent mode. The editor prompts for your API key the first time the server is used.

Unlike the other clients, this config lives inside your project rather than your home directory, so a pasted key can end up in a commit. Add .vscode/mcp.json to .gitignore, or leave the key out of the file and let VS Code prompt for it.

Add the server to ~/.codeium/windsurf/mcp_config.json. Windsurf uses serverUrl rather than url:

{
  "mcpServers": {
    "neetorecord": {
      "serverUrl": "https://connect.neetorecord.com/mcp/messages",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Enable the server under Settings → Cascade → MCP Servers. Windsurf allows at most 100 tools across every connected server, so disable servers you are not using if NeetoRecord’s tools do not appear.

Replace YOUR_API_KEY with a key from your workspace. See Authentication.

Confirm the connection

Ask the assistant something only the server can answer, for example “List my five most recent NeetoRecord recordings.” If it answers with real recordings, the connection works. If it does not, see Troubleshooting.

Getting Started

Reference

Server details

OAuth, scoped to you

API key, scoped to the workspace

Confirm the connection

​Server details

​OAuth, scoped to you

​What the sign in looks like

​API key, scoped to the workspace

​Confirm the connection

Server details

OAuth, scoped to you

What the sign in looks like

API key, scoped to the workspace

Confirm the connection