Remine Docs MCP

Multi-tenant MCP server wrapping the Bright MLS Remine Docs RPC API (transactions, forms, e-signing, MLS form fills). Each user enrolls with their own Bright SSO credentials.

Server URL: https://remine.nlma.io/mcp
Auth: OAuth 2.1 (Dynamic Client Registration + PKCE) — clients drive enrollment via the connector flow. Tokenless setup. Enroll →

163 tools registered, covering: deals/transactions, deal-versions (the fill-fields / signing core), folders, packages, source-forms, clauses, checklists, submissions, MLS listing lookup, contacts, comments, files (S3-backed PDF/upload), users, permissions, and a generic remine_request escape hatch.

Claude.ai (Pro / Max / Team / Enterprise)

  1. Settings → Connectors → Add custom connector.
  2. Name: Remine. Remote MCP server URL: https://remine.nlma.io/mcp.
  3. Click Add, then Connect. You'll be redirected here to sign in with your Bright credentials and approve access.

ChatGPT (Pro / Business / Enterprise)

  1. Settings → Connectors → Create.
  2. Name: Remine. MCP Server URL: https://remine.nlma.io/mcp. Authentication: OAuth.
  3. Save, then add the connector to a chat. First use will redirect here for OAuth approval.

Claude Code (CLI)

claude mcp add --transport http remine https://remine.nlma.io/mcp

On first tool invocation, Claude Code opens the OAuth flow in your browser.

Claude Desktop

{
  "mcpServers": {
    "remine": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://remine.nlma.io/mcp"]
    }
  }
}

mcp-remote bridges Streamable HTTP to Claude Desktop's stdio and handles OAuth. Restart after editing.

VS Code (Copilot Chat / Agent mode)

{
  "servers": {
    "remine": {
      "type": "http",
      "url": "https://remine.nlma.io/mcp"
    }
  }
}

Cursor

{
  "mcpServers": {
    "remine": {
      "url": "https://remine.nlma.io/mcp"
    }
  }
}

How enrollment works

Click /enroll (or let the OAuth connector flow drop you there). Enter your Bright MLS email + password. A headless Chromium drives the Bright SSO portal, captures your docs JWT (49-day TTL), and stores your encrypted password so the server can auto-refresh the JWT without manual intervention.

No public Remine API — this is reverse-engineered from bright.remine.com/docs/. Endpoint catalog: 161 named tools + 2 helpers. Bright passwords are stored AES-256-GCM-encrypted at rest using a derived key (HKDF) from REMINE_ENCRYPTION_KEY. The encryption key never leaves the VPS.

/health · Enroll · OAuth metadata: authorization-server, protected-resource.