agentView Displays — agentView MCP Resource
agentView Displays
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 agentView Displays from your client
- Claude Code agentView Resource/agentView Displays run in your project directory
- Claude Desktop agentView Resource/agentView Displays ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentView Resource/agentView Displays ~/.cursor/mcp.json
- VS Code agentView Resource/agentView Displays .vscode/mcp.json
- Zed agentView Resource/agentView Displays ~/.config/zed/settings.json
- Windsurf agentView Resource/agentView Displays ~/.codeium/windsurf/mcp_config.json
- Cline agentView Resource/agentView Displays ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentView Resource/agentView Displays ~/.gemini/settings.json
- Grok agentView Resource/agentView Displays .mcp.json (in your project root)
- ChatGPT agentView Resource/agentView Displays Settings → Connectors → Advanced → Developer mode
- Claude.ai agentView Resource/agentView Displays Settings → Connectors → Add custom connector
- LangChain agentView Resource/agentView Displays pip install langchain-mcp-adapters
Other resources on this server
- agentView Template Gallery
- agentView Template Detail
- agentView Template Installed
- agentView Display Preview
- agentView Screen Connected
- agentView Sign In
- Public status
- Agent instructions
- Premium display design system
- Developer documentation
- 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.