That is the whole appeal — asking for a link and getting one back is faster than the dashboard when you are already mid-conversation with a customer — and it is also the thing to be deliberate about, since the key secret in your config signs live requests. Reading back the links and their transactions in the same session is what makes it more than a link generator: you can send one and check whether it was paid without switching tools.
A Paytm merchant server for the payment-link workflow: generate a link to send a customer, see every link you have created, and check what has been paid against a specific one. It signs requests with your merchant credentials, so it acts as your merchant account rather than as a viewer.
- Create a Paytm payment link for a customer
- Fetch every payment link you have created
- Retrieve the transactions recorded against a specific payment link
Python 3.12 or higher, `uv`, and Paytm merchant credentials — `PAYTM_MID` and `PAYTM_KEY_SECRET`, held in a `.env` file or the client's env block. Install with `uv venv` and `uv pip install .` (package `payment-mcp`, version 0.1.0), or run the supplied `setup.sh`, which checks the prerequisites, creates the environment and writes the `.env` template. The server is launched by your MCP client rather than by hand.
One command plus a key — uv path --directory path to project run paytm_mcp.py, then supply credentials
