Flow Productivity

io.github.geraldho81Published by GitHub account geraldho81v1.1.0Updated Oct 27, 2026

Notes, kanban tasks, and a capture inbox: read and create Flow data with a personal token.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for Flow Productivity that lets an assistant read and create notes, kanban tasks and inbox captures in a Flow account.

What you can do
  • Read and create notes in a Flow account
  • Read and create kanban tasks
  • Add items to a capture inbox
  • Access is scoped to the user's own Flow workspace via a personal token
When to use it
Useful when you keep notes, kanban boards or an inbox in Flow Productivity and want an assistant to look things up or add new items without switching apps. It is a narrow fit if you use a different notes or task tool.
Requirements
A remote MCP endpoint over streamable HTTP; no local package or runtime. A Flow Productivity account and a personal token generated on the Flow account page, sent as an Authorization header in the form of a bearer token. OAuth is declared as required.
Before you install
The Authorization header carries a personal Flow token that grants access to your account data; treat it as a secret and revoke it if exposed. The assistant can create notes, tasks and inbox items, which writes data into your workspace. Content you ask about is sent to the Flow service.

Installation

In SourceWeft

  1. Open Flow Productivity in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.geraldho81%2Fflow-productivity/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "flow-productivity": {
      "type": "http",
      "url": "https://neighborly-stoat-529.eu-west-1.convex.site/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.