Who can connect
Only an admin of your Nickel organization can approve a browser sign-in or create an MCP token. Anyone else who tries to connect sees “You do not have the relevant permissions to connect apps” on the approval screen.Whose permissions apply
A connection acts as the person who approved it, or who created its token. Every tool call runs with that person’s role, the same as if they were using the dashboard. A token created with a role of its own can do only what both that role and its creator’s role allow, so you can give an assistant less than you have. When a role doesn’t allow something, Nickel refuses the call and the assistant tells you why. The tools a client sees also depend on what your organization uses. The Nickel Banking tools appear only when your organization has an active Nickel Banking account.Confirmations
Tools that only read — searching, listing, and fetching a single record — run as soon as the assistant calls them. Every tool that changes your account asks you first. That covers moving money, like paying a bill or issuing a refund, and every other change too: creating or editing a record, sending an invoice by email, and marking an invoice or bill as paid. Before one of these runs, your client shows a confirmation that names the action and lists every value it will send, with amounts in dollars.- Confirm, and the action runs.
- Decline or cancel, and nothing changes. The assistant is told the action was not confirmed. It also gets a link to approve the same action in the Nickel dashboard, for clients that decline without showing you anything. If you declined it yourself, ignore the link.
- No answer within five minutes, and the request times out. Nothing changes, and the assistant gets the dashboard link.
When your client can’t ask you
Confirmations use a part of MCP called elicitation. Some clients don’t support it, and some, such as Cursor’s cloud agents, answer the confirmation themselves without showing it to anyone. For those clients, Nickel asks you in the dashboard instead:- The assistant gives you a link to an approval page in the Nickel dashboard. Nothing has run yet.
- The page lists every value the action will send, with customer, vendor, and file names next to their IDs. Approve or decline it there.
- Tell the assistant to continue. It runs the action once, exactly as you approved it.
Bill approval rules
A confirmation is your approval to submit an action. It doesn’t bypass your organization’s bill approval rules. When a bill payment or a recurring bill matches a rule, Nickel sends it to your approvers instead of paying it, and the assistant reports it as sent for approval. Approvers approve it in the Nickel dashboard; there’s no MCP tool for approving. Your assistant can tell you in advance whether a payment will need approval, and who has to approve it.Where to go next
Tool reference
Every tool, with the ones that ask for confirmation marked.
Connect a client
Browser sign-in and API tokens, and how to disconnect.
