manage_display_category — agentView MCP Tool
manage_display_category
(manage display category) is one of 57 tools on the
agentView
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call manage_display_category from your client
- Claude Code agentView manage_display_category run in your project directory
- Claude Desktop agentView manage_display_category ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentView manage_display_category ~/.cursor/mcp.json
- VS Code agentView manage_display_category .vscode/mcp.json
- Zed agentView manage_display_category ~/.config/zed/settings.json
- Windsurf agentView manage_display_category ~/.codeium/windsurf/mcp_config.json
- Cline agentView manage_display_category ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentView manage_display_category ~/.gemini/settings.json
- Grok agentView manage_display_category .mcp.json (in your project root)
- ChatGPT agentView manage_display_category Settings → Connectors → Advanced → Developer mode
- Claude.ai agentView manage_display_category Settings → Connectors → Add custom connector
- LangChain agentView manage_display_category pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentview-mcp https://agentview.de/mcpOther tools on this server
- assign_display_categories
- list_data_slots
- set_display_grant
- authenticate
- create_api_key
- get_data_slot
- get_storage_usage
- broadcast_content
- manage_licenses
- get_public_status
- get_display
- create_auth_session
- list_store_categories
- send_store_template_to_display
- create_display
- delete_data_slot
- get_license_info
- get_organization
- remove_display_from_org
- set_data_slot
- submit_feedback
- upload_asset
- configure_display
- search_public_apis
- claim_display
- send_url
- clear_display
- get_account
- delete_asset
- get_store_template_content
- get_auth_session
- send_html
- delete_display
- logout
- search_store_templates
- search
- pair_by_code
- get_store_template_details
- list_displays
- list_assets
- get_agent_artifact
- configure_organization
- list_api_keys
- read_display_html
- list_organizations
- revoke_api_key
- get_display_preview_url
- delete_organization
- list_display_categories
- update_asset
- create_organization
- get_asset
- fetch
- test_display_content
- get_store_template_install_options
- manage_org_member
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.