Developer documentation — agentView MCP Resource

Developer documentation is one of 15 resources on the agentView MCP server. Connect the server and your client can attach it as context.

by client

How to attach Developer documentation from your client

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

Other resources on this server

• agentView Template Gallery
• agentView Template Detail
• agentView Template Installed
• agentView Display Preview
• agentView Displays
• agentView Screen Connected
• agentView Sign In
• Public status
• Agent instructions
• Premium display design system
• MCP capability status
• OAuth status
• Support diagnostics
• Public API catalog

agentView 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.