How Spaces helps
ERP APIs and MCP servers make the data reachable, but finance agents still take a build. Spaces ships ready-made finance connectors with MCP access that follow your permissions.
Still manual today Building finance-specific agents on raw APIs still takes developer or partner effort.
Example Asked in Claude why group opex rose 10% in October, the agent answers from GL balances, the #close Slack thread and a Jira ticket, with each source cited and read-only access.
Connections · finance workspace
- ERP Connected, integration user Done
- Slack 5 finance channels enabled Done
- Gmail AP and AR inboxes enabled Done
- Google Drive Contracts folder pending approval For approval
- Jira Scope broader than requested Needs review
Access follows your existing permissions
What the agent does
- Ready-made connectors for your ERP, Slack, Gmail, Drive, Notion and Jira
- Uses your ERP's APIs and MCP within existing security roles
- Exposes finance context and agents through MCP to approved AI tools
- Logs every read and proposed write for audit
How it runs
- 01 Authorize IT grants scoped access using your ERP security and app permissions.
- 02 Connect tools Finance enables the Slack, Gmail, Drive, Notion and Jira sources it needs.
- 03 Use via MCP Approved assistants such as Claude and ChatGPT query finance context and agents.
- 04 Govern Writes to your ERP need approval. Access is logged and reviewable.
No custom build
Finance agents work through ready-made connectors.
Respects your security
Access follows existing ERP permissions.
Open by standard
MCP lets approved tools use the same finance context.
- Can agents write to our ERP without approval?
- No. Writes need maker-checker approval and follow your ERP's processes and security.
- Do we need developers to set this up?
- Setup is mainly granting access and choosing sources, coordinated with your ERP admin.
