NeetoRecord MCP server

What is NeetoRecord MCP?

NeetoRecord MCP lets AI assistants like Claude and ChatGPT work with your NeetoRecord library. Once it's connected, you can ask your AI assistant to find the recording where something was said, summarize a video you don't have time to watch, look at what's on screen at a given moment, and tidy up titles, tags, and folders, in the same conversation where you're already working.

MCP stands for Model Context Protocol, an open standard for connecting AI assistants to the apps you use. You don't need to know anything about it. You connect once, sign in to NeetoRecord, and start asking.

Your AI assistant talks to the NeetoRecord MCP server. NeetoRecord hosts it, so there's nothing to install or keep updated, and every workspace uses the same address:

https://connect.neetorecord.com/mcp/messages

When you connect, you sign in with your NeetoRecord account and pick your workspace. The assistant then works as you: it sees only the recordings you can see, and does only what your role allows. It can search recordings by title or by what was said, read transcripts, chapters, summaries, and action items, look at a frame at any timestamp, upload videos, organize recordings into folders and tags, share and embed them, add calls to action, request recordings from others, manage team members, and read view counts. You never name a tool; you ask in plain language. The full list is in the NeetoRecord MCP tools reference.

NeetoRecord also has a command-line tool, the NeetoRecord CLI. It works with the same library, but runs in your terminal, in scripts, and in scheduled jobs. It's open source, so you can read exactly what it does, change it, and build on it.

Connect any MCP client

Every client uses the same server URL, https://connect.neetorecord.com/mcp/messages, over HTTP (Streamable HTTP). Sign in with your NeetoRecord account in each one. To use an API key instead, see Connect with an API key.

Step-by-step guides for each AI assistant:

• Claude
• ChatGPT
• Claude Code
• Cursor
• Codex
• VS Code
• Antigravity CLI
• Devin
• Antigravity

Which sign-in each client supports

Sign in and choose permissions

When you sign in, enter your workspace subdomain, not your email address. For acme.neetorecord.com, enter acme.

What each permission allows

If you leave a permission unticked, a tool that needs it is refused with a message that names the permission. Nothing is broken and nothing half happened. For example, a read-only connection can list recordings and read transcripts, but cannot retitle, move, or delete anything. To grant it later, remove the connector and add it again with the box ticked.

For developers: the OAuth metadata is at https://connect.neetorecord.com/.well-known/oauth-authorization-server. The server supports the authorization_code and refresh_token grants, requires PKCE (S256), and issues refresh tokens. Clients register dynamically at https://connect.neetorecord.com/mcp/oauth/register, and loopback redirect URIs are accepted. The scopes are read, write, delete, and offline_access.

Connect with an API key

An API key is not tied to a person. Every tool call reaches the whole workspace, and role checks do not run. Use a key for automation that must see every recording. Do not use a key on a machine where the person should see only their own recordings.

Get a key from your workspace: how to generate an API key. It is the same key the REST API uses. Send it in this header:

Authorization: Bearer YOUR_API_KEY

Replace YOUR_API_KEY with your key in the snippets below.

Each AI assistant's guide shows where its config file lives and how it sends the key.

How each interface signs in

NeetoRecord MCP tools

Once you connect, your AI assistant lists every tool and what it does, and you never need to name one. This is a summary of what the tools cover.

• Recordings. Find recordings by owner, date, folder, tag, title or what was said, read their details, change titles, summaries and tags, move them into folders, upload an MP4 video, and delete them.
• Transcripts and chapters. Read transcripts, action items and chapters, and start generating any of them. Action items are made by sending the transcript to OpenAI.
• Sharing and media. Get a recording's share link and embed code, prepare and find the MP4 download, and capture a still frame at any moment.
• Folders and tags. List and create folders, including nested ones, and list tags.
• Calls to action. List the call-to-action buttons on a recording and add new ones.
• Analytics. See view counts for the whole workspace or for one recording.
• Recording requests. Create a link that anyone can use to upload a recording to you.
• Team members. List and read members, invite people by email with a role, change their details or role, and deactivate them. This needs the permission to view or manage team members.
• Public recordings. Read the details, transcript, chapters, share link, embed code, download and screenshots of recordings in other workspaces. This works only for recordings that need no sign-in, and it respects what the owner allowed.

What to know before you connect

• Deleting a recording is permanent. It removes the recording and everything made from it, and it cannot be undone. Check what is about to be deleted before you approve it.
• Over OAuth, results follow your role. Lists and searches show only the recordings you can see, and a recording you cannot open is refused. An API key sees the whole workspace.
• Downloads happen in the app. The assistant cannot hand you a file. It tells you whether the MP4 is ready and gives you the recording page to download it from.
• Uploads need your computer. An assistant that cannot send a file from your machine cannot finish an upload.
• Transcripts go to OpenAI for action items. Starting action item extraction sends the transcript to OpenAI.
• You cannot deactivate your own account. Deactivating a member stops them signing in, and their recordings stay.

