MCP Rinne MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-rinne -e 'RINNE_API_KEY=<RINNE_API_KEY>' -- npx -y @codespar/mcp-rinne

{
  "mcpServers": {
    "mcp-rinne": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-rinne"
      ],
      "env": {
        "RINNE_API_KEY": "<RINNE_API_KEY>"
      }
    }
  }
}

[mcp_servers.mcp-rinne]
command = "npx"
args = ["-y", "@codespar/mcp-rinne"]
env = { RINNE_API_KEY = "<RINNE_API_KEY>" }

{
  "mcpServers": {
    "mcp-rinne": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-rinne"
      ],
      "env": {
        "RINNE_API_KEY": "<RINNE_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "mcp-rinne": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-rinne"
      ],
      "env": {
        "RINNE_API_KEY": "<RINNE_API_KEY>"
      }
    }
  }
}

Put your own value in place of <RINNE_API_KEY> (API key sent as x-api-key header on every request. Organization-level keys see all merchants; merchant-level keys are scoped to one merchant). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: RINNE_SANDBOX (Defaults to sandbox (https://api-sandbox.rinne.com.br/core). Set to "false" for production (https://api.rinne.com.br/core)), RINNE_EMAIL (Login identifier for the access-management tools (API Keys, Roles, Permissions, org Users, Zipcode lookup), which reject x-api-key by design and require a JWT session), RINNE_PASSWORD (Login password paired with RINNE_EMAIL), RINNE_COMPANY_ID (Company to select after JWT login, for accounts with access to multiple companies).