FreeAgent + Claude
Connect FreeAgent to Claude
Prepare a grounded billing review briefing
Read invoices with Claude and Agent200. Prepare a billing review briefing using the connected user’s own FreeAgent account.
On this page
Overview
Ask Claude for a focused billing review briefing from one selected invoice. Compare its answer with the retrieved source and separate suggestions from recorded facts.
Start with one identified invoice. Preserve returned invoice, contact, status and amount fields; report missing data and keep the workflow read-only.
Provider reference: FreeAgent API.
- Connector
- FreeAgent
- Works with
- Claude · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- FreeAgent enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a FreeAgent account. They approve access once, on FreeAgent's own page.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect FreeAgent to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers FreeAgent and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
-
6
Step 6: Connect your FreeAgent account
The first time you ask Claude for something in FreeAgent, Agent200 returns an authorization link. Open it and approve access on FreeAgent's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read the FreeAgent invoice I identify and prepare a billing review briefing. Name the source and use only invoice, contact, status and amount fields. State access gaps; do not change records.
What should come back
- The selected invoice is identified.
- Only the returned invoice, contact, status and amount fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected invoice ID, account scope, read permission and pagination. Sandbox records are test data. Do not present a sandbox result as production revenue or an invoice status as a bank reconciliation.
Get your API key
Create a key in the Agent200 dashboard. It reaches FreeAgent and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect FreeAgent to Claude.
Goal: connect FreeAgent to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/freeagent/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure FreeAgent is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. The first FreeAgent request returns an authorization link if the user has not connected FreeAgent yet: show it to them and continue once they have approved access on FreeAgent's own page. 5. Check it works with this request: "Read the FreeAgent invoice I identify and prepare a billing review briefing. Name the source and use only invoice, contact, status and amount fields. State access gaps; do not change records." What should come back: - The selected invoice is identified. - Only the returned invoice, contact, status and amount fields are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in FreeAgent, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/freeagent/framework/claude.md
FreeAgent tools Claude can call
-
List invoices
Readfreeagent_list_invoicesFind invoices in the authorized FreeAgent account.
-
Read an invoice
Readfreeagent_get_invoiceRetrieve one invoice by its resource URL.
-
List contacts
Readfreeagent_list_contactsFind available contact records.
-
Read a contact
Readfreeagent_get_contactRetrieve one identified contact.
-
List expenses
Readfreeagent_list_expensesReview recorded expenses in scope.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in FreeAgent.
-
02
Claude picks a tool
It sees the FreeAgent tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own FreeAgent connection, within the tools and scopes your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's FreeAgent account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and FreeAgent enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected invoice ID, account scope, read permission and pagination. Sandbox records are test data. Do not present a sandbox result as production revenue or an invoice status as a bank reconciliation.
FAQ
How do I verify this result?
Compare the named invoice and returned invoice, contact, status and amount fields with the source. Treat missing information as missing, not as a fact.
