Close MCP integration for AI agents.
Connect AI agents to Close through 16 structured actions, including get contact, create contact, and create lead. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 16
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Close integration exposes
The Close Agent App exposes 16 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent fetch a single close contact by id, create a close contact under a specific lead, and create a close lead with optional nested contacts and addresses. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Close account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Close capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADFetch a single Close contact by ID.
INPUTS: contactId / includeFields
create_contactWRITECreate a Close contact under a specific lead.
INPUTS: leadId / name / title / emails / phones
create_leadWRITECreate a Close lead with optional nested contacts and addresses.
INPUTS: name / description / statusId / url / addresses
create_opportunityWRITECreate a Close opportunity for an existing lead.
INPUTS: leadId / contactId / userId / statusId / confidence
create_taskWRITECreate a lead-scoped Close task.
INPUTS: leadId / text / assignedTo / date / dueDate
get_leadREADFetch a single Close lead by ID.
INPUTS: leadId / includeFields
get_opportunityREADFetch a single Close opportunity by ID.
INPUTS: opportunityId / includeFields
get_taskREADFetch a single Close task by ID.
INPUTS: taskId / includeFields
list_contactsREADList Close contacts with optional lead filtering and pagination.
INPUTS: limit / skip / includeFields / leadId
list_leadsREADList Close leads with optional pagination and field selection.
INPUTS: limit / skip / includeFields
list_opportunitiesREADList Close opportunities with stable workflow filters and pagination.
INPUTS: limit / skip / includeFields / leadId / userId
list_tasksREADList Close tasks with lead, assignee, completion, and view filters.
INPUTS: limit / skip / includeFields / leadId / assignedTo
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
contactIdREQUIRED- The Close contact ID.
includeFieldsOPTIONAL- Additional Close API fields to request through the _fields query parameter.
create_contact
leadIdREQUIRED- The Close lead ID that owns the contact.
nameREQUIRED- The Close contact name.
titleOPTIONAL- The Close contact title.
emailsOPTIONAL- Contact emails.
phonesOPTIONAL- Contact phones.
create_lead
nameREQUIRED- The Close lead name.
descriptionOPTIONAL- The Close lead description.
statusIdOPTIONAL- The Close lead status ID.
urlOPTIONAL- The lead website URL.
addressesOPTIONAL- Lead addresses.
create_opportunity
leadIdREQUIRED- The Close lead ID that owns the opportunity.
contactIdOPTIONAL- The Close contact ID linked to the opportunity.
userIdOPTIONAL- The Close user ID that owns the opportunity.
statusIdOPTIONAL- The Close opportunity status ID.
confidenceOPTIONAL- The Close opportunity confidence percentage.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Fetch a single Close contact by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactControl Create Contact
Create a Close contact under a specific lead. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Lead
Fetch a single Close lead by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_leadSAFETY BOUNDARY
Operate Close with explicit limits
- Authorize Close with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Close rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Close task completed successfully.
CONNECTION MODEL
API key
Close API key used as the HTTP Basic Auth username with an empty password. Create it in Settings > Developer > API Keys: https://developer.close.com/api/overview/api-key-authentication.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Close.