The Close connector.
Leads, opportunities and activity. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Close exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Close defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Close tool
6 tools, named as the agent sees them.
- search_leadsread
Search leads (the company/account record Close is built around). Pass `query` in Close search syntax — a bare string matches name, email, phone and custom fields; `status:"Potential"` or `sort:updated` also work. Returns lead ids ("lead_...") for get_lead, list_opportunities and list_activities.
- get_leadread
Get one lead in full: every contact with their emails and phones, every opportunity, custom fields and addresses. Use after search_leads when you need the whole account, not the summary.
- list_opportunitiesread
List opportunities (deals) with value, status, confidence and expected close date. This is the pipeline/forecast tool — filter by lead_id from search_leads, by user_id from list_users, or by status_type ("active"/"won"/"lost").
- list_activitiesread
List activities (calls, emails, notes, SMS, meetings) newest first. Use to answer "what happened with this account lately" — pass lead_id from search_leads. Bodies are truncated; use get_lead or the Close UI for full email text.
- list_contactsread
List contacts (people) with their emails, phones and title. Each contact carries the lead_id of the account it belongs to, which feeds get_lead and list_activities.
- list_usersread
List the org's Close users with their ids, names and emails. Call this to turn a person's name into the user_id that list_opportunities and list_activities filter on.
Use it from any agent
The same Close tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Close API Key in your Close account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Close once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.