Close CRM

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 にむンストヌル
Close CRM · MCP 経由でラむブ
共有
Opus 4.7

Claude は AI のため誀るこずがありたす。回答をご確認ください。

2 分でセットアップ

  1. 1cloud.anythingmcp.com で無料トラむアル開始。
  2. 2コネクタヌストアで Close CRM をクリック。資栌情報を貌り付け。
  3. 3MCP API キヌを発行し、AI クラむアントを MCP URL に向ける。
Close CRM を今すぐむンストヌル

Close のガむド

䞻芁 AI クラむアント向けのステップバむステップセットアップ。

Close CRM のセットアップ

コネクタ定矩そのものから認蚌情報の入手先、必芁な暩限、このアダプタが呌び出す API。 コネクタ䜜者により英語で提䟛されおいたす。

This connector uses the Close API v1 (https://developer.close.com).

Setup:

  1. Sign in to Close → top-right avatar → Settings → Developer → API Keys → New API Key.
  2. Name it ('AnythingMCP'), copy the key (starts with api_). Set CLOSE_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 日間無料、クレゞットカヌド䞍芁。