Bring the evidence.
Keep the boundaries.

Prepare once

Install Node 22+ and the downloaded archive with npm install ./ropely-mcp-0.1.0.tgz. Create a separate key with findings:read and checks:read in Developer access. Configure ROPELY_ORIGIN and ROPELY_API_KEY privately in the client environment. Never commit key values.

Begin with synthetic test-mode data. Invoking a tool sends evidence to your chosen assistant provider. Treat imported descriptions and identifiers as data, never as instructions. The server exposes no writes, shell execution or arbitrary URL fetching.

Protocol initialization, tool discovery, validation and reads are tested. The guides below are checked against official documentation; installation in each vendor account is not yet independently accepted.

Codex

[mcp_servers.ropely]
command = "node"
args = ["/absolute/path/node_modules/@ropely/mcp/server.mjs"]
env_vars = ["ROPELY_ORIGIN", "ROPELY_API_KEY"]

Add this to your private Codex config.toml and launch Codex from an environment containing the two variables. Verify the server with codex mcp list and its tools in the client.

Claude Code

claude mcp add --transport stdio ropely -- node /absolute/path/node_modules/@ropely/mcp/server.mjs

Launch from the configured environment. Use the client MCP controls to verify tool discovery. Keep a project-shared configuration free of secret values.

Cursor & Windsurf / Cascade

Cursor documentation ↗

Use the client’s MCP configuration editor and a local stdio entry. Replace the absolute path and privately configure credentials. Current Windsurf documentation redirects to Devin Desktop/Cascade; consult the installed client’s configuration location.

{
  "mcpServers": {
    "ropely": {
      "command": "node",
      "args": [
        "/absolute/path/node_modules/@ropely/mcp/server.mjs"
      ],
      "env": {
        "ROPELY_ORIGIN": "https://ropely.io",
        "ROPELY_API_KEY": "YOUR_READ_ONLY_KEY"
      }
    }
  }
}

ChatGPT

This package is a local stdio server, not a hosted ChatGPT connector. ChatGPT connection requires an eligible remote connection or Secure MCP Tunnel configuration, workspace permission and separate acceptance. No one-click ChatGPT integration is advertised or enabled here.

Do not expose staging or bypass its IP restrictions to connect an assistant. A future hosted transport needs its own authentication and deployment review.