Codex, Claude, Cursor & other MCP clients

Connect Codex, Claude, Cursor, MCP Inspector or any OAuth-capable MCP client to the RedERP MCP server.

The RedERP MCP server speaks standard Streamable HTTP with OAuth 2.1 discovery, so any compliant MCP client can connect. Use these values everywhere:

Setting	Value
Server URL	`https://rederp.ai/mcp`
Transport	Streamable HTTP (`http`)
Authentication	OAuth 2.1 — automatic discovery, dynamic client registration or Client ID Metadata Documents, PKCE (S256)
Scopes	`sales:read sales:write`

Codex

Once the RedERP plugin is published, install it from the shared Plugins Directory in Codex. Until then, add the server manually:

codex mcp add rederp --url https://rederp.ai/mcp
codex mcp login rederp

Codex opens the RedERP consent page in your browser; sign in with your RedERP email and password. Then ask Codex, for example, "Use RedERP to list my draft quotations".

Claude (web, desktop, mobile)

Settings → Connectors → Add custom connector, name RedERP, Remote MCP server URL https://rederp.ai/mcp, leave the OAuth client fields empty and click Add, then Connect and sign in. Claude for Teams / Enterprise admins can add it once for the whole organization.

Cursor

Add the server to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "rederp": {
      "url": "https://rederp.ai/mcp"
    }
  }
}

Cursor detects the OAuth challenge, opens the consent page and stores the token. The RedERP tools then appear in the agent's tool list.

MCP Inspector (developers)

npx @modelcontextprotocol/inspector

Choose transport Streamable HTTP, URL https://rederp.ai/mcp, click Connect. The Inspector performs the OAuth flow (you can follow each step in the Auth panel), then lists the 20 tools so you can call them with custom arguments and inspect the JSON responses.

Any other client

Point the client at https://rederp.ai/mcp. On the first request the server answers 401 with a WWW-Authenticate header pointing at https://rederp.ai/.well-known/oauth-protected-resource/mcp; the client discovers the authorization server (https://rederp.ai), registers or identifies itself, runs the authorization-code + PKCE flow and retries with a bearer token. Details in Authentication (OAuth 2.1).

Headless / machine accounts:

The MCP server only issues user tokens through the interactive consent page. For unattended server-to-server integrations use RedERP API tokens instead.

Connect ChatGPT

Authentication (OAuth 2.1)