Troubleshooting

Your AI assistant shows no NeetoRecord tools

Restart the client first. Every client reads its MCP config at startup.

On Claude or ChatGPT, confirm that you added the connector and finished the sign-in. In ChatGPT, the plugin is created only after you tick I understand and want to continue.

On Claude Code, Cursor, Codex, VS Code, Devin, Antigravity, or Antigravity CLI, check these:

1. The config key. Claude Code, Cursor, Devin, Antigravity, and Antigravity CLI nest servers under mcpServers. VS Code uses servers. Codex uses a [mcp_servers.<name>] section in TOML. A server under the wrong key is ignored silently.
2. The URL key. Antigravity and Antigravity CLI expect serverUrl. Claude Code, Codex, Cursor, Devin, and VS Code expect url.
3. The endpoint. It is https://connect.neetorecord.com/mcp/messages, with no trailing slash.
4. The syntax. In JSON, a trailing comma or an unclosed brace makes the whole file unreadable, which takes out your other servers too.

The connection is refused or unauthorized

With an API key, the Authorization header must read Bearer YOUR_API_KEY, with the word Bearer and one space before the key. Confirm the key is not revoked and belongs to the workspace you expect. A key from one workspace does not work in another. Generate a new key if you are unsure.

With OAuth there is no key to check. Remove the connector and add it again to run the sign-in from the start.

The client sends a key when you meant to sign in

A client that finds a credential in its config never starts the OAuth flow. Remove the headers block, or the bearer_token_env_var line in Codex, and restart the client. It then opens the sign-in.

The client asks you to sign in when you meant to use a key

The credential is missing, so the client falls back to OAuth. Add the headers block with "Authorization": "Bearer YOUR_API_KEY", or set bearer_token_env_var = "NEETORECORD_API_KEY" in Codex and export that variable. Then restart the client.

The sign-in fails at the workspace step

The first screen needs a workspace subdomain or a workspace URL, not an email address. For acme.neetorecord.com, enter acme.

Your AI assistant sees fewer recordings than expected

This is scoping working as intended. An OAuth connection acts as the person who approved it, so lists and searches show only what you can see, and a recording you cannot open is refused. If your AI assistant needs to reach everything in the workspace, use an API key.

Your AI assistant reaches the wrong workspace

An OAuth connection covers the workspaces you ticked while approving it. To add another, sign in again and tick it. An API key belongs to exactly one workspace, so reaching the wrong one means the wrong key. Add the server a second time with the other key and a different server name.

VS Code never offers the tools

MCP needs VS Code 1.99 or later with GitHub Copilot in Agent mode. It is not available in Ask or Edit mode. Check the version, switch Copilot to Agent mode, and confirm that .vscode/mcp.json is in the workspace you have open. With an API key, VS Code asks for the key the first time it uses the server, so answer that prompt.

Devin or Antigravity connects but the tools are missing

Enable the server after saving the config. In Devin, open the ... menu at the top of a Devin chat in the IDE view and turn the server on, then run devin mcp login <name>. In Antigravity, go to Settings → Customizations.

Claude shows the connector as unauthorized

Open Customize → Connectors (claude.ai/customize/connectors), remove NeetoRecord, and connect it again from the NeetoRecord listing. On a Team plan, Requested means an admin has not turned NeetoRecord on yet. An admin turns it on under Organization settings → Connectors (claude.ai/admin-settings/connectors).

Check that the server is reachable

The server publishes its OAuth metadata without any credential, so one request tells you whether the problem is on the server or in your client:

curl -s https://connect.neetorecord.com/.well-known/oauth-authorization-server

A JSON document whose issuer is https://connect.neetorecord.com means the host is reachable and answering, so look at your client's setup next. It does not prove that every tool call succeeds. No answer, or an error page, means the server cannot be reached from your network. Try again in a few minutes, and if it persists, tell us.

Still stuck

Reach us through the help center, or at support@neetorecord.com. Tell us which client you are using and what your AI assistant reports when it tries a NeetoRecord tool.

Frequently asked questions

Does NeetoRecord MCP require an API key?

No. Sign in with your NeetoRecord account and approve access. There's no API key to copy or manage.

Any client that can send an Authorization header can also use a NeetoRecord API key instead. Claude and ChatGPT use sign-in only. However, API keys provide access to the entire workspace rather than operating with your individual permissions.

Where is the NeetoRecord MCP server hosted?

NeetoRecord hosts the MCP server at https://connect.neetorecord.com/mcp/messages. You don't need to install, configure, or maintain a server yourself.

Use NeetoRecord in other AI assistants

Prefer the terminal? The NeetoRecord CLI reaches the same data from your shell, your scripts and your coding agent.