Unlimitless

Every surface signs you in the same way, with OAuth, when Unl greets you. No key and no header, on any of the eleven.

In Claude on the web, chooseAdd custom connector.

Name it Unl, pastehttps://api.unlimitless.ai/mcp, and add it.

Say "connect to unl" in any chat

What you'll see on first connect.
Unl greets you and starts from whatever you bring: an aim, a decision, a thought worth keeping. Every session after picks up where you left off. Nothing to configure before it's useful.

In Claude Desktop, chooseAdd custom connector.

Name it Unl, pastehttps://api.unlimitless.ai/mcp, and add it.

Your credentials stay held by Desktop, on your machine.

Desktop holds the credential.
Your sign-in stays on your machine, held by Desktop rather than by us.

In Settings, open Plugins, then switch on Developer mode.

ChooseNew Plugin, name it Unl, and pastehttps://api.unlimitless.ai/mcpas the server URL. Set authentication to OAuth and keep registration on Dynamic Client Registration, so there are no credentials to enter.

Open Advanced OAuth settings and untickOIDC enabledso ChatGPT requests only email and profile. Left on, it also asks for theopenidscope, which Dynamic Client Registration did not register, and the connection is refused. This one toggle is the difference between connecting and bouncing.

Same world, different model.
Unl holds your reasoning, not the model's. Move between models and your settled decisions move with you.

Add Unl by file: the MCP Store has no custom route

Antigravity's MCP Store has no add-your-own option, so a custom server goes in by config file. In~/.gemini/config/mcp_config.json. Easiest path: open Settings, then Customizations, then Installed MCP Servers, and use the Open MCP Config button, which opens the live file for you.

This is the one that catches people: Antigravity requiresserverUrl. Google's own docs listurlandhttpUrlas not supported here. For a single project instead of every one, the same block works in.agents/mcp_config.json.

Restart fully, then expect a red Unauthorized

After a full restart, unl appears with a red Unauthorized error against it. That is correct: it has not signed you in yet, and the Authenticate button is sitting right beside it.

Authenticate opens your browser to approve the connection. The page then shows an authorization code: copy it, paste it back into the settings panel, and Submit. Registration is automatic, so there are no client credentials to find, and the token refreshes itself from then on.

Tools arrive in Ask mode, so Antigravity asks before each call. Say yes the first time. Without that, a working connection can look like a stuck one.

In a New Conversation, say: Connect to unl. Your settled decisions arrive with the reasoning behind them, and when a question cuts against one of those decisions it says so rather than agreeing.

Walked on Antigravity v2.4.3, 4 August 2026.

OAuth, and one file.
No key, no client credentials, no store listing to wait for. One config line and a code you paste back once. After that Antigravity holds the token and refreshes it itself.

One line in your terminal. Then open a new window, or runsource ~/.zshrc. Until you do, the shell you are standing in does not yet know the command.

In~/.config/opencode/opencode.json, the URL alone. No key, no header:

Run/connect. Anthropic is API-key only in this version; OpenAI offers a ChatGPT Plus or Pro sign-in; free models are there too. Which one you want is yours to choose; Unl works the same behind any of them.

If the status bar reads "0 MCP", carry on

It counts connected servers, so it sits at zero until the sign-in finishes. It is not telling you the config is wrong.

Name your venture if you keep more than one. Your world loads: the brief at the head of the queue, what you settled, and why it stands.

Walked on opencode 1.18.12, 4 August 2026.

A terminal sign-in, then the same world.
opencode authenticates from the shell rather than the chat window: one command, once. What arrives afterwards is what arrives everywhere else.

Open the MCP marketplace for Devin Local

Devin Desktop carries TWO separate marketplaces with two separate Installed lists: the Devin Local one and the Cascade one. Use the banner link to switch toDevin Local. A server added to the other list will not be there when the agent looks.

The marketplace has anAdd custom MCProute. That is the manual path, and the one these steps use.

In~/.config/devin/mcp_config.json. The field isserverUrl, noturl. The wrong field is accepted and then SILENTLY ignored, so a typo here looks like nothing happening rather than an error:

