Documentation
Using rinkata in ChatGPT
Using rinkata in ChatGPT
Connect ChatGPT, on the web or in the desktop app, so it can read and update the same project you see on screen.
Nothing to paste. No key, no token, no command. You point ChatGPT at one address and approve a sign-in screen. About two minutes.
How it works
ChatGPT signs you in, the same way Claude does. On first use it sends you to rinkata, you approve, and ChatGPT gets its own connection that it renews. No key exists anywhere in this flow. (Grok still uses a copied key; see its page.)
Connect once and it follows your ChatGPT account: the same plugin works on the web, in the desktop app, and on mobile.
Cut it off later from Settings → Connected apps without touching anything else.
The one address you need is:
https://api.rinkata.dev/mcp
Before you start
You need a rinkata account that's already signed in, ChatGPT authorizes you. If you've never signed in to rinkata in a browser, do that first.
You also need developer mode in ChatGPT, which is what exposes custom connectors. OpenAI notes that availability can depend on account and workspace policy, if you don't see it, that's an account restriction, not a rinkata problem.
Step 1: Turn on developer mode
- In ChatGPT, open Settings → Security and login.
- Scroll to Developer mode.
- Turn it on.
It's badged ELEVATED RISK, and warns that connectors "could modify or erase data permanently." That's OpenAI's blanket label for any server they haven't reviewed, it looks the same whether you're connecting rinkata or something you wrote this morning. Only add servers you trust.
Step 2: Add rinkata
The web app and the desktop app are the same flow, same Plugins page, same dialog. Only the button that opens it differs.
- In ChatGPT's left sidebar, click Plugins (on the web, if it isn't there, look under More).
- Start a new plugin:
| Where you are | What to click |
|---|---|
| ChatGPT on the web | The + to the right of the Search plugins box |
| ChatGPT Desktop | The Create button in the top-right, then choose the plugin option |
Fill in the New Plugin dialog:
| Field | What to put |
|---|---|
| Icon (optional) | Skip it |
| Name | rinkata |
| Description (optional) | Something like "project status, tickets, and specs" |
| Connection | Leave the toggle on Server URL (not Tunnel) |
| Server URL | https://api.rinkata.dev/mcp |
| Authentication | OAuth |
The URL box suggests the wrong thing. Its placeholder readshttps://example.com/sse, but rinkata's path is/mcp, not/sse. Entering/sseis the most common way this fails.
Then two things before the dialog will let you finish:
- Tick "I understand and want to continue" under the orange warning. Create stays greyed out until you tick it.
- Click Create.
You never enter a token here, OAuth is the whole configuration. If you paste a key into a field, you've got the wrong setup.
Step 3: Sign in and approve
The first time ChatGPT actually uses rinkata, it hands you off to sign in.
- Sign in to rinkata if you aren't already.
- You land on "Authorize ChatGPT?". It names the workspace, the account, and the permissions.
- Check the workspace is the right one, then click Approve.
| Permission | What it means |
|---|---|
rinkata:read | Read your projects, goals, specs, tickets, decisions, and status. |
rinkata:write | Create and change project state. |
Approving is per-person, not per-team. Teammates each authorize separately. Disconnecting yours doesn't disturb theirs.
Step 4: Check it works
Ask: "List my rinkata projects." You should get your workspace's projects back. Then try "What's on Work for <your project name>?"
Using it
Talk in plain language, "what's ready to start on <your project>?", "capture an idea called X", "what's on Needs attention?" ChatGPT looks up the project by name.
You can read and change the same things you can on screen: Ideas, Work, Complete, decisions, and tickets.
Disconnecting: this part matters
Nothing you do inside ChatGPT revokes its access. Disconnect, uninstall, or delete in ChatGPT only stops ChatGPT-local use. From rinkata's side nothing has changed. A client that kept its credential could keep renewing it for up to 30 days.
To actually end access:
- In rinkata, click your name (top-right) → Settings.
- Find Connected apps. Each row is one connection.
- Click Disconnect, then Yes, disconnect.
That takes effect immediately. The next request fails and it cannot renew.
Reconnecting later is this page again from Step 2. You'll see Authorize ChatGPT? again; the old connection stays dead.
Two behaviors that look like breakage but aren't:
- The connection lapses after about 30 days without a fresh sign-in. When rinkata tools stop responding weeks later, ask ChatGPT to list your rinkata projects and follow the sign-in again, that's renewal, not a fault.
- Recreating the plugin creates a new connection. Each plugin you create has its own identity, so the old row in Settings → Connected apps sticks around until you disconnect it or it expires. Disconnect the old one; keep the row whose "last used" is current.
If something's not working
| What you see | Fix |
|---|---|
| No Developer mode in Settings | Account or workspace policy doesn't allow it |
| Developer mode is on, but connectors still won't work | Check Lockdown mode, just above it in Security and login |
| Create is greyed out / clicking it does nothing | Tick "I understand and want to continue" |
| Connection won't validate | Check the URL ends in /mcp. The box suggests /sse |
| Plugin created, but ChatGPT has no rinkata tools | Authorization happens on first use. Ask it to list your rinkata projects and follow the sign-in |
| "Not authenticated" / 401 | Disconnect the row in Settings → Connected apps and add it again |
| Sign-in loops, or approving does nothing | Sign in to rinkata in the same browser as the approve screen |
| The approve screen names the wrong workspace | Click Deny. Sign out of rinkata, sign back in with the right account, try again |
| Reads work but changes fail on permissions | Disconnect in Settings → Connected apps and reconnect, approving both permissions |
| rinkata tools stopped working after weeks of not using them | The connection lapsed (about 30 days). Ask ChatGPT to list your rinkata projects and follow the sign-in again |
| Two ChatGPT rows in Settings → Connected apps | You recreated the plugin. Disconnect the row whose "last used" is stale |
| "Which project?" | Tell ChatGPT the project by name, or ask it to list your rinkata projects first |