PipRail MCP Server

What this does

PipRail exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

PIPRAIL_PRIVATE_KEY
PIPRAIL_CHAIN
PIPRAIL_CHAINS
PIPRAIL_MAX_AMOUNT
PIPRAIL_MAX_TOTAL
PIPRAIL_MAX_TOTAL_DENOM
PIPRAIL_MAX_PAYMENTS
PIPRAIL_MAX_PAYMENTS_PER_WINDOW
PIPRAIL_WARN_AT_FRACTION
PIPRAIL_SPEND_LOG
PIPRAIL_EVENT_LOG
PIPRAIL_TOKENS
PIPRAIL_SCHEMES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install PipRail?

Run the Claude Code command in the install section to add PipRail to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with PipRail?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to PipRail as well.

Does PipRail need an API key?

Yes. Before it can run, set these environment variables: PIPRAIL_PRIVATE_KEY, PIPRAIL_CHAIN, PIPRAIL_CHAINS, PIPRAIL_MAX_AMOUNT, PIPRAIL_MAX_TOTAL, PIPRAIL_MAX_TOTAL_DENOM, PIPRAIL_MAX_PAYMENTS, PIPRAIL_MAX_PAYMENTS_PER_WINDOW, PIPRAIL_WARN_AT_FRACTION, PIPRAIL_SPEND_LOG, PIPRAIL_EVENT_LOG, PIPRAIL_TOKENS, PIPRAIL_SCHEMES. They go in the env block of your MCP config.