Server Status — ReadingRate MCP Resource
Server Status
is one of 4 resources on the
ReadingRate
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Server Status from your client
- Claude Code ReadingRate Resource/Server Status run in your project directory
- Claude Desktop ReadingRate Resource/Server Status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ReadingRate Resource/Server Status ~/.cursor/mcp.json
- VS Code ReadingRate Resource/Server Status .vscode/mcp.json
- Zed ReadingRate Resource/Server Status ~/.config/zed/settings.json
- Windsurf ReadingRate Resource/Server Status ~/.codeium/windsurf/mcp_config.json
- Cline ReadingRate Resource/Server Status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ReadingRate Resource/Server Status ~/.gemini/settings.json
- Grok ReadingRate Resource/Server Status .mcp.json (in your project root)
- ChatGPT ReadingRate Resource/Server Status Settings → Connectors → Advanced → Developer mode
- Claude.ai ReadingRate Resource/Server Status Settings → Connectors → Add custom connector
- LangChain ReadingRate Resource/Server Status pip install langchain-mcp-adapters
Other resources on this server
ReadingRate also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 11 November 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.