Documentation

Using rinkata with Cursor

Using rinkata with Cursor

Connect Cursor to this project from Settings. About two minutes. Nothing to install.

Once connected, ask Cursor for what's on Work, capture ideas, or update tickets, the same project you see on screen.

This path works for every model in Cursor, including Grok Bot.

Step 1: Mint a key

  1. In rinkata, click your name (top-right) → Settings.
  2. Find API keys.
  3. Type a name, anything that reminds you which machine it's for, like cursor. A name is required; skip it and Create key errors.
  4. Click Create key.

rinkata shows the key and, underneath it, a Grok Bot (Cursor) card already filled in, your key and the address you signed in at.

Don't dismiss that panel until you've copied. The key is shown once. If you lose it, mint another.

Click Copy config.

If you already use the rinkata command-line tool, connect Cursor from that tool instead of minting a key. The command-line path does not use this card.

Step 2: Add it in Cursor

Open Cursor's MCP settings and add the copied config, or merge it into Cursor's global MCP file. Keep every other server already in that file.

Then keep going, Step 3 is not optional. A running Cursor holds the old connection.

Step 3: Reload and check

  1. Reload Cursor's tools, or restart Cursor.
  2. Ask: "List my rinkata projects." You should get your workspace's projects back.
  3. Then ask for one of them by name, "what's on Work for <your project>?"

Using it

Talk in plain language, "what's ready to start on <your project>?", "capture an idea called X", "what's on Needs attention?" Cursor looks up the project by name.

You can read and change the same things you can on screen: Ideas, Work, Complete, decisions, and tickets.

If something's not working

What you seeFix
Cursor has no rinkata tools after setupReload Cursor's tools or restart Cursor. The list is read once at startup
"Not authenticated" / 401The key is wrong or was revoked, mint a new one, copy the config again, then restart
"Which project?"Name the project, or ask Cursor to list your rinkata projects first

Replacing your key

Mint a new key, click Copy config, paste. The copied config replaces the existing connection rather than adding a second one.

A running Cursor keeps the old key. Reload tools or restart Cursor after you swap. This is the step people miss.

To cut a key off entirely, revoke it in Settings → API keys. That takes effect on rinkata's side immediately.

See also