Use NeetoKB in Cursor

Check requirements

• Cursor installed on your computer.
• A NeetoKB account.

Connect NeetoKB to Cursor

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

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

Restart Cursor and sign in to NeetoKB when Cursor asks.

In the Cursor CLI, run cursor-agent mcp login neetokb once to sign in. Then ask from your terminal:

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 article, including drafts and private categories. Do not use one on a machine where a person should see only their own articles.

It is the same key the REST API uses. Learn how to generate your API key. Send it in this header:

Authorization: Bearer YOUR_API_KEY

Add the same entry to ~/.cursor/mcp.json, then restart Cursor:

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

Try these prompts

Look things up:

Show me the Getting Started Guide article, including its HTML content.

What categories do I have, and how many articles are in each?

Fill the gaps:

Show the searches that found no article in the last 30 days, then draft an article for the most common one.

Which invalid URLs did visitors open this month? Add a redirection for each one that has an obvious new page.

Organize:

Merge the Billing and Payments tags into Billing.

Create a Billing category under Getting Started and put it first.

Share:

Regenerate the unlisted link for Getting Started Guide. The old one leaked.

Ask your AI assistant to confirm before it creates, publishes, or regenerates anything. These actions affect your live workspace, and regenerating an unlisted link breaks the previous URL immediately.

Troubleshooting

Your AI assistant shows no NeetoKB 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 clients that read a config file, check these:

1. The config key. Claude Code, Cursor, Devin, Antigravity, and Antigravity CLI use mcpServers. VS Code uses servers. Codex uses a [mcp_servers.<name>] section. 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.neetokb.com/mcp/messages, with no trailing slash.
4. The syntax. In JSON, a trailing comma or an unclosed brace makes the whole file unreadable, and other servers stop working 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. Check that the key is not revoked and belongs to the workspace you expect. Generate a new key from your workspace settings if you are unsure.

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

More fixes are in the NeetoKB MCP troubleshooting guide.

Frequently asked questions

Can I use NeetoKB MCP with Cursor or Codex?

Yes. Cursor, Codex, VS Code with GitHub Copilot, Devin, Antigravity, and Antigravity CLI can all connect to the NeetoKB MCP server. See the NeetoKB MCP setup guide for instructions specific to each tool.

Use NeetoKB in other AI assistants

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