小红书热门笔记 history — TrendHub MCP Resource
小红书热门笔记 history
is one of 207 resources on the
TrendHub
MCP server. Connect the server and your client can attach it as context.
by client
How to attach 小红书热门笔记 history from your client
- Claude Code TrendHub Resource/小红书热门笔记 history run in your project directory
- Claude Desktop TrendHub Resource/小红书热门笔记 history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TrendHub Resource/小红书热门笔记 history ~/.cursor/mcp.json
- VS Code TrendHub Resource/小红书热门笔记 history .vscode/mcp.json
- Zed TrendHub Resource/小红书热门笔记 history ~/.config/zed/settings.json
- Windsurf TrendHub Resource/小红书热门笔记 history ~/.codeium/windsurf/mcp_config.json
- Cline TrendHub Resource/小红书热门笔记 history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TrendHub Resource/小红书热门笔记 history ~/.gemini/settings.json
- Grok TrendHub Resource/小红书热门笔记 history .mcp.json (in your project root)
- ChatGPT TrendHub Resource/小红书热门笔记 history Settings → Connectors → Advanced → Developer mode
- Claude.ai TrendHub Resource/小红书热门笔记 history Settings → Connectors → Add custom connector
- LangChain TrendHub Resource/小红书热门笔记 history pip install langchain-mcp-adapters
Other resources on this server
- content-studio
- methodology
- sources
- capabilities
- source-health
- namespace
- evidence-contract
- skill-contract
- 小红书热搜词榜 history
- 微博热搜 history
- 知乎热榜 history
- 百度热搜 history
- 贴吧热议 history
- 虎扑步行街 history
- B站热门 history
- 抖音热点 history
- 快手热点 history
- 今日头条 history
- 澎湃新闻 history
- 腾讯新闻 history
- 网易新闻 history
- 新浪新闻 history
- 36氪 history
- IT之家 history
- 虎嗅 history
- 少数派 history
- 爱范儿 history
- 稀土掘金 history
- CSDN history
- 51CTO history
- V2EX history
- HelloGitHub history
- 酷安 history
- 微信读书飙升 history
- 历史上的今天 history
- Hacker News history
- GitHub Trending history
- Product Hunt history
- Reddit r/technology history
- Reddit r/programming history
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.