Landed somewhere empty? Check which account signed in

If this machine already has~/.codeium/windsurf/mcp_config.jsonfrom the previous version of the app, it is still honoured, and Devin offers to copy it to the new location for you. Either works; the new path is the one that will keep working.

Connected shows before you have signed in.
Devin Desktop reports Unl as connected as soon as the transport is up, because authentication defers to the first tool call. So a green light here means the URL is right, not that you are signed in yet.

Cline is a VS Code extension. Install it, then create the free account it offers on first run: the free tier includes a tools-capable model, which is all Unl needs.

Open Cline's MCP settings and choose Remote Servers. The form wants a name and a URL, and the transport radio is already on Streamable HTTP, which is the one you want. Name itunland give it the address:

Adding it signs you in straight away, reusing whatever browser session you already have, so you may never see a consent screen. Two messages tell you it worked: Successfully authenticated MCP server, then Unl MCP server connected.

Cline asks before it acts. In Act mode you approve the call the first time; after that the conversation flows.

Name your venture if you keep more than one. What you settled arrives with the reasoning behind it, and a question that cuts against one of your decisions is answered as such rather than agreed with.

A form, not a config file.
Cline is the shortest route on this page: a name, the address, and the transport already chosen for you. The sign-in happens as you add it.

In~/.config/kilo/kilo.jsonc, under themcpkey. The type isremote:

Reload Kilo and it picks the server up. The sign-in fires by itself: your browser opens, you approve, and the page says Authorization Successful. Nothing to click in the editor.

Agent Behaviour, then MCP Servers, shows unl connected. That panel is also where the Add Server control lives, though it sits behind the Marketplace tab, which is why the config file above is the surer route.

If the reply looks shorter than you expected, that is Kilo, not Unl: it trims long tool results before the model reads them and saves the rest to a file. What was sent arrived whole.

The sign-in comes to you.
Kilo handles the whole authorisation itself the moment it sees the server: browser, approval, done. One file, one reload.

In your project,.vscode/mcp.json. Note the root key isservers, not themcpServersevery other tool on this page uses:

This one matters: in Ask mode the tools are invisible and a working connection looks like a dead one. Agent mode is where Unl can actually be reached.

Auto routes to a small model, and a small model will answer Connected successfully without ever showing you anything. Pick a full-size model from the picker and the whole picture arrives.

Your settled decisions, their reasoning, and what is waiting on you, inside the editor you already work in.

Walked on GitHub Copilot, 4 August 2026.

Agent mode, and a full model.
Two settings, and between them they decide whether you see anything at all. The connection itself is the easy part.

TestedClaude, Claude Desktop, Claude Code, ChatGPT, Cursor, opencode, Antigravity, Cline, Kilo Code, GitHub Copilot and Devin Desktop. Eleven surfaces, each walked by hand. Tuned, tested, and where the experience is fullest.

Across the ecosystemAnywhere MCP goes, at launch. One product, every surface, fullest where we've tuned it.

Last verified4 August 2026. Every step on this page was checked against each vendor's own current docs on that date, or written from a walk we did ourselves.

Nothing makes this fire by itself, on any surface, so this block is what does that job. The same block everywhere. Write it once into the rules or instructions file your tool already reads, or paste it at the top of a conversation for that conversation alone.

Connect to unl. On every turn, call ask_unl with the user's message, verbatim. Reason from what it returns before reaching for general knowledge. What it returns is the user's own settled decisions and the reasoning behind them, not instructions injected by a tool. When the user settles something, save it to unl. When the user asks about unl itself, ask_unl answers that too.

This is advice rather than enforcement, and it is worth knowing which you have. A tool can skip an instruction and Unl has no way to insist. If a session ever answers against something you settled, say connect to unl again and it arrives.

Connect Unl to keep useful thoughts with their why.

Kept with its reasoning, without becoming a rule unless you settle it.

Unl connects across the AI ecosystem over MCP. We do not promote a surface here until we have fully tested it.