Connect notespace to your AI app

Every app uses the same address. You sign in once per app and choose which spaces it can see.

https://notespace.sh/mcp
For one space only, use https://notespace.sh/s/<space>/mcp. That connection can never see your other spaces.

Claude (claude.ai and the desktop app)

Tested
  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it notespace and paste https://notespace.sh/mcp as the URL.
  3. Choose Connect. Sign in to notespace, pick the spaces Claude may use, and approve.
  4. In a chat, make sure notespace is switched on in the tools menu, then ask Claude to save or find something.

When Claude asks to change how a space is organized, it shows a confirmation dialog in the chat; nothing changes until you confirm.

Claude Code

Tested
  1. Add the server in your terminal:
claude mcp add --transport http notespace https://notespace.sh/mcp
  1. In Claude Code, run /mcp, select notespace and choose Authenticate. Your browser opens to sign in and pick spaces.

Add --scope user to make it available in every project. Claude Code can install the notespace skills to ~/.claude/skills/, so later conversations start faster.

ChatGPT

Tested
  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Choose Create app. Name it notespace, paste https://notespace.sh/mcp as the URL, and set authentication to OAuth.
  3. Sign in to notespace, pick spaces, and approve.
  4. In a new chat, open the + menu and select notespace for that conversation.

If ChatGPT cannot show a confirmation dialog, requests to change how a space is organized come back as a link; open it to confirm.

OpenAI Dots

Not tested yet

Dots uses the apps connected to your ChatGPT account, so add notespace there first.

  1. Connect notespace in ChatGPT as described above.
  2. Open a Dot and ask it to use notespace, for example “save this to my notes in notespace”. Start with a read, such as “list my notespace spaces”.

OpenAI has not documented whether Dots can use custom MCP servers added in developer mode. Tell us if it works for you.

Codex

Tested
  1. Open Settings → Plugins → MCP and choose Add.
  2. Paste https://notespace.sh/mcp and sign in when prompted.

Grok (grok.com)

Tested
  1. Go to grok.com/connectors and choose New Connector → Custom.
  2. Paste https://notespace.sh/mcp as the URL.
  3. Sign in to notespace, pick spaces, and approve.

Grok Bot

Tested

Grok Bot has no field for a server address. Ask it in a chat to add a remote MCP server:

Add a remote MCP server named notespace at https://notespace.sh/mcp

It then sends you to sign in to notespace, where you pick the spaces it may use and approve.

Muse (Meta)

Not tested yet
  1. Open Settings → Connectors and choose Add custom connector. Paste https://notespace.sh/mcp as the URL.
  2. Sign in to notespace, pick spaces, and approve.

If your Muse has no connector settings, ask it in a chat instead:

Add a custom connector for the MCP server at https://notespace.sh/mcp

Muse runs in Meta's cloud, which is fine: notespace is a public address.

xAI API and your own bots

Not tested yet
  1. On your account page, create an API key. Limit it to the spaces the bot needs, read-only if it only looks things up.
  2. Add notespace to the tools of a request. xAI sends the key as the Authorization header:
{
  "model": "<a Grok model>",
  "input": "What did we decide about pricing?",
  "tools": [{
    "type": "mcp",
    "server_url": "https://notespace.sh/mcp",
    "server_label": "notespace",
    "authorization": "nsk_your_key"
  }]
}

To keep a bot inside one space, use https://notespace.sh/s/<space>/mcp instead. Keep the key secret; revoke it on the account page if it leaks.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP works. Use https://notespace.sh/mcp and let the client sign in with OAuth, or send an API key as Authorization: Bearer nsk_….

If something does not work

The app says a tool does not exist, or new tools are missing
Apps remember the tool list from when they connected. Start a new conversation; if that does not help, disconnect and reconnect notespace in the app.
Writes fail with “read only”
That app was given read-only access to the space. Disconnect it on your account page and connect again with read and write.
The app picks the wrong space
Agents choose by each space's description. Make the descriptions specific on your account page, or connect with a one-space address.
You want to remove access
Every connected app is listed on your account page; disconnect it there. API keys can be revoked on the same page.