{"id":"computeruseprotocol-computeruseprotocol","name":"computeruseprotocol","homepage":"https://computeruseprotocol.com/","repo_url":"https://github.com/computeruseprotocol/computeruseprotocol","category":"devtools","subcategories":[],"tags":["ai-agents","ui-automation","accessibility","json-schema","mcp","computer-use","protocol","llm-integration"],"what_it_does":"Computer Use Protocol (CUP) defines a cross-platform, LLM-friendly schema for representing desktop UI accessibility trees (JSON envelope and a compact text encoding) and the canonical action vocabulary needed for AI agents to perceive and interact with UI elements. This repo provides the core schema/spec; execution is implemented by SDKs and (optionally) MCP servers in the ecosystem.","use_cases":["Representing native UI accessibility trees in a single cross-platform format for agent reasoning","Capturing UI state for LLM context (using the compact text encoding)","Standardizing agent actions (click/type/toggle/etc.) across Windows/macOS/Linux/web/mobile accessibility layers","Building interoperable SDK adapters that normalize platform-specific accessibility data into CUP"],"not_for":["A complete, turnkey automation system by itself (it is primarily a protocol/spec; runtime capture/action execution lives in SDKs/adapters)","Secure, authenticated remote execution APIs where CUP would be called over the network"],"best_when":"You want consistent UI grounding across platforms for agent workflows, and you can supply or integrate a platform-specific SDK/MCP server for capture and action execution.","avoid_when":"You need a dedicated network service/API with authentication, rate limits, and guaranteed idempotent action semantics out of the box.","alternatives":["Raw accessibility tree formats per platform (e.g., UIA/AXUIElement/AT-SPI) used directly","ARIA-based role/state representations without a compact cross-platform action vocabulary","Other agent UI automation frameworks that define their own internal UI schemas (platform-specific or vendor-specific)"],"af_score":57.8,"security_score":18.0,"reliability_score":26.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:30:04.500465+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":true,"sdk_languages":["Python","TypeScript"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"The package/spec itself does not describe network authentication. Auth concerns would be relevant only for runtime SDKs or MCP servers provided by other components."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"License is MIT; pricing for SDK/MCP hosting is not specified in the provided README content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":57.8,"security_score":18.0,"reliability_score":26.2,"mcp_server_quality":40.0,"documentation_accuracy":80.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":0.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"This repo is primarily a schema/spec (no network endpoints described), so transport security/authn/authz are not applicable from the provided content. Security posture for runtime capture/action execution depends on downstream SDKs/MCP servers. Since dependency/package hygiene is not provided in the snippet, dependency hygiene is estimated rather than verified.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":60.0,"error_recovery":10.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["The spec defines schema and actions, but action execution details (timeouts, failures, retry behavior) depend on the specific SDK/MCP adapter implementation.","UI trees can be dynamic; agents may need to re-capture/refresh the UI state between actions to avoid acting on stale nodes.","Compact encoding/tokenization can be optimized for LLM context; agents must rely on the documented format spec to parse it correctly."]}}