# Connect Myplan to your app

One MCP endpoint: `https://myplan.lol/mcp`. Agents that can run commands need one sentence: `Connect to myplan: follow https://myplan.lol/setup`. Choose the instructions for the app where you want to use Myplan. Installing a server configuration does not by itself authenticate it or load tools into an existing conversation.

## Coding apps: one command

Run the command in a terminal on the same computer or server as your coding app. Node.js 22 or newer is required.

| App | Command |
| --- | --- |
| Codex | `npx myplan codex` |
| Claude Code | `npx myplan claude-code` |
| Cursor, including remote environments | `npx myplan cursor` |
| Grok Build | `npx myplan grok-build` |

The same package is served pinned at `https://myplan.lol/connect.tgz` for another deployment (`--url`) or an offline review; `npm i -g myplan` installs the `myplan` command.

Without an app argument, the installer asks which one to configure. It configures one selected app for all projects by default; `--project` limits installation to this project. Run from the project where you use the app so the installer can identify conflicting project configuration.

1. Run the command. It checks configuration and starts device sign-in.
2. Open its approval link in **any browser, on any device**. Sign in to Myplan, choose access, and approve. Leave the terminal command running until it reports **Connection verified**.
3. Reload your coding app using the instructions below.
4. Ask: **“Use Myplan to list the workspaces I can access.”** A successful tool call confirms this app session has the connection.

| App | Load the connection |
| --- | --- |
| Codex | Start a new session; `/mcp` shows the connected server. |
| Claude Code | Restart Claude Code; `/mcp` shows the connected server. |
| Cursor | Reload the window; check Settings → Tools & MCP. |
| Grok Build | Restart Grok Build. |

The same flow works over SSH, in containers, and on a VPS. Approval does not redirect to a localhost listener. The connector stores and refreshes credentials privately; never paste tokens into config, prompts, or chats.

When a Myplan workspace's Share → Agents panel supplies a command, use it unchanged: its `--scope` preselects that workspace or item during approval. To request a known workspace yourself:

```sh
npx myplan codex --scope 'account workspace:ws_example'
```

Replace `ws_example` with the real ID. An item scope is `account note:<workspaceId>/<documentId>` or `account canvas:<workspaceId>/<boardId>`, with actual IDs rather than the placeholders. `--url https://your-host/mcp` selects another Myplan deployment; download its installer from that same host.

For a connection problem, run the install command again. Keep its diagnostic result; do not report success merely because approval completed. A revoked grant needs a fresh approval. For Codex diagnostics, run:

```sh
npx myplan status codex
```

To sign in again, run `npx myplan codex --reauth`. Substitute the app you installed; keep any `--url`, `--project`, and concrete `--scope` options from the original command.

## Cursor on your computer

Share → Agents → Cursor has an **Add to Cursor** link. Accept the installation, open Settings → Tools & MCP, and connect or authenticate `myplan`. Sign in to Myplan and approve. Enable its tools, then ask it to list your workspaces.

The link carries only the server URL, so choose workspace/item access during approval. For a remote Cursor environment use the command above.

## Claude web / desktop

Custom connectors are available on Claude Free, Pro, Max, Team and Enterprise; Free accounts can add one. A Team or Enterprise Owner first adds it through **Organization settings → Connectors → Add → Custom → Web**; members then find it under **Customize → Connectors** and select Connect.

For individual accounts, open **Customize → Connectors → + → Add custom connector**. Name it `myplan`, enter `https://myplan.lol/mcp`, connect, and approve access in Myplan. Start a conversation with the connector enabled and ask it to list your workspaces. These remote connectors belong to your Claude account and also work in Claude Desktop and Cowork.

Source: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp

## ChatGPT web / desktop

For web setup, your account and workspace policy must allow Developer mode. Open **Settings → Security and login → Developer mode**, then **Plugins → +**. Add the name `myplan` and the server URL `https://myplan.lol/mcp`, create the connection, and approve authentication. Start a new conversation and enable the connection from the tools menu. Ask it to list your workspaces.

On the desktop app, **Settings → MCP servers → Add server → Streamable HTTP** also accepts the URL. Save, Restart, then Authenticate. These local MCP settings are shared with Codex on the same host; ChatGPT web does not read local Codex configuration. For a remote Codex host, use the terminal connector above.

Source: https://developers.openai.com/apps-sdk/deploy/connect-chatgpt and https://developers.openai.com/codex/mcp

## Grok web / desktop

Business and Enterprise organizations need an administrator to provision the connector first. Open https://grok.com/connectors, then **New Connector → Custom**. Enter `https://myplan.lol/mcp`, authenticate, and approve. Start a conversation and ask it to list your Myplan workspaces. Use Grok web if your desktop version does not expose the connection.

Source: https://docs.x.ai/grok/connectors

## Hermes Agent

Hermes supports device sign-in directly, including on a server or in a messaging gateway.

1. Configure `hermes config set mcp_servers.myplan.url https://myplan.lol/mcp`, `hermes config set mcp_servers.myplan.auth oauth`, and `hermes config set mcp_servers.myplan.oauth.flow device`.
2. Run `hermes mcp login myplan --flow device` in the background; it waits for approval. Read its output for `Code: XXXX-XXXX`.
3. Send the user one approval link: `https://myplan.lol/device?code=XXXX-XXXX` using that actual code.
4. Wait for `✓ Authenticated`. Exit code 0 alone is not success; on `✗` or expiry, start a new attempt.
5. Run `hermes mcp test myplan`. In a messaging gateway, send `/reload-mcp`, then make a Myplan tool call.

## Manual configuration and other apps

Use native OAuth only when the app's browser approval can return to that app. For coding apps on SSH/VPS, use the device connector above.

`npx add-mcp https://myplan.lol/mcp --name myplan` writes configuration **only**. It does not sign you in. The authentication step depends on the app:

- Codex: `codex mcp login myplan`, approve, then start a new session and check `/mcp`.
- Claude Code: `/mcp` → myplan → Authenticate, approve, and check tools.
- Gemini CLI: `/mcp auth myplan`, approve, then check tools.
- Cursor, VS Code, Kiro, LM Studio: connect or authenticate myplan in the app's MCP settings, approve, then enable/refresh its tools.

JSON formats differ by client. For apps that accept `mcpServers` and `type: "http"`:

```json
{"mcpServers":{"myplan":{"type":"http","url":"https://myplan.lol/mcp"}}}
```

Clients without browser OAuth can implement the device grant (RFC 8628): discover `/.well-known/oauth-authorization-server`, register the client, request a device code with `resource=https://myplan.lol/mcp` and the desired scope, show `verification_uri_complete`, and poll the token endpoint at its interval. Respect denial, expiry, and `slow_down`.

These instructions describe supported configuration paths and official client guidance. Real-client verification, versions, and known limitations are recorded in the project's verification documentation; a documentation-backed path is not a claim that every client version has passed a live smoke test.