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 ã«ã€ã³ã¹ããŒã«ããŸãã
Close ã Cloud ã«ã€ã³ã¹ããŒã«Claude 㯠AI ã®ãã誀ãããšããããŸããåçãã確èªãã ããã
2 åã§ã»ããã¢ãã
- 1cloud.anythingmcp.com ã§ç¡æãã©ã€ã¢ã«éå§ã
- 2ã³ãã¯ã¿ãŒã¹ãã¢ã§ Close CRM ãã¯ãªãã¯ãè³æ Œæ å ±ã貌ãä»ãã
- 3MCP API ããŒãçºè¡ããAI ã¯ã©ã€ã¢ã³ãã MCP URL ã«åããã
Close ã®ã¬ã€ã
äž»èŠ AI ã¯ã©ã€ã¢ã³ãåãã®ã¹ããããã€ã¹ãããã»ããã¢ããã
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.
ããªãã® AI 㯠Close CRM ãã 2 ã¯ãªãã¯å ã
ã³ãã¯ã¿ãŒãã€ã³ã¹ããŒã«ãè³æ Œæ å ±ã貌ãä»ããAI ã«è³ªåã7 æ¥éç¡æãã¯ã¬ãžããã«ãŒãäžèŠã