> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noimosai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect clients

> Connect Remote or Local MCP to a supported AI client.

## Overview

Choose Remote or Local MCP and connect Claude, ChatGPT Desktop, Codex, Cursor, or VS Code. Normally use Remote, which needs no installation or key management; use Local for local files or headless environments.

## Choose a connection method

Choose according to your environment and whether local files are needed.

| Method | Suitable uses | Authentication | Installation |
| - | - | - | - |
| Remote MCP | Regular AI clients | Browser OAuth | None |
| Local MCP | Headless environments or local files | NoimosAI API key | Node.js and npm package required |

> [!NOTE]
>
> Remote cannot use `upload_media`, `upload_website_source`, or `download_creation`, which access local files. Use Local when these are needed.

## Connect with Remote MCP

Register the NoimosAI-hosted endpoint in your client, then authorize NoimosAI access in the browser.

Prepare these two things:

* A NoimosAI account
* An MCP client supporting Streamable HTTP and OAuth

Use this endpoint URL.

```text theme={null}
https://mcp.noimosai.com/mcp
```

Follow the setup for your client.

> [tab] Claude Code
>
> In Claude Code, add the endpoint with this command.
>
> ```bash theme={null}
> claude mcp add --scope local --transport http noimosai https://mcp.noimosai.com/mcp
> ```
>
> Run `/mcp` in a session, authorize in the browser, then return to Claude Code.

> [tab] Claude.ai / Desktop
>
> In Claude.ai or Claude Desktop, register a custom connector.
>
> Open **Settings → Connectors → Add custom connector** and enter `https://mcp.noimosai.com/mcp`. Save, then sign in and authorize in the browser.

> [tab] ChatGPT Desktop
>
> In ChatGPT Desktop, register an MCP server.
>
> 1. Open **Settings → MCP servers** and choose **Add server**.
> 2. Set the name to `NoimosAI`, transport to **Streamable HTTP**, and URL to `https://mcp.noimosai.com/mcp`.
> 3. Save and choose **Restart**.
> 4. Choose **Authenticate** in the server list and authorize in the browser.
>
> Type `/mcp` in the composer to inspect connected servers. The [current OpenAI guide](https://learn.chatgpt.com/docs/extend/mcp) states that ChatGPT Web uses Remote MCP tools from installed plugins, not local configuration. These direct-connection instructions are for Desktop.

> [tab] Codex
>
> In Codex CLI, add the endpoint and start OAuth with these commands.
>
> ```bash theme={null}
> codex mcp add noimosai --url https://mcp.noimosai.com/mcp
> codex mcp login noimosai
> ```
>
> Check registration with `codex mcp list`. ChatGPT Desktop, Codex CLI, and the Codex IDE extension share MCP settings on the same Codex host.

> [tab] Cursor
>
> In Cursor, add this configuration to the project’s `.cursor/mcp.json`.
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "noimosai": {
>       "url": "https://mcp.noimosai.com/mcp"
>     }
>   }
> }
> ```
>
> Enable NoimosAI in Cursor’s MCP settings and complete browser authentication.

> [tab] VS Code
>
> In VS Code, add this configuration to the workspace’s `.vscode/mcp.json`.
>
> ```json theme={null}
> {
>   "servers": {
>     "noimosai": {
>       "type": "http",
>       "url": "https://mcp.noimosai.com/mcp"
>     }
>   }
> }
> ```
>
> Starting the server opens browser OAuth authentication in VS Code.

Check the NoimosAI account and `mcp:tools` permission on the consent screen. Reconnect afterward and confirm NoimosAI tools appear.

## Connect with Local MCP

Local runs [`@noimosai/mcp`](https://www.npmjs.com/package/@noimosai/mcp), published on npm, as a child process of your client.

Prepare these three things:

* Node.js 20 or later
* An MCP client supporting STDIO
* An API key from the API tab in NoimosAI team settings

Replace `your-api-key` below with your key. Add `NOIMOS_WORKSPACE_ID` only to fix a default workspace.

> [!WARNING]
>
> Never commit or share configuration containing keys. Use a regular NoimosAI key; Developer Platform keys beginning with `nmp_` are not supported.

> [tab] Claude Code
>
> In Claude Code, add the local server with this command.
>
> ```bash theme={null}
> claude mcp add noimosai \
>   --env NOIMOS_API_KEY=your-api-key \
>   --env MCP_TOOL_TIMEOUT=900000 \
>   -- npx -y @noimosai/mcp
> ```

> [tab] Claude Desktop
>
> In Claude Desktop, add this configuration to `claude_desktop_config.json`.
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "noimosai": {
>       "command": "npx",
>       "args": ["-y", "@noimosai/mcp"],
>       "env": {
>         "NOIMOS_API_KEY": "your-api-key"
>       }
>     }
>   }
> }
> ```

