What is Dynafis MCP?
MCP exposes selected Dynafis functions as typed tools for compatible AI clients and agents.
Optional developer module
Technical integration
Dynafis MCP for AI clients
Connect ChatGPT, Claude and other MCP-capable clients to Dynafis in a controlled way – with OAuth and a clear boundary around workspace, legal entity and approved functions.
MCP
Where MCP fits
Who is it for?
Developers, integrators and technical teams that want Dynafis functions inside AI-assisted workflows.
When do you not need it?
Normal Dynafis use in the browser requires no MCP setup. Core product functions remain independent.
MCP Tools
What MCP enables
Find invoices and documents
Authorized clients can read documents, invoices and status data inside the approved legal entity.
Query review and monthly close
Open review items and monthly-close status can be used in controlled agent workflows.
Run approved actions
Write tools require separate authorization. Write access is never inferred from read access.
Keep clients isolated
For accounting firms every connection is permanently bound to one client. A tool cannot switch clients on its own.
OAuth + PKCE
OAuth instead of permanently shared API keys
Before approval, the user sees the application, workspace, legal entity/client and requested scopes. Access tokens are short-lived; persistent connections use revocable refresh tokens.
Policy
Dynafis boundaries still apply through MCP
- Roles and permissions
- Plan and module entitlements
- Document, export and AI limits
- MCP rate limits
- Revocation of connected clients
- Workspace and client binding
OAuth flow
Connect in four steps
1
The MCP client discovers Dynafis and starts OAuth.
2
You sign in and choose the workspace and legal entity/client.
3
You review read, write and offline permissions and approve the connection.
4
The client sees only tools actually allowed by role, plan and enabled modules.
Help Center
Help without protocol knowledge
The Help Center explains MCP from a user perspective: connecting a client, MCP vs API, missing visibility and revoking a connection.
Self-service MCP and Partner MCP remain separate
Self-service MCP is for Dynafis users and their AI clients. The service/partner MCP for QuoAPI and other partners remains a separate interface with dedicated tokens, capability allowlists and tenant isolation.
MCP documentation
Connect ChatGPT, Claude and other MCP-capable clients to Dynafis in a controlled way – with OAuth and a clear boundary around workspace, legal entity and approved functions.
MCP documentation →