Skip to main content
Switch coding agents without rebuilding your setup. Notis gives each agent the same integrations, skills, and long-term memory through your Notis account. You can connect in two ways:
  • Notis CLI — Use this with ChatGPT desktop, Claude Code, Cursor, OpenClaw, Hermes, OpenCode, or another agent that can run commands on your computer.
  • Remote MCP — Use this with ChatGPT on the web, Claude, Grok, Notion, or another app that lets you add an MCP connection.
Both use the same Notis account. Choose the connection your agent supports; your tools and context stay the same.

​
Connect with the Notis CLI

1

Open your agent

Start a session in ChatGPT desktop, Claude Code, Cursor, OpenClaw, Hermes, or OpenCode. The session must be allowed to run commands on your computer.
2

Give it the setup command

Paste the command into the conversation and ask the agent to run it. If your ChatGPT desktop session cannot run commands, use the ChatGPT Remote MCP steps below instead.
3

Enter your email

Your agent asks for your email address. Notis sends you a secure sign-in link instead of making you complete a separate signup form.
4

Open the link and approve access

The sign-in link opens Notis in your browser. Sign in and approve the CLI for this machine. If you already use the Notis desktop app, signing in there can approve the same CLI profile automatically, but the desktop app does not need to stay open.
5

Let Notis remember across Codex sessions

When setup runs inside Codex or Claude Code, Notis adds its instructions without duplicating anything already there. If you want cross-session memory recall and completed-turn capture, ask your agent to run npx --package @notis_ai/cli@latest -- notis agents install. In Codex, open /hooks, review the Notis hooks, and trust them once.At the start of a session, Notis loads your profile. As you work, it recalls only useful new context and saves completed turns for future sessions. Ask the agent to “remember this” whenever you want something saved explicitly.
6

Approve the apps you want to use

Your agent gives you a Notis link for each app. Open it, approve the connection, then return to the agent.
7

Start working

Ask the agent to use Notis whenever it needs Gmail, Calendar, Notion, Slack, GitHub, Linear, or another connected service.
The same command works in every supported coding agent:
  • ChatGPT desktop — Open a coding session with terminal access, paste the command, and ask ChatGPT to run it.
  • Claude Code — Open Claude Code in your project, paste the command, and follow its prompts.
  • Codex — Open Codex in your project, paste the command, then approve the installed Notis hooks once through /hooks.
  • Cursor — Open your project in Cursor, paste the command into Agent chat, and ask it to run the command.
  • OpenClaw — Start an OpenClaw session that can use your terminal, then paste the command.
  • Hermes — Start Hermes with command access, then paste the command.
  • OpenCode — Open your project in OpenCode, paste the command, and follow its prompts.

​
Connect with Remote MCP

Use this address for every Remote MCP connection:
After you add it, your browser opens Notis. Sign in, check the agent name and permissions, then choose Allow access.

​
ChatGPT on the web

Full Notis actions require ChatGPT Business, Enterprise, or Edu. A workspace admin or owner must allow developer mode first.
  1. In ChatGPT, open Settings → Apps → Advanced Settings.
  2. Turn on Developer mode. If the setting is missing, ask your workspace admin to allow it.
  3. Return to Settings → Apps and choose Create.
  4. Name the app Notis and paste the Notis MCP address.
  5. Create the app, review the tools, and sign in to Notis.

​
Claude

On Pro or Max:
  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Paste the Notis MCP address and choose Add.
  4. Connect and sign in to Notis.
On Team or Enterprise, an owner opens Settings → Connectors, switches to Organization connectors, and adds Notis. Members can then find Notis in Settings → Connectors and choose Connect.

​
Grok

  1. Open grok.com/connectors.
  2. Choose New Connector → Custom.
  3. Paste the Notis MCP address.
  4. Finish the Notis sign-in.
On Grok Business or Enterprise, a team admin must make the connector available to the organization first.

​
Notion

Notion MCP connections require a Business or Enterprise plan. Your workspace must also allow custom MCP connections.
  1. Open Settings → Connections → Discover.
  2. Choose Add Custom MCP.
  3. Enter Notis and paste the Notis MCP address.
  4. Finish the Notis sign-in.
If Add Custom MCP is missing, ask your workspace admin to allow custom connections.

​
Another MCP app

Open the app’s connections or tools settings, add a remote MCP server named Notis, and paste the Notis MCP address.

​
What happens during Remote MCP setup

1

Add Notis

Paste the Notis MCP address into your app and name the connection Notis if it asks for a name.
2

Sign in to Notis

Your browser opens Notis. Sign in if needed.
3

Review the request

Check the agent name, the Notis account being connected, and each permission it requests. Choose Allow access only if you recognise the agent.
4

Return to your agent

The agent finishes the connection and can start finding the right Notis tools for your requests.

​
What the Remote MCP permissions mean

  • Read through Notis — Find and read information in Notis and services you connected to Notis.
  • Take actions through Notis — Create or change information when you ask the agent to take an action.
  • Help connect services — Give you a Notis connection link when a service still needs your approval.
The agent only receives the permissions shown on the approval screen. If it later needs another permission, Notis asks you to approve the connection again.

​
When a service is not connected

If the agent needs Gmail, Notion, Slack, Calendar, or another service that is not connected yet, it gives you a Notis link. Open it, approve the service, then ask the agent to try again. Never paste a password or private access key into the agent.

​
What follows you between agents

  • 1,000+ integrations — Connect an app once, then use it through the CLI or Remote MCP.
  • Skills — Create or install a skill once and keep it available in Notis, Claude Code, Codex, and Cursor. See Skills.
  • Long-term memory — Give each agent the useful context Notis has learned instead of explaining it again.
  • Notis Apps — Build with your favorite coding agent and deploy the result into Notis, through the Notis CLI.

​
When you need the desktop app

Remote MCP does not need it: you sign in to Notis in your browser and never install anything. The Notis CLI does not strictly need it, but the desktop app is the easiest way to get signed in. Signing in to the Notis desktop app also signs the CLI in on that machine, so there is no second sign-in to complete. From then on the CLI keeps its own session alive and works whether or not the desktop app is running. If you prefer, notis login signs the CLI in on its own. The desktop app also syncs skills into local agent folders, builds Notis Apps locally, and connects tools that run on your computer.

​
Remove or reconnect an agent

To remove Remote MCP access:
  1. Open Notis.
  2. Open your account menu.
  3. Choose Notis CLI/MCP.
  4. Find the agent and choose Remove access.
  5. Confirm the removal.
The agent loses its Notis access immediately. Your services stay connected to Notis, so your other Notis features continue to work. To reconnect or change permissions, remove the old connection and add Notis again from the agent’s settings. Notis shows a fresh approval screen.

​
Troubleshooting

  • The CLI is not working — Ask your agent to run npx --package @notis_ai/cli@latest -- notis doctor.
  • Codex does not recall Notis memory — Open /hooks in Codex and trust the Notis hooks. Run npx --package @notis_ai/cli@latest -- notis agents install --codex-only to repair them.
  • The Remote MCP approval expired — Return to the agent and start the connection again.
  • The wrong Notis account appears — Cancel, sign out of Notis in that browser, then restart the connection.
  • The agent says a permission is missing — Reconnect Remote MCP and approve the permission you want it to use.
  • A service is unavailable — Open the connection link from the agent, finish connecting the service, then retry.