Rebuilding the tools at launch from Adfin's current documentation means the server does not go stale between versions — a new endpoint is there the next time you start your client. The trade is that first start costs 10-20 seconds and needs network access. The bulk-upload workflow is the one worth setting up deliberately: it wants a filesystem server alongside this one, which is why the sample config declares both.
Adfin's server for its invoicing and payments platform. It exposes Adfin's API to an assistant, and refreshes the tool set from Adfin's current API documentation each time the client launches.
- Credit control status on demand — ask for the check and read it back
- Invoice creation from a sentence: amount, currency, customer name, due date and email
- Bulk upload of existing PDF invoices from a local folder, when paired with a filesystem server
- The available tools are rebuilt at launch from the most recent Adfin API documentation, so a new endpoint appears without you updating anything
Python 3.10 or higher and uv. Add it to your client with `uv --directory <path to the adfin mcp folder> run main_adfin_mcp.py`, with ADFIN_EMAIL and ADFIN_PASSWORD in the environment. The first launch takes 10-20 seconds while packages install and the current API documentation downloads.
One command plus a key — uvx adfinmcp, then supply credentials