note-mcp-server

Created By
NaotoCodinga year ago
Note用の簡易的なMCPサーバー
Overview

what is note-mcp-server?

note-mcp-server is a simple MCP server designed to retrieve article content from Note.com based on user IDs.

how to use note-mcp-server?

To use note-mcp-server, clone the repository, install the necessary dependencies, and call the MCP client tools to fetch recent articles from a specified user ID.

key features of note-mcp-server?

  • Access to Note.com articles via unofficial API
  • Web scraping to retrieve article content
  • Ability to fetch recent articles from specific users

use cases of note-mcp-server?

  1. Retrieving the latest articles from a Note.com user for content aggregation.
  2. Summarizing recent articles for quick insights.
  3. Integrating Note.com content into other applications or services.

FAQ from note-mcp-server?

  • Is note-mcp-server officially supported by Note.com?

No, it uses unofficial methods and may stop working if Note.com changes its service.

  • What are the system requirements?

You need Node.js v22.14.0 and npm v10.9.2 to run this project.

  • How do I install note-mcp-server?

Clone the repository and run npm ci to install dependencies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NaotoCoding
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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