Claude is good at thinking and drafting, but it can only work with what you give it. If your clients, projects and tasks live in a system Claude can't reach, you end up pasting in screenshots and exports that are stale by lunchtime.
MCP fixes that. This guide shows you how to connect Claude to your OnFlow workspace so it can read and update your live records, using your own permissions.
The short version: add https://app.onflowapp.com/api/mcp as a remote MCP server in Claude, sign in to OnFlow and approve access. Claude then works with the records your OnFlow role can see, and nothing more.
Who this is for (and who it isn't)
This is for you if you already use Claude for drafts and thinking, you want it working on live clients, projects or tasks, and you're the person who sets tools up for a small team.
It isn't for you if you need a formal compliance programme or a long vendor security review before you can try a tool. Talk to us first. This guide is the hands-on route for a small team that wants Claude working on real records today.
What you need
- An OnFlow workspace. A 30-day free trial is fine.
- Claude Desktop, or any version of Claude that supports remote MCP servers.
- A module with a few records to practise on. Todo works, and so does CRM & sales pipeline.
Step 1: Start with a module and a few records
- In OnFlow, open the module library and create the Todo module (or CRM & sales pipeline).
- Add three to five real tasks. Make one overdue and assign one to yourself.
- Check you can see them on the board and in the table view.
A module gives you a working data model, so Claude has clear fields to read instead of a pile of free text.
Step 2: Connect Claude to OnFlow
OnFlow's MCP server URL is:
https://app.onflowapp.com/api/mcp
Option 1: OAuth (recommended)
- In Claude, add a new remote MCP server and paste in the URL above.
- Claude sends you to OnFlow to sign in. Review the permissions it asks for and click Allow.
- Claude is now connected and scoped to your own OnFlow permissions.
Option 2: API key (for scripts and clients without OAuth)
- In OnFlow, go to Admin > API Keys.
- Create a key and choose which role it should act as.
- Authenticate with the key as a Bearer token in the form
key:secret, against the same URL.
Use OAuth for day-to-day work, so access follows the person who is signed in. Use an API key for scripts, and give it the narrowest role that does the job.
Step 3: Ask Claude about your records
Try one of the Todo module's starter prompts:
List my todos due in the next 7 days that aren't Done or Cancelled. Show Name, due date, and status.
The answer should come from your live records, not from earlier chat. Change a task in OnFlow, ask again, and check the answer changes.
Step 4: Make a change, then check the log
Try a write:
Create a todo from what I describe: chase the signed proposal. Put the detail in the description, set the due date to Friday and leave the status Open.
Then open the record in OnFlow. The new todo should match what you asked for. Open its history to see the change. Every AI read, write and tool call is also logged, so you can review what Claude did, not just what it changed. How long the audit trail is kept depends on your plan: 7 days on Business Starter, one year on Growth and ten years on Scale.
If writes feel too early, stick to questions for your first week and add writes once you trust the setup.
Step 5: Check permissions before you share it
Before teammates connect their own Claude, run through this:
| Check | Why it matters |
|---|---|
| Sign in as a user with a narrower role and ask the same questions. Claude should see less. | Claude acts with that person's permissions, so their role is the limit. |
| Know how to disconnect. | Remove the connection in Claude, or delete the API key under Admin > API Keys. |
| Check the log after a test run. | Every AI read, write and tool call is logged, so you can see what Claude did and when. |
| Keep irreversible actions with a person. | Sending, deleting and paying are worth approving yourself, whoever asks. |
What Claude can and can't do
Through OnFlow's MCP server, Claude can create records, move work through workflows, search your data and trigger automations, with the same permissions as you. It can't see or change anything your role can't.
A few limits to plan for:
- This walkthrough covers Claude. OnFlow's MCP server works with Claude or any MCP-capable client, but follow that client's own steps for adding a remote server.
- Claude is only as useful as your data model. A module with clear fields gives better answers than a free-text dump.
- You stay responsible for what you approve. Treat write access like giving a new hire edit rights.
Next step
Create a module, connect Claude and ask it one real question about your work. Start your 30-day free trial with the Todo or CRM module, or book a 20-minute setup call and we'll do it with you. A payment method is required to start the trial, you won't be charged until it ends, and you can cancel any time.
Want the bigger picture first? Read what AI-native actually means.
OnFlow: built from real problems, for your team and your AI.
FAQ
Do I need to write code to connect Claude to OnFlow?
No. With OAuth you add the server URL in Claude, sign in to OnFlow and click Allow. An API key is only needed for scripts and clients without OAuth support.
Can Claude see all my data?
No. Claude acts with the permissions of the person who connected it, or the role chosen for an API key. It can't see more than that person could.
Does this work with AI tools other than Claude?
OnFlow's MCP server works with Claude or any MCP-capable client. This guide walks through Claude.
Is MCP access an extra cost?
No. Every plan includes MCP and API access. Plans start at $20 per seat per month, billed per seat, with a 30-day free trial. A payment method is required to start the trial.
Is there a record of what Claude does?
Yes. Every AI read, write and tool call is logged, and changes appear in the audit trail. How long the audit trail is kept depends on your plan: 7 days on Business Starter, one year on Growth and ten years on Scale.