DuetFlow has an optional built-in MCP server. MCP lets a compatible AI client use the tasks you allow through DuetFlow’s existing rules. Your private and shared work keeps the same permissions, dependencies and recurrence behavior.
The connection runs inside the existing Mac app. You do not need a separate helper, terminal runtime, hosting account or external sign-in provider.
DuetFlow is not publicly available yet. Join early access for private-beta and launch updates. These instructions apply to Mac builds with AI Integration in Settings.
Connect your desktop client
- Open DuetFlow → Settings → AI Integration. Choose the acting member and permissions. Select the household when allowing household access.
- Turn on Enable Local MCP and wait for Ready.
- In the Codex desktop client, open Settings → Plugins → Add → Add MCP Server. Choose Streamable HTTP and enter the MCP URL copied from DuetFlow.
- Add an Authorization header. Its value is
Bearerfollowed by the access key copied from DuetFlow, with one space between them. Leave the bearer-token environment-variable field empty when using this header. - Save the connection, start a fresh chat and ask it to check your DuetFlow connection.
Paste the access key only into your trusted client’s connection settings. Keep the key and copied configuration private; never paste either into a chat or support message.
Use a configuration file or another MCP client
For Codex, choose Copy Codex Configuration in DuetFlow and add the section to ~/.codex/config.toml. Replace an existing DuetFlow section instead of adding a duplicate, then reconnect and start a fresh chat. A project-local configuration requires a recognized, trusted project; it is not a universal setup for projectless chats.
Other clients must support local Streamable HTTP and a custom Authorization: Bearer header. Copy the URL and access key from DuetFlow into that client’s connection settings.
Choose what the assistant can access
Private and household read/write permissions are independent. Attachment transfers and administration have their own permissions. Consequential actions open an exact preview in DuetFlow, where you approve the changes. The assistant cannot give that approval for you.
Try a useful request
- “Capture ‘Call the garage’ in my private Inbox.”
- “Review my open projects and identify any that have no next action.”
- “Erfasse ‘Werkstatt anrufen’ in meiner privaten Inbox.”
The server provides Getting Things Done context, keeps defer, planned and due dates distinct, and uses DuetFlow’s existing assignment, inheritance and recurrence rules.
Compatibility and availability
Keep your Mac awake and DuetFlow running. Quitting DuetFlow stops the server. Ordinary hosted ChatGPT web and iPhone chats cannot connect directly to this Mac-local endpoint. A desktop client must actually support local HTTP MCP; installing a desktop chat app alone does not establish that support. STDIO-only clients need an adapter and are not supported by this direct connection.
This is a local integration, with no official public ChatGPT plugin or directory listing. Client/account policies may restrict MCP access. Read get_profile and connection_status to check the bound member, grants and connection.
If the tools are missing, or you changed the server URL, start a fresh chat. In our desktop test, existing chats kept their previous tools or address after settings changed. The normal DuetFlow app retains its configured port.
Stop access or change the key
Turn off Enable Local MCP to stop access immediately. Disable before changing the member, household or permissions. Regenerate Access Key invalidates the old key; copy the new details and reconnect your client. If the port is occupied, disable access, select a free port under Advanced, then update the client URL after enabling again.
After a failed reply, check the operation status before retrying. A saved local receipt does not prove iCloud synchronization. Import, backup, restore, sharing and system permissions retain their native safeguards.