Use NeetoRecord in Devin

Check requirements

• Devin Desktop installed on your computer. Devin Desktop is the new name for Windsurf.
• A NeetoRecord account.

Connect NeetoRecord to Devin

Add the server to ~/.config/devin/mcp_config.json:

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

Then run devin mcp login neetorecord in your terminal and sign in to NeetoRecord in your browser. Run devin mcp list to check that neetorecord is listed. The devin command ships with Devin Desktop at /Applications/Devin.app/Contents/Resources/app/extensions/windsurf/devin/bin/devin.

Then ask Devin in a Local session. Devin asks before each NeetoRecord tool call. Choose Allow, or pick the option that allows every NeetoRecord tool for the session:

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 ~/.config/devin/mcp_config.json. Devin uses the key on its next session:

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

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

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.

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.

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.