Integration
Fluidwave + Claude MCP: manage your tasks from a chat with Claude
Add Fluidwave as a custom connector in Claude and manage your tasks, lists, schedules, categories and contexts from a conversation. Twenty-three tools over OAuth, with every change showing up in the app in real time.
What syncs
| Data | Direction | Notes |
|---|---|---|
| Tasks | Two-way | Create, update, find, complete, cancel and delete, one at a time or in bulk. Changes made in Claude appear in the app in real time, and Claude reads the current state on every call. |
| Lists and schedules | Two-way | Create, update and delete, and refer to them by name when creating or moving tasks. |
| Categories and contexts | Two-way | Create, update and delete, and tag tasks with them from a conversation. |
| Email, calendar and contacts | One-way | Not exposed through MCP in either direction. The connector is scoped to tasks and their organizers. |
How to set it up
- 1
In Claude, open the connectors settings and choose to add a custom connector.
- 2
Enter https://fluidwave.com/api/mcp as the connector URL and save it.
- 3
When prompted, sign in with your Fluidwave account through OAuth and approve the connection.
- 4
Start a new conversation, enable the Fluidwave connector for it, and ask something like “What is due today?”
- 5
Open Fluidwave in another window and watch tasks Claude creates appear in your list immediately.
Privacy and permissions
The MCP connector runs on Fluidwave’s own server at fluidwave.com/api/mcp and authenticates with OAuth, so you sign in with your Fluidwave account in a browser and never paste a password or API key into Claude. There are no API keys to leak; revoking access is a matter of removing the connector in Claude or signing out of the session.
Claude sees only what a tool call returns: the tasks, lists, schedules, categories and contexts that match what you asked for. The connector exposes no email, calendar or contact data, so nothing from your Gmail, Google Calendar or Google Contacts integrations is reachable through it.
On the Fluidwave side, Anthropic Claude is also the sole model provider for in-app AI features, and your data is never used to train AI models, never sold, and never used for advertising. Deleting your Fluidwave account removes synced data and encrypted tokens.
| Permission | Why it is needed |
|---|---|
| Sign in with Fluidwave (OAuth) | Sign you in with your Fluidwave account through OAuth so tool calls run as you, in your workspace, without an API key. |
| Read tasks and organizers | Find tasks and list your lists, schedules, categories and contexts so Claude can answer questions like “what is due today?” |
| Write tasks and organizers | Create, update, complete, cancel and delete tasks, singly or in bulk, and create, update and delete lists, schedules, categories and contexts. |
Features that matter for this
Claude MCP connector
Connect the app to Claude through the Model Context Protocol and manage tasks from a chat.
Auto-prioritization
The app orders your list for you using tunable criteria such as due dates, quick wins, importance and dependencies.
Natural-language task input
Type a sentence like "Pay rent by noon on the last day of each month, remind me a week ahead" and the date, recurrence, priority and reminder are parsed for you.
What you can do once Claude is connected
The Model Context Protocol is an open standard that lets an AI assistant call tools on an external service. Fluidwave publishes an MCP server at https://fluidwave.com/api/mcp with 23 tools, so once it is added as a custom connector, Claude can act on your tasks the way you would in the app.
In practice that means conversations like these:
- “What is due today?” Claude calls the find tool and lists the tasks, with their due dates and lists.
- “Create three tasks for the launch checklist: draft the announcement, update the pricing page, brief support. Put them in the Marketing list, due Friday.” One bulk create call, and all three appear in Fluidwave.
- “Mark the pricing page task complete and move the brief to next Monday.” Complete and update, in one turn.
- “Make a new context called Deep work and tag anything with High complexity.” Create the context, find the tasks, bulk update.
Because the server is Fluidwave’s own and Claude reads the current state on each call, there is no stale copy to reconcile. Everything Claude changes goes through the same path as the app, so auto-prioritization reorders the list immediately and the changes sync to every device you have open. Compare this to the in-app AI assistant, which has around 110 tools and also handles email, calendar and automations; the MCP connector is the smaller, task-focused set you can reach from wherever you already talk to Claude.
Workflows that work well over MCP
The connector is most useful as a capture and review surface, not as a replacement for the app. A few patterns that work well:
Capture while thinking. You are planning a project in a Claude conversation. Rather than copying the plan into a task manager afterward, ask Claude to create the tasks as it goes, with lists, due dates and contexts. They are in Fluidwave before the conversation ends, and prioritized by the time you open the app.
Daily review from a chat. “Show me what is overdue, then what is due this week grouped by list.” Read tools answer it; then “push everything overdue in the Admin list to Thursday” fixes it in one bulk update.
Tidy organizers. Rename categories, merge two contexts, delete a schedule you no longer use. These are the small maintenance jobs that never get done in a UI and take one sentence here.
Hand off to the app for the rest. Time blocking, email triage and automations live in Fluidwave. Ask Claude to set duration estimates on this week’s tasks, then open the Calendar view and let AI scheduling pack them into free time with Google Calendar.
Fluidwave also offers a public REST API at /api/v1 for tasks, lists, schedules, categories and contexts, using the same OAuth sign-in and with an OpenAPI spec, for people who want to script rather than chat. For a broader look at AI-driven task tools, see best AI task managers.
Limits and what is not supported
What the connector deliberately does not do:
- Tasks and organizers only. The 23 tools cover tasks, lists, schedules, categories and contexts. Email, calendar events, contacts, comments, habits, goals and automations are not exposed through MCP. Use the in-app AI assistant for those.
- Claude as the client. The connector is documented and tested as a custom connector in Claude. It speaks standard MCP over OAuth, but Fluidwave does not currently document setups for other MCP clients.
- No API keys. Authentication is OAuth only. If a tool or script cannot complete a browser sign-in, it cannot connect.
- No outbound events. Fluidwave does not push notifications to Claude or call webhooks when tasks change; Claude reads state when you ask.
- No Zapier or Notion bridges. There is no Zapier integration, Notion sync or browser extension. MCP and the REST API are the programmatic surfaces.
- Platforms. The connector works wherever Claude does, and changes appear in the Fluidwave web app, the macOS desktop app and the iPhone and Android apps. Windows and Linux desktop apps are coming soon.
Everything Claude does through the connector can be undone in the app, since Fluidwave keeps undo and redo for all actions, including AI ones. If a bulk update goes further than you meant, Cmd+Z in Fluidwave brings it back.
Frequently asked questions
Ready to know exactly what to do next?
Tasks, email, calendar and contacts in one place, with AI that works out what to do next. Free forever, no credit card.