Flomo Mcp

io.github.plidezusPublished by GitHub account plidezusv1.0.0Updated Oct 24, 2026

Connect AI to your flomo notes. Search, create, edit notes and manage tags via MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search, create, and edit flomo notes and manage tags through the hosted flomo MCP endpoint.

What you can do
This server connects an AI assistant to a flomo account so it can work with notes and tags. According to its description, it supports searching notes, creating new notes, editing existing notes, and managing tags. It is a remote streamable HTTP endpoint hosted at flomoapp.com, so no local package is installed.
When to use it
Worth adding when you keep notes in flomo and want an assistant to find, write, or reorganize them without switching apps. Useful for capturing quick notes from a conversation or for tag cleanup across an existing note collection.
Requirements
A remote MCP connection to the flomo endpoint at flomoapp.com. The manifest declares no authentication, environment variables, or headers, but a flomo account is implied by the note and tag operations; expect the service to require its own sign-in or authorization before it can read or change your notes.
Before you install
The server can create and edit notes and change tags, so assistant actions modify your flomo data. The manifest declares no authentication details, so confirm how the endpoint authorizes access and whether note content leaves your account to a third party before connecting.

Installation

In SourceWeft

  1. Open Flomo Mcp 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.plidezus%2Fflomo-mcp/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": {
    "flomo": {
      "type": "http",
      "url": "https://flomoapp.com/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.0.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.