/docs/guides/editor-setup — Proa documentation MCP Resource
/docs/guides/editor-setup
is one of 50 resources on the
Proa documentation
MCP server. Connect the server and your client can attach it as context.
by client
How to attach /docs/guides/editor-setup from your client
- Claude Code Proa documentation Resource//docs/guides/editor-setup run in your project directory
- Claude Desktop Proa documentation Resource//docs/guides/editor-setup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Proa documentation Resource//docs/guides/editor-setup ~/.cursor/mcp.json
- VS Code Proa documentation Resource//docs/guides/editor-setup .vscode/mcp.json
- Zed Proa documentation Resource//docs/guides/editor-setup ~/.config/zed/settings.json
- Windsurf Proa documentation Resource//docs/guides/editor-setup ~/.codeium/windsurf/mcp_config.json
- Cline Proa documentation Resource//docs/guides/editor-setup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Proa documentation Resource//docs/guides/editor-setup ~/.gemini/settings.json
- Grok Proa documentation Resource//docs/guides/editor-setup .mcp.json (in your project root)
- ChatGPT Proa documentation Resource//docs/guides/editor-setup Settings → Connectors → Advanced → Developer mode
- Claude.ai Proa documentation Resource//docs/guides/editor-setup Settings → Connectors → Add custom connector
- LangChain Proa documentation Resource//docs/guides/editor-setup pip install langchain-mcp-adapters
Other resources on this server
- /docs
- /docs/guides/tutorial
- /docs/core/html-rendering
- /docs/core/components
- /docs/core/markdown
- /docs/core/write-buf
- /docs/framework/responses
- /docs/core/streaming-ssr
- /docs/core/sink
- /docs/framework/routing
- /docs/framework/linking
- /docs/framework/route-handlers
- /docs/framework/sitemaps
- /docs/framework/robots
- /docs/framework/content-negotiation
- /docs/framework/page-caching
- /docs/framework/errors
- /docs/framework/metadata
- /docs/framework/data-loading
- /docs/framework/databases
- /docs/framework/caching
- /docs/guides/forms-actions
- /docs/guides/islands
- /docs/rsjs/signals
- /docs/rsjs/shared-state
- /docs/rsjs/handlers
- /docs/rsjs/bindings
- /docs/rsjs/component-props
- /docs/rsjs/client-helpers
- /docs/rsjs/browser-apis
- /docs/rsjs/server-only
- /docs/rsjs/hydration
- /docs/rsjs/queries-mutations
- /docs/rsjs/runtime
- /docs/guides/tailwind-intellisense
- /docs/core/class-composition
- /docs/framework/fonts
- /docs/framework/images
- /docs/framework/static-assets
- /docs/framework/third-party
Read from the server itself, by connecting to it and calling resources/list on 28 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.