limits — NameWheel MCP Resource
limits
is one of 3 resources on the
NameWheel
MCP server. Connect the server and your client can attach it as context.
by client
How to attach limits from your client
- Claude Code NameWheel Resource/limits run in your project directory
- Claude Desktop NameWheel Resource/limits ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NameWheel Resource/limits ~/.cursor/mcp.json
- VS Code NameWheel Resource/limits .vscode/mcp.json
- Zed NameWheel Resource/limits ~/.config/zed/settings.json
- Windsurf NameWheel Resource/limits ~/.codeium/windsurf/mcp_config.json
- Cline NameWheel Resource/limits ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NameWheel Resource/limits ~/.gemini/settings.json
- Grok NameWheel Resource/limits .mcp.json (in your project root)
- ChatGPT NameWheel Resource/limits Settings → Connectors → Advanced → Developer mode
- Claude.ai NameWheel Resource/limits Settings → Connectors → Add custom connector
- LangChain NameWheel Resource/limits pip install langchain-mcp-adapters
Other resources on this server
NameWheel also offers 5 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 3 October 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.