Skip to main content
The Nickel MCP server lets an AI assistant work in your Nickel account. MCP (Model Context Protocol) is an open standard that AI clients such as Claude, Cursor, and Codex use to call tools outside the chat. Connect one to Nickel and you can ask it which invoices are overdue, have it add a vendor and pay their bill, or apply a check deposit to the invoice it pays — it calls Nickel for you and answers from your live data. The REST API is for code you write and run on a schedule. The MCP server is for a person working with an assistant: the assistant decides which tools to call, and you approve anything that changes your account before it happens. The MCP server is available on every Nickel plan.

​
What you can do

Get paid

Create, send, and track invoices and recurring invoices. Manage customers, charge saved payment methods, record payments made outside Nickel, and issue refunds.

Pay bills

Add vendors and their payment details, create bills, and pay them by ACH, check, or international wire. Set up recurring bills and bill approval policies.

Track payments

Search incoming and outgoing payment activity and check where any payment stands.

Nickel Banking

See your accounts and cards, deposit a check from photos, and apply check deposits to invoices.

Import from spreadsheets

Bring in vendors, customers, bills, or invoices from a CSV or Excel file.

QuickBooks

Check your sync status and look up QuickBooks accounts and items while creating bills and invoices.
The tool reference lists every tool.

​
How it works

You add the server to your client and sign in to Nickel in your browser. An admin of your organization approves the connection, and from then on the assistant acts as the person who approved it: it can see and do what that person can in the dashboard, and nothing more. Looking something up runs right away. Anything that changes your account — sending an invoice, paying a bill, deleting a vendor — first shows you the exact action and asks you to confirm. Your bill approval policies still apply on top of that. Permissions and confirmations covers the details.

​
Server URL

The sandbox is a separate environment with its own accounts, where no real money moves. Sign in with your sandbox account to try the server before you connect it to production.

​
Where to go next

Connect a client

Add the server to Claude, Claude Code, Codex, or any MCP client.

Permissions and confirmations

Who can connect, whose permissions apply, and what asks before it runs.

Tool reference

Every tool the server offers, grouped by what it works on.