Close CRM
Drive Close (sales-team CRM) from any AI agent: leads, contacts, opportunities, activities (calls/emails/SMS/notes), tasks, smart views and custom fields. 16 tools, API-key Basic-auth.
7 天免费 · 无需信用卡 · EU 托管
问 Close 任何事
通过 AnythingMCP 对 Close CRM 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 CloseClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Close CRM。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Close CRM
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector uses the Close API v1 (https://developer.close.com).
Setup:
- Sign in to Close → top-right avatar → Settings → Developer → API Keys → New API Key.
- Name it ('AnythingMCP'), copy the key (starts with
api_). SetCLOSE_API_KEY.
Authentication: HTTP Basic auth with username=API_KEY and password empty. The adapter passes Authorization: Basic base64(API_KEY:). Same as Stripe's auth model.
Lead is the top-level object — a 'lead' in Close is what other CRMs call an 'account' or 'company': it groups multiple contacts (the actual people), opportunities (deal-level pipeline records), and activities (timeline of calls/emails/notes/SMS). When in doubt, the agent should start with close_search_leads (Smart View query) rather than searching contacts directly.
Custom field IDs: like Pipedrive, custom fields have opaque IDs. Discover via close_list_lead_custom_fields / close_list_contact_custom_fields / close_list_opportunity_custom_fields. Reference them in writes via custom.cf_XYZ keys on the resource.
Smart Views (saved searches): Close's central UX is filtered queries. The API exposes them via close_search_leads with a query JSON (the same DSL the UI builds). Easiest: build the view in the UI, copy its Smart View ID, then call close_get_smart_view to inspect — but for ad-hoc queries the query param accepts the JSON directly.
Activities are typed: call, email, sms, note, meeting, task_completed, lead_status_change, opportunity_status_change. Use close_create_note_activity for plain notes; for calls/emails the SaaS expects you to use Close's built-in dialer / email integration, not POST a fake activity (the agent shouldn't fabricate a sent email).
Pagination: cursor-based via _skip + _limit (max 100 per page) plus has_more boolean. Some list endpoints return total counts in meta.
Rate limits: ~80 requests/sec burst per organization. On 429, back off — RateLimit-Reset header is set.
Out of scope here: dialer call recording, email sequences (use Close UI), reports/analytics computation, integrations (Mailchimp/Stripe sync), webhook subscription management.