mcp-remote
helper, authentication, and per‑client configuration steps.
Prerequisites
Requirement | Why it’s needed |
---|---|
Node.js 18 LTS or newer | mcp-remote (and many editors) run on Node. Verify wit node --version . |
npm / npx | npx fetches mcp-remote on demand. Bundled with Node. |
Recommended: If you don’t have Node.js installed, we recommend usingnvm
(Node Version Manager) for easy installation and management:
1 – Generate a personal access token
You can now generate tokens directly from the Elementary UI: go to User → Personal Tokens. Quick steps:- Open the User → Personal Tokens page and click Generate token.
- (Optional) Add a name/description.
- Copy the token and store it securely — it is shown once. Manage (revoke/rotate) anytime from the same page.
Security
Tokens are user‑scoped bearer tokens and inherit your workspace permissions. Treat them like passwords — do not share or commit them. Keep them secret, rotate regularly, and revoke immediately if compromised.2 – Install mcp-remote
(optional)
You don’t have to install anything globally, our configs use npx to fetch the latest version automatically. If you do prefer a global install, use:
Important:mcp-remote
expects the server URL as the first argument (flags come after the URL). It does not implement--help
; runningmcp-remote --help
will error because--help
is treated as a URL.
3 – Configure your client
Most MCP‑compatible clients read a JSON config that defines mcpServers. Use one of the following patterns.-y
flag?It makes
npx
skip the interactive “install this package?” prompt.
Client‑specific steps
3.1 Cursor IDE
- Settings → Model Context Protocol → Add Custom Server
or edit~/.cursor/mcp.json
(global) /<project>/.cursor/mcp.json
(workspace). - Paste the JSON above.
- Save – Cursor auto‑restarts its MCP agent.
3.2 Claude Desktop
- In the menu bar choose Claude → Settings -> Developer.
- Under Local MCP Servers, click Edit.
- Paste the JSON block
- Restart Claude