MCP tools
Give an AI agent your CRM as tools. It works as the key's teammate, with the key's scopes.
Connect a client
The MCP server lives at https://syntropic-crm.com/api/mcp over streamable HTTP. Send your key in the Authorization header, exactly as for REST. Replace the sample key below with yours.
Claude Code
Run this once in a terminal. Claude Code sends the key as a header on every request.
claude mcp add --transport http syntropic https://syntropic-crm.com/api/mcp --header "Authorization: Bearer sk-syn-YOUR_KEY"Claude Desktop
Add this to claude_desktop_config.json, then restart Claude Desktop. It needs Node.js on this computer.
{
"mcpServers": {
"syntropic": {
"command": "npx",
"args": [
"mcp-remote@0.14.3",
"https://syntropic-crm.com/api/mcp",
"--header",
"Authorization:${SYNTROPIC_AUTH}"
],
"env": {
"SYNTROPIC_AUTH": "Bearer sk-syn-YOUR_KEY"
}
}
}
}Cursor
Add this to ~/.cursor/mcp.json, and set SYNTROPIC_API_KEY in your shell so the key stays out of your project.
{
"mcpServers": {
"syntropic": {
"url": "https://syntropic-crm.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:SYNTROPIC_API_KEY}"
}
}
}
}
export SYNTROPIC_API_KEY=sk-syn-YOUR_KEYHermes
Add this to ~/.hermes/config.yaml, and set SYNTROPIC_API_KEY where Hermes runs.
mcp_servers:
syntropic:
url: "https://syntropic-crm.com/api/mcp"
headers:
Authorization: "Bearer ${SYNTROPIC_API_KEY}"
export SYNTROPIC_API_KEY=sk-syn-YOUR_KEYREST / Zapier
Zapier, Make, n8n and your own scripts call the REST base URL with the same key in an Authorization header.
curl -X POST -H "Authorization: Bearer sk-syn-YOUR_KEY" https://syntropic-crm.com/api/agent-gateway/whoamiclaude.ai connects with a fixed header only if your organization has Request headers (beta). On Team and Enterprise plans that header is set once for the whole organization, so everyone in it uses the same key and acts as the same teammate. Use a key for a teammate whose access fits everyone, or connect from Claude Code, Claude Desktop or Cursor, where each person uses their own key.
ChatGPT can't send an API key yet. It will connect once sign-in (OAuth) arrives.
How tools work
- Each tool is one REST endpoint, with the same fields, scopes, rules and limits: a tool call counts as one request. The reference has the details.
- Your client only sees the tools your key's scopes allow. Add a scope to the key and reconnect to see more.
- Each tool carries MCP hints: read-only tools say so, and tools that call, text or email someone are marked as reaching outside the CRM.
- A refusal, such as a missing scope, comes back as a tool error with the same message. A write held for approval comes back as a normal result that says it's waiting.
Tools
| Tool | What it does | Kind |
|---|---|---|
add_lead_note | Add a note to the lead's timeline as the key's rep. @mentions notify teammates as in the app. | Changes data |
analyze_deal | MAO, opening offer and walk-away from the account's saved deal defaults and offer rules. | Read-only |
complete_lead_task | Mark a task on a lead done. The rep must own the task, unless they're an owner or admin. | Changes data |
create_lead | Add a seller lead owned by the key's rep, in the account's acquisitions pipeline. An address, phone or email already on a lead, at any stage, answers 409 with the matching leads unless allowDuplicate is true. | Changes data |
create_lead_task | Add a follow-up task to a lead, for the key's rep or another active teammate, with an optional due date and time. | Changes data |
create_reminder | Set a reminder for the rep at a date and time in the account's time zone, optionally on a lead, transaction or dispo deal. | Changes data |
creative_finance | Price a seller-finance, subject-to or hybrid deal: entry cost, payments, spread and balloon exposure, with an optional cash comparison. | Read-only |
dialer_session_status | The account's live power dialer sessions: rep, state, start time, lines and counts. No phone numbers or lead names. | Read-only |
estimate_rehab | Price an itemized repair scope with the account's unit costs. | Read-only |
find_lead | Search the leads the rep can see by name, phone or address. Give at least one. | Read-only |
get_call_recording | The audio of one call from Recent calls, streamed with the API key. Checks the key's rep can open that call on every request; never returns a link. Only calls with recordingFetchable true can be downloaded. Over MCP, recordings up to 3 MB come back as audio; larger ones must use REST. | Read-only |
get_lead | One lead by id: contact details, stage, owner, recent outcomes, notes and counts. A lead the rep can't see answers 404. | Read-only |
get_property_underwrite | The status and, once finished, the result of an underwrite run. Free. | Read-only |
list_calls | Recorded or connected calls the key's rep can open, newest first. Without from, until or cursor: the latest, at most 15. With from and/or until (epoch ms, or YYYY-MM-DD in the account's time zone, until exclusive / through that day): pages of up to limit checked calls with nextCursor; a page can be empty while nextCursor has more, and nextCursor is null when done. | Read-only |
list_dispo_deals | The deals on the Dispo desk with their stage, asking price, buyer interest and blast activity. | Read-only |
list_events | CRM events from the last 30 days, newest first, limited to the leads and records the key's rep can open. Each call checks one page of up to 100 recorded events, so a page can be empty while nextCursor still has more. truncated is true when some events couldn't be checked and were left out. | Read-only |
list_lead_tasks | The open or done tasks on one lead, with their ids for completing them. | Read-only |
list_leads | The seller leads the key's rep can see. Without cursor: newest activity first, at most limit, with truncated when more exist. With cursor: send "start", then each nextCursor, to walk every lead oldest-created first; a page can be empty while nextCursor has more, and nextCursor is null when done. Send the same filters on every page. | Read-only |
list_offers | The account's open offers on seller leads, with amounts, status and follow-up dates. | Read-only |
list_projects | Rehab projects with budget, schedule and open tasks, or one project by id. | Read-only |
list_properties | Rental properties with tenants, rent status, leases and open maintenance. | Read-only |
list_reminders | The rep's open or done reminders. | Read-only |
list_support_tickets | Support tickets this account filed, newest first, with status and last update. Message text is not included. | Read-only |
list_tc_chases | Without a transactionId, every chase past its next-chase time. With one, that file's chase history. | Read-only |
log_call | Record a call the rep already made on a lead, with its outcome and notes. It shows on the lead's timeline and counts like a call logged in the app. Nothing is dialed. | Changes data |
meeting_prep | A brief for one of the rep's own appointments: the lead, recent notes, calls and texts, and open offers. | Read-only |
move_lead_stage | Move a lead to another stage in its pipeline, by stage key or name. The stage's required fields and the lead's locks apply as in the app. | Changes data |
offer_history | Offers made over a past window, optionally filtered by status. | Read-only |
place_call | Ring the rep's phone, then connect it to a number on the lead. Do-not-call and calling hours always apply. | Sends |
read_calendar | The rep's agenda: today's and upcoming appointments. | Read-only |
read_draw_schedule | Lender draw schedules on rehab projects, or one project's schedule. | Read-only |
read_email_thread | The emails between the rep's own mailbox and a lead or contact the rep can see, newest first, one page at a time. Other teammates' mail is never included, and an email that also belongs to a lead or contact the rep can't see is left out and counted in omitted. Addresses on records the rep can see are shown in full, as in the app. A page can hold fewer emails than the limit; keep reading while cursor is set. | Read-only |
read_text_thread | The texts with a lead or contact the rep can see, newest first, one page at a time. Numbers and names on records the rep can see are shown in full, as in the app. A text that also belongs to a lead or contact the rep can't see is left out and counted in omitted. | Read-only |
send_email | Email an address on the lead as the rep. Do-not-email and unsubscribes always apply. | Sends |
send_text | Text a number on the lead from the rep's line. Do-not-text, opt-outs and calling hours always apply. | Sends |
stress_underwrite | The base case plus ARV -5%, rehab +15%, timeline +2 months and all three, with MAO, profit and ROI for each. | Read-only |
tag_lead | Add a tag to a lead (created if the account doesn't have it yet), or remove one with remove: true. DNC and DNT can be added but only removed in the app. | Changes data |
transaction_board | Every open transaction file with its stage, closing date, overdue checklist items and what's due next. | Read-only |
underwrite_lead | Run the Deal Analyzer on a lead's saved property facts, with optional overrides, and return MAO and offer guidance. | Read-only |
underwrite_property | Start a full underwrite of a lead or an address: comps, ARV, as-is value, repairs and offers. Answers at once with a runId; get the result in 1-3 minutes from comps-underwrite.get. 100 AI credits, charged only if the run finishes ok. | Read-only |
update_lead | Change a lead's contact details, value, source, address or its lead fields. Stage, owner and system fields can't be set here; use the stage op for the stage. | Changes data |
whoami | The rep this key acts as, and the key's name, scopes and approval setting. | Read-only |