RedNote MCP

Created By
Leoa year ago
A friendly tool to help you access and interact with Xiaohongshu (RedNote) content through Model Context Protocol.
Overview

What is RedNote MCP?

RedNote MCP is a user-friendly tool designed to help users access and interact with Xiaohongshu (RedNote) content through the Model Context Protocol.

How to use RedNote MCP?

To use RedNote MCP, install it via NPM or build it from source. After installation, run rednote-mcp init to log in and set up your account, which saves your login information securely.

Key features of RedNote MCP?

  • Automatic cookie management for seamless login
  • Keyword search through notes
  • Command-line tools for easy interaction
  • URL-based content viewing

Use cases of RedNote MCP?

  1. Accessing and managing Xiaohongshu notes efficiently.
  2. Searching for specific content within notes using keywords.
  3. Integrating with other tools via command-line interface.

FAQ from RedNote MCP?

  • Is RedNote MCP easy to set up?

Yes! Just follow the installation instructions and run the initialization command.

  • Can I use RedNote MCP without logging in?

No, logging in is required to access and manage your notes.

  • What if my login expires?

You can simply run the init command again to log in.

Server Config

{
  "mcpServers": {
    "RedNote MCP": {
      "command": "npx",
      "args": [
        "rednote-mcp",
        "--stdio"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Leo
Star
-
Language
-
License
-
Tags

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