Reading this in another language? Use your browser's built-in translate option. Button and field names stay in English on purpose, to match what you see in Keysender.
Connect Claude, or any other MCP-compatible assistant, to your Keysender account so it can read your orders, stock, and customers and act on them in plain language. The server runs on your own machine and only reaches the account tied to your API key.
TL;DR
keysender entry to your assistant's MCP config with those values, then fully restart it.The Keysender MCP server is being published; the steps below apply as soon as it is available.
Make sure you have:
node --version.Open your assistant's MCP config. In Claude Desktop, go to Settings > Developer > Edit Config to open claude_desktop_config.json. In Cowork, go to Settings > Connectors and add a custom server with the same JSON.
Add a keysender entry under mcpServers, replacing the placeholders with your own key and secret.
{
"mcpServers": {
"keysender": {
"command": "npx",
"args": ["-y", "@keysender/mcp-server"],
"env": {
"KEYSENDER_API_KEY": "your_api_key",
"KEYSENDER_API_SECRET": "your_api_secret"
}
}
}
}
Save the file.
Fully restart the assistant. Quit and reopen it, do not just close the window.
Ask your assistant "how did we do today". It should return today's and this month's transactions, sent codes, and your credit balance, pulled from your live account.
The server ships the same 30 tools the panel relies on, split between reading and acting. For example:
buyer@email.com for 4.99 GBP."Delivered codes stay masked in every response unless you ask to reveal them. Action tools do exactly what you ask, the same as the panel, so read back any bulk action before confirming something you cannot easily undo.
npx when your assistant needs it. Nothing is hosted for you.| Symptom | Cause | Action |
|---|---|---|
| No tools listed after setup | The config file path is wrong for your OS, or the JSON is invalid | Check the path and JSON validity, then fully restart the assistant |
| Credentials rejected | The API Key or Secret was copied incorrectly | Re-copy both from Account, Settings, Security exactly; a bad pair can come back as a generic server error |
npx: command not found |
Node.js is not installed, or is older than 18 | Install Node.js 18 or later, then confirm with node --version |
| A tool call returns an error | Varies | Ask the assistant to show the error message; it names the endpoint and the reason |
Submit a claim so Keysender Support can review it.
Three things: a Keysender vendor account, your API key and secret from Account > Settings > API access, and Node.js 18 or later on the machine running your assistant. Not sure Node is installed? Check with node --version before you start.
The server ships all 30 tools the panel relies on, 14 read tools and 16 action tools, scoped to your account. Read tools cover orders, stock, customers, and account activity. Action tools cover uploading stock, creating sales, resending orders, and buying from the supply catalog.
No. Delivered keys and codes are masked to the last 4 characters by default in every tool. Only three read tools, list_stock, get_order_details, and get_supply_order, accept a reveal option when you need the full value. Every other tool always masks.