Flomo Mcp Server Demo

Created By
SheldonFat8 months ago
Overview

what is Flomo MCP Server?

Flomo MCP Server is a TypeScript-based Model Context Protocol (MCP) server that implements a simple notes system, demonstrating core MCP concepts.

how to use Flomo MCP Server?

To use the Flomo MCP Server, install the dependencies, build the server, and configure it with your application. You can create notes and generate summaries through the provided tools and prompts.

key features of Flomo MCP Server?

  • Resources for managing text notes with URIs and metadata.
  • Tools for creating new notes with required parameters.
  • Prompts for generating summaries of all stored notes.

use cases of Flomo MCP Server?

  1. Creating and managing text notes for personal or team use.
  2. Generating summaries of notes for quick reference.
  3. Integrating with applications that require note-taking capabilities.

FAQ from Flomo MCP Server?

  • What is the purpose of the Flomo MCP Server?

It serves as a simple notes system that implements the Model Context Protocol.

  • How do I install the Flomo MCP Server?

You can install it by running npm install and then build it using npm run build.

  • Can I use it with other applications?

Yes, it can be integrated with applications like Claude Desktop by configuring the server settings.

Server Config

{
  "mcpServers": {
    "flomo-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@panghui8383/flomo-mcp@0.0.5"
      ],
      "env": {
        "FLOMO_API_URL": "https://flomoapp.com/iwh/xxxx/xxxxx/"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
6 months ago
Author Name
SheldonFat
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago