MCP server

The Dash.fi MCP server lets you connect your AI assistant to your Dash.fi account so you can ask questions about your data in plain language — “what bills are due this week?”, “show my pending approvals”, “how much did Marketing spend last month?” The connection is read-only. Your assistant can look things up and report on them, but it cannot create cards, approve requests, pay bills, or move money.

​

What you can ask about

​

Tools the server exposes

Thirteen read-only tools. Your assistant picks the right one for the question — you don’t call these by name — but administrators reviewing the server can see the full surface here. Every tool is annotated read-only, so compliant clients won’t show “this tool can modify your data” warnings. Each one is gated on its own permission scope — a call your role doesn’t cover is rejected rather than answered.

​

What it can’t do

• Read-only — the assistant cannot create a card, approve a request, pay a bill, or move money
• Can’t filter transactions by date range (planned)
• Can’t narrow the approvals queue to only those waiting on you specifically (planned)

​

Permissions

The assistant signs in as you and inherits your exact Dash.fi permissions — it gives no extra access. If you can’t see something in Dash.fi, the assistant can’t either.

​

Connect your assistant

Connector URL: https://mcp.dash.fi/mcp Add Dash.fi as a connector in your AI assistant, then sign in with your Dash.fi account when prompted. You only need to approve it once — you can disconnect at any time from the same settings screen. Verify it’s working. Ask your assistant “Who am I?” or “List my cards” — a sensible answer confirms the connection.

​

Security

• You sign in with your own Dash.fi login — no separate password, no extra access granted
• You only ever see your own company’s data
• Full card numbers and vendor bank account details are never exposed to the assistant
• Every request is logged for audit
• The connection is read-only

​

How sign-in works

Sign-in uses the OAuth authorization code flow with PKCE. Your assistant redirects you to Dash.fi, you approve the connection once, and the assistant receives a token — your password never reaches the MCP server, and the server never stores credentials of any kind.

• Short-lived access tokens. An access token is valid for 60 minutes, after which your assistant obtains a fresh one. A leaked token stops working within the hour.
• Tokens are validated at the edge. Signature, audience, and expiry are checked before a request reaches the server at all, so an expired or forged token never touches your data.
• Scoped tokens. A token carries only the permission scopes your role holds. Any call beyond them is rejected for insufficient scope, and each tool re-checks its own scope on every call.
• Client registration is dynamic. Assistants register themselves at connection time, so there’s no shared secret for you to distribute or rotate.

​

Audit logging

Every tool call is recorded, and so is every rejected attempt — an expired token, a missing scope, or a request made while MCP is switched off. Each record captures who called, which tool, when, the outcome, and how long it took.

• Outputs are never stored. The log keeps the size of the response, not its contents.
• Inputs are reduced to an allow-list. Only a named set of fields per tool is retained, so free-text arguments don’t land in the log.
• Records are append-only — they can’t be edited or deleted after the fact.

Logs are held by Dash.fi. Contact support@dash.fi if you need MCP activity for your organisation as part of a security review or audit.

​

Turning it off for everyone

An administrator can revoke MCP for the whole organisation at any time under Company → Products. This takes effect immediately: every subsequent request from every connected assistant is rejected, regardless of tokens already issued, and each rejection is recorded in the audit log. Re-enabling restores access without anyone having to re-approve the connection. Changing a person’s role is the narrower lever — it shrinks what their assistant can read on their next reconnect. Removing them from Dash.fi ends their access outright.

​

Troubleshooting