Developers and AI

Connecting Nemi to an AI assistant

One connector URL turns Claude, ChatGPT, Cursor or any other MCP client into something that can work in your Nemi workspace, and an access key covers the clients that cannot sign in.

On this page

Nemi speaks MCP, the protocol assistants use to reach outside their own chat window. Give your assistant one URL and it can list your files, search them, convert one, make a share link, read and write a Nemi Doc, and fill a Nemi Sheet, all inside your account and under your own permissions. The assistant is one you already have, and through this connection nothing is sent to a model provider unless you connect one and ask it to do something.

For most assistants there is no key to generate and no file to edit. The assistant asks Nemi for access, a Nemi page opens in your browser, you press Allow access, and the connection is live. For a script or a client that cannot open that page, you can make an access key instead: see Access keys further down this page.

Which plans have it#

Every plan, the free one included. What the assistant can do is what your plan allows you to do: it uses the same storage, the same conversion allowance and the same document limits as you, so connecting it never lets it past a limit you would hit yourself. Nemi AI, the assistant built into Nemi, is a separate feature on the Pro, Max and Business plans. See What Nemi AI can do for how the two compare.

Your connector URL#

Open Settings and pick the MCP tab. It holds the connector URL and the list of assistants currently connected. The URL is the same for everybody, because who you are is decided by the sign-in, not by the address.

Connector URL
https://mcp.nemilab.com

https://nemilab.com/mcp and https://nemilab.com/api/mcp are the same server. A connection you already made through one of them keeps working, and so does the Claude plugin.

Adding it to your assistant#

  1. 1

    Open your assistant's connector settings

    In Claude that is Settings, then Connectors, then Add custom connector. Other clients name it differently: look for custom connector, custom MCP server or remote MCP.

  2. 2

    Paste the connector URL

    Nothing else is needed. No client id, no secret, no token.

  3. 3

    Press Add, then Connect

    The assistant registers itself with Nemi and sends you to Nemi to approve it.

  4. 4

    Sign in and press Allow access

    A Nemi page opens showing which account you are signed in as and what the app is asking for. If you are signed out, sign in first and you land back on the same page.

  5. 5

    Ask it something

    Try "list my Nemi workspaces". If tools appear in the answer, it is connected.

Connect to Nemi

Signed in asYour name and email address
Requested by

The address the app sends you back to, shown so you can check who is really asking.

This will allow it to

View your workspaces and files. Upload, rename, move and delete files. Create folders, share links and rooms. Convert, compress and edit files. Create and edit Docs, Sheets, Forms and Canvas boards, and read form responses. Read and change your calendar and meetings. Send files with Glide.

Allow access
The approval page. Cancel is next to it, and nothing is granted until you press Allow access.

The Nemi plugin#

The connector gives an assistant the tools. The Nemi plugin adds the know-how: skills that teach it which kind of link fits which job, how to edit a Doc without losing a paragraph, which spreadsheet formulas Nemi can calculate, how to build and read a form, how to lay out a Canvas board and when to ask before deleting or publishing anything. It uses the same connector URL, so adding both gives one set of tools, not two.

  • Claude and Cowork: open Nemi in Claude's plugin directory, press Install and connect the connector when asked.
  • Claude Code: run /plugin marketplace add GuusLab/nemi-plugin, then /plugin install nemi@guuslab.
  • Codex: run codex plugin marketplace add GuusLab/nemi-plugin, then codex plugin add nemi@guuslab.
  • Anything else: the connector URL above is all you need. The skills are plain Markdown at github.com/GuusLab/nemi-plugin if your client reads skills.

In Claude the plugin can also connect on its own when you sign in to Claude, without the Allow access page. Claude tells Nemi which email address you signed in with, and Nemi connects the account that has that address verified, as a primary or an extra address. Such a connection gets full access to your workspaces but never your mail in Nemi Mail: that still needs the Allow access page with the box ticked. If no Nemi account has that address verified, Claude shows the normal sign-in instead. If it does not connect on its own for you, it has not been switched on for your account yet.

What it can reach, and what it cannot#

  • It can reach your files and folders, your share links and upload links, your Nemi Docs, Nemi Sheets, Nemi Forms and their responses, Nemi Canvas boards, Rooms, Glide, meetings, and calendars you created inside Nemi.
  • It can act, not only read. Asked to, it can put a Nemi Doc you own on the open web as a page anyone with the address can read, publish a form so anyone with its link can respond, create a meeting link anyone can open, send files with Glide, change and delete events in calendars you made inside Nemi, and delete files, folders, documents, spreadsheets, forms, canvases and meetings.
  • It cannot reach a calendar account you connected. Nothing from Google Calendar, Outlook or an ICS subscription is available to an assistant, by any means. That is a property of the connection itself and not a setting, so an agenda an assistant reads back to you can be incomplete. See Connecting calendars.
  • It reaches your mail only if you let it. Nemi Mail is off for every connected assistant until you choose what it may do in Mail, Settings, General, Connected AI apps, and then tick Nemi Mail when you connect it. See Using your mail from a connected assistant.
  • It cannot reach your photo library. Nemi Gallery is outside the connection entirely. This is about AI assistants you connect here; an app you sign in to with your Nemi account is a different thing with its own permissions, described in Signing in to apps with Nemi.
  • It only sees what you see. The connection acts as you, so it is bounded by your workspaces and your role in each of them. In a workspace where you may only read, the assistant may only read.

