Connecting Nemi to an AI assistant

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.

There is no API 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.

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 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.

https://nemilab.com/api/mcp

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.

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, Beam, 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 Beam, 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 cannot reach your photo library. Nemi Gallery is outside the connection entirely.
• 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, section 6.3.

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. The assistant has to ask for access again, and you have to approve it again, before it can do anything.

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, no API key page and no client library. If you need something programmatic that the tool list does not cover, write to support@nemilab.com and say what you are building.