> [tab] Codex
>
> In Codex CLI, add the local server with this command.
>
> ```bash theme={null}
> codex mcp add noimosai \
>   --env NOIMOS_API_KEY=your-api-key \
>   --env NOIMOS_MCP_ALLOWED_UPLOAD_ROOTS="$PWD" \
>   -- npx -y @noimosai/mcp
> ```
>
> This permits uploads and downloads only within the folder where the command runs.

> [tab] Cursor
>
> In Cursor, add this configuration to `.cursor/mcp.json`.
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "noimosai": {
>       "command": "npx",
>       "args": ["-y", "@noimosai/mcp"],
>       "env": {
>         "NOIMOS_API_KEY": "your-api-key"
>       }
>     }
>   }
> }
> ```

> [tab] VS Code
>
> In VS Code, add this configuration to `.vscode/mcp.json`.
>
> ```json theme={null}
> {
>   "servers": {
>     "noimosai": {
>       "type": "stdio",
>       "command": "npx",
>       "args": ["-y", "@noimosai/mcp"],
>       "env": {
>         "NOIMOS_API_KEY": "your-api-key"
>       }
>     }
>   }
> }
> ```

Local supports these environment variables:

| Variable | Required | Description |
| - | - | - |
| `NOIMOS_API_KEY` | Yes | Key issued in the API tab of NoimosAI team settings. |
| `NOIMOS_WORKSPACE_ID` | No | Default workspace ID when a tool call omits `workspaceId`. |
| `NOIMOS_MCP_ALLOWED_UPLOAD_ROOTS` | No | Local folders allowed for uploads. Separate multiple paths using your OS path separator. |

Allow only necessary folders. For example, add the absolute path of the current folder as `NOIMOS_MCP_ALLOWED_UPLOAD_ROOTS` in the launch configuration.

Restart your client and confirm tools appear. `chat` and `create_workspace_and_onboard` can take several minutes; allow about 15 minutes if your client supports timeout configuration.

## Try your first tools

Start with read-only operations to inspect the target workspace and available information safely.

Ask your AI client in this order:

1. “List the NoimosAI workspaces I can use.”
2. “Check the target workspace’s brand summary and connected accounts.”
3. “Use that brand information to draft one LinkedIn post. Show only the text; do not publish.”

The first two use read tools such as `list_workspaces` and `get_workspace_context`. The third also requests no publication, so you can review content before choosing the next action.

## Troubleshoot connections

Check the following for your connection method:

* **Remote consent screen does not open** — Remove the connection and add it again.
* **Remote tools are missing** — Check `mcp:tools` permission and that the account has a workspace.
* **Remote token expired** — Reauthorize from the client.
* **Local will not start** — Check Node.js 20+, `npx`, package name, and key.
* **Local cannot select a workspace** — Check `NOIMOS_WORKSPACE_ID` or the tool call’s `workspaceId`.
* **Local cannot read a file** — Check that it is inside a folder allowed by `NOIMOS_MCP_ALLOWED_UPLOAD_ROOTS`.

## Related pages

See these pages for tool selection and other access methods.

* [Use tools](https://docs.noimosai.com/developers/mcp/tools.md)
* [Understand the basics](https://docs.noimosai.com/developers/cli/overview.md)
* [Standard MCP connection guide](https://modelcontextprotocol.io/docs/develop/connect-local-servers)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.