What the assistant reads is then processed by the company that makes it, under your agreement with them. Nothing goes anywhere through this connection except what your assistant asks for, and we do not use your content to train anything. The one Nemi feature that calls a language model of its own is Nemi AI, which is a separate thing you open yourself. The full statement is in the privacy policy.

Edits are stamped as AI, not as you#

Anything written into a Doc or a Sheet through the connection is recorded as an AI actor in that document's own authorship history, block by block and cell by cell. Open the clock icon in the editor and switch to Inspect to see it. It cannot be switched off, and it is what lets somebody months later tell a paragraph you wrote from a paragraph a model wrote. See Writing together.

Disconnecting#

  • From Nemi: Settings, MCP, Connected assistants. Each one shows when it was connected and when it was last used, with a Disconnect button, and Disconnect all removes every one of them at once.
  • From the assistant: remove the connector there. Either side ends it.

Disconnecting revokes the tokens immediately, together with any approval the assistant had not used yet. The assistant has to ask for access again, and you have to approve it again, before it can do anything.

Access keys#

Some clients cannot open a browser page for you to approve: a script, a scheduled job, a build server, or a desktop client without a sign-in step. For those you can make an access key in Settings, MCP, Access keys. If you do not see Access keys there, it has not been switched on for your account yet.

  1. 1

    Press New access key

    Give it a name that says where you will use it, so you can tell your keys apart later.

  2. 2

    Choose its access

    Full access can use every tool. Read only can only use the reading tools, and every writing tool is refused and hidden from its list.

  3. 3

    Choose when it expires

    After 30 days, 90 days or a year, or never. A key that has expired stops working and stays in the list until you revoke it.

  4. 4

    Tick Nemi Mail if it should reach your mail

    Only offered once Connected AI apps is on in Mail settings. Without the tick a key never reaches your mail, whatever your Mail settings say.

  5. 5

    Copy the key

    It is shown once. Nemi keeps only a fingerprint of it, so a key you lose cannot be shown again: revoke it and make a new one.

Point your client at the connector URL and send the key in the Authorization header as a bearer token. No sign-in page opens.

Request header
Authorization: Bearer nemi_key_...
  • It acts as you. A key reaches exactly what a connected assistant reaches, on your plan and with your role in each workspace, and edits made with it are stamped as AI like any other connection.
  • Treat it like a password. Anybody holding the key can use it until it expires or you revoke it. Keep it out of shared documents and code repositories.
  • You can have up to 10 keys. The list shows when each one was made, when it expires and when it was last used. Revoke stops a key on its next request, and Revoke all stops every one at once.

Is there a REST API?#

Not a public one. Today the MCP connection is the only supported way to reach a Nemi account from outside the app, so there is no documented REST API and no client library. An access key is a way into the MCP connection, not into a separate API. If you need something programmatic that the tool list does not cover, write to support@nemilab.com and say what you are building.

It says this account cannot connect an assistant.

The connection is on every plan, so this is not about your plan: it means the account has been suspended, or has not been let in from the waitlist yet. An account on the waitlist can connect as soon as it is in, and an invite lets it in at once. For a suspended account, contact support. Until September 2026 the connection needed the Max or Business plan and this message named them; if an older assistant still says so, remove the connector and add it again.

The assistant never opens the Nemi approval page, or says the connection was refused.

Assistants that run on your own computer, such as Cursor, send you back to an address on that computer or straight into the app, rather than to a website. Nemi accepts all of those, so if a client refuses at the first step, update it to its latest version and add the connector again. If it still fails, remove the connector, restart the client, and connect once more. When the approval page does open, it names the app by where it sends you back to, so a desktop client is shown as an app on this computer rather than by a web address.

The assistant does not see a tool I read about here.

Tools for an app you have not been given yet do not appear. Reconnect the connector after a plan change or a rollout, because most clients read the tool list once when they connect and keep it.

Does Nemi send my files to an AI on its own?

Never on its own. Nothing leaves through this connection unless you connected an assistant and asked it for something. Nemi does call a language model for Nemi AI, the assistant built into the Pro, Max and Business plans, and that too only happens when you open it and send a message. See Your conversations and what is sent.

How long does the access last?

Access tokens are valid for one hour and the assistant renews them quietly in the background until you disconnect. Every renewal hands the assistant a new renewal key and retires the old one. If a retired key is ever used again, which means a copy of it is somewhere it should not be, Nemi ends that connection at once and the assistant asks you to connect it again. An access key you made yourself lasts until the expiry you chose or until you revoke it. Download links it makes are temporary Nemi links, also valid for one hour, and never a raw storage address.

Can I give it read-only access?

If your client asks Nemi for read access only, it is held to the reading tools and every writing tool is refused and hidden from its list. Most clients ask for full access, which is what the approval page then describes.

Related

Still stuck? Email support@nemilab.com and tell us what you were trying to do.