Use NeetoRecord in Claude Code

Connect Claude Code to the NeetoRecord MCP server and work with your recordings from your editor or terminal, with your NeetoRecord sign-in or an API key.

Connect NeetoRecord to Claude Code

  1. 1Run this command in your terminal.
  2. 2Start Claude Code, run /mcp, select neetorecord, and sign in to your NeetoRecord account.
claude mcp add --transport http --scope user neetorecord https://connect.neetorecord.com/mcp/messages
Claude Code

> List my NeetoRecord recordings from this week

● neetorecord - ListRecordings · 9 found

You made 9 recordings this week. 3 of them have no title yet.

>

NeetoRecord

Check requirements

  • Claude Code installed on your computer.
  • A NeetoRecord account.

Connect NeetoRecord to Claude Code

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

Start Claude Code, run /mcp, select neetorecord, and sign in to your NeetoRecord account.

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. Antigravity needs one. 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.

Add the server to ~/.claude.json, then restart Claude Code:

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

Let Claude Code use the CLI

You don't have to write these scripts yourself. Claude Code, Codex, or another coding agent can write the automation and use the open-source NeetoRecord CLI to work with your library. Run neetorecord setup claude (or setup codex, setup cursor) once, then ask:

Every Friday at 4 PM, use the NeetoRecord CLI to post this week's new recordings, with their view counts and links, to our Slack channel. Write the script, test it, and set up the cron job.

Using the NeetoRecord CLI, write a script that downloads the transcript of every recording in the Customer calls folder into a Markdown file per call.

You get the convenience of a chat, and the result is a script you can read, run, and commit.

Terminal recording of Claude Code. It lists this week's recordings with the neetorecord CLI, writes a script that posts them to Slack, tests it on a test channel, and adds a cron job that runs at 4 PM every Friday.
Claude Code builds the Friday recordings summary with the NeetoRecord CLI, tests it, and schedules it with cron.

Try these prompts

Jump to the moment something was said

Which of our recordings talks about the pricing page redesign? Jump to the part where it comes up.

Your AI assistant searches transcripts rather than titles, then reads the matching transcript and reports the timestamped segment. Ask it to show what was on screen at that moment and it captures the frame at that timestamp.

Ask a teammate for a recording

Create a recording request titled "Walkthrough of the billing bug" and give me the link to send to Sam.

Your AI assistant creates a recording request and returns the link. Anyone who has the link can upload the recording, so you send it to Sam yourself.

Read a recording from another workspace

Here is a NeetoRecord link a customer sent us. What is in it?

For a publicly accessible recording outside your workspace, your AI assistant uses the public tools to read its details, transcript, and chapters. This works only when the recording needs no sign-in, and it respects what the owner allowed, so a transcript or a download may be unavailable.

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.

More fixes are in the NeetoRecord MCP troubleshooting guide.

Frequently asked questions

Can I use NeetoRecord with Claude Code?

Yes. You can connect Claude Code directly to the NeetoRecord MCP server using claude mcp add, or run neetorecord setup claude to let Claude Code use the NeetoRecord CLI. You can also use both.

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.

Have something to share? Record it instead of scheduling a meeting.

Get started with NeetoRecord today.