pair_by_code — agentView MCP Tool
pair_by_code
(pair by code) 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 pair_by_code from your client
- Claude Code agentView pair_by_code run in your project directory
- Claude Desktop agentView pair_by_code ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentView pair_by_code ~/.cursor/mcp.json
- VS Code agentView pair_by_code .vscode/mcp.json
- Zed agentView pair_by_code ~/.config/zed/settings.json
- Windsurf agentView pair_by_code ~/.codeium/windsurf/mcp_config.json
- Cline agentView pair_by_code ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentView pair_by_code ~/.gemini/settings.json
- Grok agentView pair_by_code .mcp.json (in your project root)
- ChatGPT agentView pair_by_code Settings → Connectors → Advanced → Developer mode
- Claude.ai agentView pair_by_code Settings → Connectors → Add custom connector
- LangChain agentView pair_by_code 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
- 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
- manage_display_category
- 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.