Close is a CRM platform designed for sales teams to manage leads, deals, and customer relationships with built-in calling and messaging capabilities. It provides APIs and webhooks for programmatic access to customer data and sales workflows.
13 of 33 checks passed. 14 unscored.
Can an agent find and understand this tool without a web search?
Can an agent create an account and get credentials without human intervention?
Can an agent operate autonomously without upfront payment or contracts?
How well does the API work for non-human consumers?
Does the tool fail gracefully when an agent makes a mistake?
Close has a solid REST API with OpenAPI documentation and a free tier, making it moderately agent-accessible. However, there is no MCP server or llms.txt file for discovery, and account creation requires manual signup through a web form—agents cannot self-register. The API is well-structured with good error handling and webhook support, but the lack of automated onboarding and missing modern agent discovery mechanisms (MCP, llms.txt) limit its agent-native capabilities. Strongest asset is the straightforward API key authentication and reliable infrastructure; biggest weakness is the absence of automated account provisioning.
Install the Agent Native Registry MCP server. Your agents can search, compare, and score tools mid-task.
claude mcp add --transport http agent-native-registry https://agentnativeregistry.com/api/mcp