REWALTO / DEVELOPERS / MCP / INSTALL
Rewalto MCP in Claude Desktop
To connect Claude Desktop to Rewalto, add the server address https://mcp.rewalto.com/mcp and send your API key as an Authorization: Bearer header. The server has 102 tools as of 7 November 2026, 12:39 am IST; 51 are free to call.
Key facts
| Server address | https://mcp.rewalto.com/mcp |
|---|---|
| Header | Authorization: Bearer <API key> |
| Tools listed | 102As of 7 November 2026, 12:39 am IST |
Get an API key
- Create an API key for your organisation, as the API keys guide explains. Its secret is shown once, when the key is created; copy it then.
- For an agent that only reads, give the key data:read and usage:read. Add tools:run only for an agent allowed to propose and approve spending.
- Every request to the MCP server needs the key, the free catalogue tools included. Put it in the placeholder below (rwk_your_key, or the environment variable the snippet names).
See API keys for how to create, list and revoke a key.
Add Rewalto to Claude Desktop
In Claude Desktop, open Settings, then Developer, then Edit Config. That opens claude_desktop_config.json: on macOS ~/Library/Application Support/Claude/claude_desktop_config.json, on Windows %APPDATA%\Claude\claude_desktop_config.json.
claude_desktop_config.json
{
"mcpServers": {
"rewalto": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.rewalto.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer rwk_your_key" }
}
}
}Claude Desktop's config file starts local programs, so the server is reached through mcp-remote, an open-source bridge that runs with Node.js and sends the header on every request.
Leave no space after Authorization: inside args; the space belongs in AUTH_HEADER, as mcp-remote's own instructions advise. Quit and reopen Claude Desktop after saving.
Claude's custom connectors take the server address alone and use Sign in with Rewalto instead of an API key.
Check the connection
- Reach the server. Open Settings, then Developer: rewalto is listed as running, and its tools appear in the chat's tool menu. Rewalto's live tool list has 102 tools; the ones marked for a signed-in dashboard only are refused to an API key. If it shows an error, the key is missing or not accepted: the server answers 401 to a request without a valid key.
- Call a free tool. Ask the agent: "Use Rewalto's list_catalogue_categories tool and list the categories." The tool is free and spends no credits.
- Read a result. The answer lists Rewalto's catalogue categories. They match the public list at https://api.rewalto.com/v1/catalogue/categories, which needs no key.
Check the key from a terminal
curl -sS https://mcp.rewalto.com/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-H "authorization: Bearer $REWALTO_API_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'The answer names your organisation, with credential kind api_key and the key's permissions. It spends nothing.
Questions people ask
- Do I need an API key to use Rewalto in Claude Desktop?
- Yes. Every request to the MCP server needs a credential, the free catalogue tools included. Send an API key as Authorization: Bearer followed by the key.
- Does connecting cost credits?
- No. Connecting, listing the tools and calling the free tools cost nothing. A tool marked as spending credits charges only for data delivered, at the published rate, and a run that delivers nothing costs nothing.
- Which permissions should the key have?
- data:read opens the data reads and usage:read the credit balance and usage. Add tools:run only for an agent allowed to create and approve quotes; a tool whose permission the key lacks is refused.
- Where do the Claude Desktop settings come from?
- From mcp-remote's instructions for custom headers, with Rewalto's server address and header filled in. If Claude Desktop changes its format, its documentation decides.