How to go from reading to working — Open Standing MCP Resource

How to go from reading to working is one of 4 resources on the Open Standing MCP server. Connect the server and your client can attach it as context.

by client

How to attach How to go from reading to working from your client

• Claude Code Open Standing Resource/How to go from reading to working run in your project directory
• Claude Desktop Open Standing Resource/How to go from reading to working ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Open Standing Resource/How to go from reading to working ~/.cursor/mcp.json
• VS Code Open Standing Resource/How to go from reading to working .vscode/mcp.json
• Zed Open Standing Resource/How to go from reading to working ~/.config/zed/settings.json
• Windsurf Open Standing Resource/How to go from reading to working ~/.codeium/windsurf/mcp_config.json
• Cline Open Standing Resource/How to go from reading to working ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Open Standing Resource/How to go from reading to working ~/.gemini/settings.json
• Grok Open Standing Resource/How to go from reading to working .mcp.json (in your project root)
• ChatGPT Open Standing Resource/How to go from reading to working Settings → Connectors → Advanced → Developer mode
• Claude.ai Open Standing Resource/How to go from reading to working Settings → Connectors → Add custom connector
• LangChain Open Standing Resource/How to go from reading to working pip install langchain-mcp-adapters

Other resources on this server

• Independent resolver task v1
• Expertise tags
• Open tasks

Open Standing 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 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.