MCP-Flomo-Server

Created By
codeugara year ago
Overview

what is MCP-Flomo-Server?

MCP-Flomo-Server is a server application based on the Model Context Protocol (MCP) that allows AI assistants (like Claude) to directly record content into the Flomo note-taking application. This service enables users to easily save valuable information during conversations with AI.

how to use MCP-Flomo-Server?

To use MCP-Flomo-Server, clone the repository, install the dependencies, configure the Flomo API key, and run the server. Once the server is running, AI assistants can call the flomo tool via the MCP protocol to record notes.

key features of MCP-Flomo-Server?

  • Provides MCP tool interface for direct AI assistant calls
  • Sends content to the user's Flomo account via Flomo API
  • Supports environment variable configuration for personalization
  • Developed in TypeScript for type safety

use cases of MCP-Flomo-Server?

  1. Recording notes during AI-assisted conversations
  2. Saving important information from AI interactions directly to Flomo
  3. Enhancing productivity by integrating AI with note-taking

FAQ from MCP-Flomo-Server?

  • How to obtain the Flomo API key?

    Log in to the Flomo web version, find the API option in settings, and create a new API key.

  • Is it normal for the server to have no output after starting?

    Yes, it is normal for the server to wait for MCP client connections without additional console output.

  • How to confirm the server is working properly?

    You can test by sending a note to Flomo through the AI assistant and checking if it appears in your Flomo account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
codeugar
Star
0
Language
TypeScript
License
-
Category
note-taking

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago