AI and automations · Connect AI and tools

API, MCP & automations

Choose a connection for agents, scripts and workflows, and understand access and limits.

Free and Pro 4 min read Updated November 2026 View Markdown For agents

Give your agent access to Figa, then use your expenses in the conversation or workflow where you need them. Read and organize records, keep recurring bills current, and return to the same data in the app.

Choose your connection

  • MCP for agents. Add the Figa server URL in a compatible client, sign in, select workspaces and choose read-only or read & write access. Connect through MCP.
  • REST API for workflows. Create a workspace key in Workspace settings → API & MCP. Store it in your tool’s credentials and send it as x-api-key. Read the API reference.
  • Skills for repeatable work. Give your agent portable instructions for reading expenses, organizing categories and tags, and matching invoices to recurring bills. Download agent skills.

From a monthly invoice to a useful answer

Your electricity invoice arrives. Your agent extracts the amount and billing period, finds the matching recurring bill, and confirms its actual amount with your authorization. Later, ask “Which bills are still unpaid?” or “How did utilities change this month?” Figa supplies the current records for the answer.

Follow the recurring invoice example →

One set of expense records
The app, API and MCP work with the same workspace data and business rules. Each connection exposes its supported operations; account administration and attachment transfer are not MCP tools. Your external tool handles email, PDF extraction and scheduling. Marking Paid in Figa does not transfer money.

Access and limits

Only workspace owners and admins can create keys or connect MCP. Start with read-only access for analysis; allow writes for changes you intend the agent or workflow to make. Approval behavior belongs to your client or workflow, so configure it before unattended updates.

API keys and MCP workspace connections share one pool: Free: 1 per organization; Pro: 10 per workspace; Enterprise: unlimited. An MCP connection to several workspaces uses one slot in each. Free exposes the oldest 20 expenses per month across the organization; summaries reflect the accessible data. Disconnect unused MCP connections or revoke unused keys in workspace settings.

Setup guides

  • MCP: OAuth setup, tools and interactive expense views.
  • Agent skills: common instructions for different agent runtimes.
  • OpenClaw: skill installation and connection choices.
  • n8n and Zapier: HTTP workflows; use the same API contract with Make or your own code.
  • Insights API: summaries, comparisons and recorded future commitments.
Was this helpful?