Available

Close MCP server

Close is a sales CRM built around calling and email automation, helping small sales teams manage leads and pipeline without heavy setup. Connect through Arc0 to use the actions your identity is allowed to call.

CRMAPI keyMCP + RESTclose.com
AUDIT LOG · CLOSEPOLICY: acme-support
09:41:07 · claude · u_8f2read
close.list_leads
List leads✓ allowed · 212ms
09:41:08 · claude · u_8f2read
close.get_lead
Get lead✓ allowed · 164ms
09:41:09 · claude · u_8f2write
close.create_lead
Create lead✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
close.delete_lead
Delete lead✕ blocked · policy: deny
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Close.

01

List statuses

Use when resolving a lead or opportunity status ID by label before a write. Returns at most 1,000 statuses; larger responses fail validation. Opportunity type is active/won/lost; pipeline ID is optional. Choose the correct pipeline.

02

List leads

Use when you need a bounded page of CRM leads. Advance _skip by _limit only while has_more is true. Use get_lead for an exact record; this is not a bulk export.

03

Get lead

Use when you need one lead by its exact ID, including after a write to check its outcome.

02 · ACTIONS

11 Close actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

7

Look things up, subject to your permissions.

  • close.list_statuses
    List statuses

    Use when resolving a lead or opportunity status ID by label before a write. Returns at most 1,000 statuses; larger responses fail validation. Opportunity type is active/won/lost; pipeline ID is optional. Choose the correct pipeline.

  • close.list_leads
    List leads

    Use when you need a bounded page of CRM leads. Advance _skip by _limit only while has_more is true. Use get_lead for an exact record; this is not a bulk export.

  • close.get_lead
    Get lead

    Use when you need one lead by its exact ID, including after a write to check its outcome.

  • close.get_contact
    Get contact

    Use when you need one contact by its exact ID. Returns only structural contact IDs, without personal details.

  • close.get_opportunity
    Get opportunity

    Use when you need one opportunity by its exact ID, including after a write to check its outcome.

  • close.list_contacts
    List contacts

    Use when you need contact IDs belonging to one specific lead. Returns structural fields only. Follow has_more for pagination; do not use for finding people across the organization.

  • close.list_opportunities
    List opportunities

    Use when you need a bounded page of deals for one lead. total_results counts all matches, not this page. Advance _skip by _limit only while has_more is true.

write

3

Create and change things. Allow, or ask the user first.

  • close.create_lead
    Create lead

    Use when you have approval to add a new CRM lead. Existing CRM automations may react. After an uncertain result, inspect Close before retrying to avoid duplicate leads.

  • close.create_note
    Create note

    Use when adding a plain-text lead note as the user who owns the API key. Visible to the whole Close org in the lead timeline; never include private reasoning. No customer email or SMS is sent; CRM automations may react. Inspect Close before retrying an uncertain write.

  • close.update_opportunity_status
    Update opportunity status

    Use when approved to move a deal to a status from list_statuses. Moving to a won status sets date_won if unset; CRM automations may react. Read back the opportunity after an uncertain response before retrying.

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • close.delete_lead
    Delete lead

    Use when explicitly authorized to delete an exact lead and its related CRM data. Never use for routine archiving or uncertain record matches.

03 · POLICIES AND AUDIT

Control access to Close.

Connect the intended Close account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • close.create_lead: require approval
  • close.delete_lead: deny

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Close connects.

Connect Close using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Close with your AI client.

Sign in to Arc0 and connect Close in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Close with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Close with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Close with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Close with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Close with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Close with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Close and Arc0, answered.

Q01

Does Close work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use Close with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official Close MCP server?

This is Arc0’s integration page, not a claim of an official Close server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Close for its own current MCP offerings.

Q04

Which Close actions are supported?

11 registry-defined actions: 7 read, 3 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Close need?

Connect Close using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in Close?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does Close through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug Close into your agent.

Close MCP server: 11 actions including list statuses, list leads, get lead. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Close and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Close.