REsimpli MCP Server
Leads, deal stages and drip campaigns for real estate investors.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/resimpli'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
REsimpli API and MCP server: Let your AI agent work your REsimpli leads.
REsimpli has an official Open API on every plan since REsimpli 6.0 went live on 12 Sep 2026, but it only reads, creates and deletes records, and its MCP server is announced with no date (checked 24 Oct 2026). Cotlet runs 15 REsimpli tools hosted, over MCP for agents and REST for scripts.
Bring REsimpli leads and pipeline details into your agent or reporting workflow. Use MCP or authenticated REST requests from automation tools and scripts.
- Free 7-day trial, no card
- Unofficial, not affiliated with REsimpli
- Page: https://cotlet.dev/integrations/resimpli-api-mcp-server
What can you automate in REsimpli?
- Move leads after a calling block
- Log the offer in a lead note
- Set call-back tasks for your team
- Assign new leads
- Put dead leads into a drip
- Skip trace leads with no phone
Does REsimpli have an MCP server or an API?
- The Open API covers 4 of our 15 tools: list and read leads, list pipelines, create a lead. Status, notes, tags, assignment and tasks are "planned for a future update".
- API changes fire no automations, and no endpoint enrolls a lead in a drip, sends a text or runs a skip trace.
- The REsimpli 6.0 Zapier app has 7 actions, all of them creates (leads, list stacking, buyers, agents, vendors), and no trigger.
| What you need | Open API | Zapier (REsimpli 6.0) | Cotlet |
|---|---|---|---|
| Read leads, pipelines and call logs | Yes, in your code | No | Leads and pipelines |
| Create a lead | Yes | Yes, land or residential | Yes |
| Change status, add notes, tags and tasks | Planned, no date | No | Yes |
| Enroll in a drip, text, skip trace | No | No | Yes, after your OK |
| The route REsimpli provides | Yes, official | Yes, official | Uses the web app |
Checked 24 Oct 2026. Sources: REsimpli help: Open API and Integrations, REsimpli Open API endpoint tester, Zapier: REsimpli 6.0 integrations, REsimpli pricing
How does Cotlet connect to REsimpli?
- Sign in to REsimpli. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your REsimpli password, and no text, drip or skip trace runs until you approve it.
Connect REsimpli to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable REsimpli for agents. Open a Cotlet account, sign in to REsimpli 6.0 in its Cloud Browser with your own user, then press Enable for agents.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 where your agent lists MCP servers or connectors.
- Confirm who is asking. Chat apps send you through a Cotlet sign-in. Editors, n8n and scripts carry an API key made in the console.
REsimpli rides on the same address as your other apps, https://cotlet.dev/mcp/v1. Turned REsimpli on after connecting? Refresh the connector to load its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-resimpli \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-resimpli": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-resimpli]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: resimpli_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: resimpli_write
How to use the REsimpli REST API
Create your Cotlet API key
Sign in to REsimpli in its Cotlet Cloud Browser and enable the app for agents. Your REsimpli account permissions determine which leads and records you can read.
Create a Cotlet API key with access to REsimpli and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Make your first REsimpli API request
cURL: list_leads:
curl "https://cotlet.dev/api/v1/resimpli/leads?page=1&limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read leads and follow page numbers
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "resimpli",
"tool": "list_leads",
"result": {
"leads": [
{
"lead_id": "66f1c2a9e4b0a1d3c8f20417",
"name": "Dana Whitfield",
"property_address": "12 Oak St, Columbus, OH 43215",
"pipeline": "Acquisitions",
"status": "Contact Made",
"assignee": "Sam Rivera",
"tags": [
"D4D October"
]
}
],
"page": 1,
"has_more": true
}
}
Read result.leads. Start at page=1, increment the page while result.has_more is true, and stop when it is false.
Lead pages default to 25 records, with a maximum of 100. Keep search, pipeline, status, tag and limit filters unchanged; this operation does not use a cursor.
Read list_pipelines for your account's IDs and compare lead stage and assignee on later runs. get_skip_trace_results reads existing results without launching a paid skip trace.
REsimpli workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read pipelines and page through leads into a status report, comparing stage and assignee by lead ID. |
| Make | HTTP > Make a request | Read lead details into a follow-up brief with contacts, notes and open tasks without moving leads. |
| Python or Node.js | REST API | Read existing skip-trace results into a contact-coverage report without starting paid searches. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads REsimpli; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
REsimpli API endpoints and MCP tools
Leads and pipelines
Pipeline and status names are the ones you set up, read by ID from list_pipelines. Dead Leads wants a reason no tool can give, so those moves stay with you.
- List leads (
list_leads, read): Leads with property address, pipeline, status, assignee and tags. - Get lead (
get_lead, read): Full lead: contacts, property, status, notes, tags, tasks and recent activity. - List pipelines (
list_pipelines, read): Your pipelines and the statuses in each, with IDs, as set up in your account. - Create lead (
create_lead, write): New seller lead with contact details and property address. - Update lead status (
update_lead_status, write): Move a lead to another status, or to a status in another pipeline.
Notes, tags, tasks and assignment
Your team sees these, the seller does not. Tasks land in the REsimpli calendar; REsimpli does not sync them to Google Calendar yet.
- Add lead note (
add_lead_note, write): Add a note to the lead, visible to your team. - Tag lead (
tag_lead, write): Add or remove tags on a lead. - Assign lead (
assign_lead, write): Assign a lead to a team member. - Create task (
create_task, write): Set up a task on a lead with a due time and assignee.
Drips and texts
Enrolling and texting reach the seller, so both ask first. Stopping a drip skips the steps not yet sent.
- List automations (
list_automations, read): Your lead automations, including drips, with name and whether each is on. - Enroll lead in automation (
enroll_lead_in_automation, write, asks first): Add a lead to an automation; its steps can text, email or mail the seller. - Remove lead from automation (
remove_lead_from_automation, write): Stop a running automation for one lead. Steps not yet sent are skipped. - Send SMS (
send_sms, write, asks first): Text a lead from your REsimpli campaign number. Shows in the lead's inbox.
Skip tracing
Draws on your plan's pooled monthly credits (10,000 on Solo, 20,000 on Team); past that REsimpli bills $0.15 a record.
- Skip trace lead (
skip_trace_lead, write, asks first): Run a skip trace on the lead's property owner. - Get skip trace results (
get_skip_trace_results, read): Phone numbers and emails found for a lead.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/resimpli-api-mcp-server#tools
Who can see my REsimpli session, and how do I revoke it?
- What we store. Your signed-in REsimpli profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 15 REsimpli tools, never the cookie or your Open API key.
- What the session sees. What your REsimpli user sees: sellers, phone numbers, notes, texts.
- What your team sees. REsimpli's green dot shows the session in a lead like any teammate.
- If REsimpli wants a code. Two-factor codes, also before a bulk text, are typed by you, never by us.
- How to cut access. Disable for agents, reset the browser, or Log out everywhere in REsimpli.
cotlet.dev rates A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). A SOC 2 report or third-party pentest is not done yet.
Is it against REsimpli's terms? Account safety
Automated use through functionality expressly provided by REsimpli is permitted, subject to plan limits, published usage allowances, applicable law, carrier restrictions, and this Fair Use Policy.
REsimpli Terms of Service, section 13, effective 17 Sep 2026
A browser agent is not one of those features, and the pricing FAQ says fair use exists "to prevent abuse such as bots, spam blasting, reselling access, or bulk exporting our data." Section 9 adds a ban on scraping. The stated process is a talk first: REsimpli says it will reach out and review the account, and section 21 promises notice and a chance to fix "when practicable". We found no public case of a REsimpli account closed for automation (checked 24 Oct 2026).
How we keep your account looking like you:
- Your own REsimpli user, signed in by you, no extra seat
- One Cloud Browser with steady cookies and IP, so the device history shows one device
- Texts, drip enrollments and skip traces wait for your OK
- Leads move one at a time, never with bulk Change Status
- If REsimpli objects, we pause the REsimpli tools for everyone within 24 h
Texts and drips fall under TCPA and carrier rules, and section 3 puts the cadence and consent on you. Text sellers who gave you their number, and spread a big drip batch over days.
What happens when REsimpli changes?
- 12 h between tests of the REsimpli reads and lead updates
- 24 h between tests of texts and drips a seller would get
- $0 for a call to a REsimpli tool paused for a fix
REsimpli 6.0 replaced the whole app on 12 Sep 2026, and every Zapier user had to reconnect to a new app. A change like that is ours to absorb: the tool names and inputs stay the same. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Checks the drip is on. list_automations must show it switched on.
- Picks the dead leads. Skips "property sold", opt-outs and leads already in a drip.
- Waits for your OK. The batch shows up in your Cotlet console first.
- Tags and reports. Enrolled, skipped with reasons, left for next week.
| Action | Undo |
|---|---|
| Move a lead to another status | One more call moves it back; status automations that fired stay fired |
| Enroll a lead in a drip | remove_lead_from_automation skips what is not sent yet |
| Send a text | No, the seller has it |
| Run a skip trace | No, the credit is spent |
| Tag or assign a lead | Yes, same tool |
3 of 15 tools ask first: send_sms, enroll_lead_in_automation and skip_trace_lead, the ones that reach a seller or spend credits. Status moves, notes, tags and tasks stay inside your team and run at once. Turn the wait off per tool for a scheduled run.
REsimpli keeps a dead lead's drips running unless an automation on Dead Lead stops them. Check that before you mark sellers dead.
MCP call:
{
"name": "update_lead_status",
"arguments": {
"lead_id": "66f1c2a9e4b0a1d3c8f20417",
"status_id": "64a0d5b2c91e7f0012ab33c6"
}
}
REST:
curl -X PATCH https://cotlet.dev/api/v1/resimpli/status/64a0d5b2c91e7f0012ab33c6/leads/66f1c2a9e4b0a1d3c8f20417/status \
-H "Authorization: Bearer $COTLET_API_KEY"
Tool output:
{
"lead_id": "66f1c2a9e4b0a1d3c8f20417",
"property_address": "12 Oak St, Columbus, OH 43215",
"pipeline": "Acquisitions",
"status": "Under Contract",
"previous_status": "Contact Made",
"updated_at": "2026-10-11T14:32:05-04:00"
}
Scripts and cron jobs call the same tools over REST at /api/v1/resimpli, one key and one price. A status ID that is not in your pipelines fails the call, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the REsimpli MCP server cost?
About $45 a month for an investor working 40 new seller leads a month, 7,680 credits. REsimpli bills its own plan as before.
| Job | Calls | Credits |
|---|---|---|
| Statuses and notes after the calling block, weekdays | 14 × 22 | 3,080 |
| Assign a new lead and set the call-back | 3 × 40 | 1,200 |
| Dead leads into the reactivation drip, weekly | 25 × 4 | 1,000 |
| Skip trace a lead with no phone | 2 × 20 | 400 |
| Text a seller back after your OK | 2 × 25 | 500 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 7,680 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on Solo, Team and Business alike
The month is our example: a Team-plan investor with a calling block every weekday and about 12 dead leads a week into a drip. Vendor blogs put ad-driven volume at 30 to 80 qualified seller leads a month. Dollars at the $29 pack rate.
REsimpli MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Zapier MCP | The 7 REsimpli 6.0 Zapier actions as agent tools: add leads, list stacking records, buyers, agents and vendors. | Creates only. Each call costs 2 Zapier tasks; the free plan has 100 a month. |
| REsimpli AI Agents | Built-in agents that call, text, score leads and coach calls, $99 to $399 a month each, $1,099 for all. | They run inside REsimpli on its own rules; your Claude or ChatGPT cannot drive them. |
| Your own script on the Open API | 500 requests a minute, every plan, one key per account. | Reads and creates; no status, note, tag, task, drip or text. |
| GitHub | No REsimpli MCP server, CLI or API client found. | Nothing to run yet. |
If you only push new leads in from forms and ads, the Open API or Zapier does it for free and is the route REsimpli supports. If you want your own agent to clean up the pipeline after every calling block and run the follow-up, Cotlet does that in your account today. REsimpli says its own MCP server is coming; when it ships, we will compare it here.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company in Poland, EU (VAT PL6342984273), in business since 2019. Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) founded it. Questions about the REsimpli tools go to contact@cotlet.dev.
REsimpli API and MCP: questions
Can I use the REsimpli API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Sign up free at https://cotlet.dev, find REsimpli under Integrations in the console and sign in to REsimpli in its Cloud Browser. Your trial starts when you sign up, and nobody asks for a card.
How do I connect REsimpli to ChatGPT or Claude?
Sign up at cotlet.dev, log in to REsimpli once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your REsimpli account through Cotlet, in their phone apps too.
What can ChatGPT do in REsimpli?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in REsimpli: update lead statuses and notes after a calling session; reactivate dead leads with a drip; skip trace new leads. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need a certain REsimpli plan?
The official Open API is included on every plan (checked 11 Oct 2026). Cotlet works in your own REsimpli account and does not use it; the features you use, such as automations, follow your plan in REsimpli.
Will the official API make Cotlet unnecessary?
It may cover more later. REsimpli lists updates to status, notes, tags, assignment and tasks as planned, and an MCP server as in development with no date. Until then they are not available.
Does REsimpli have webhooks?
Yes, outgoing ones: up to 10 per account, fired from any automation trigger, for example when a lead reaches Under Contract. Point one at your own endpoint to wake your agent, and let the agent do the follow-up through Cotlet.
Does it work with the old REsimpli?
No. Cotlet works in REsimpli 6.0, which replaced the old app for every account on 12 Sep 2026. REsimpli's Open API does not work with the old version either.
Can the agent see my REsimpli API key?
No. The agent gets the Cotlet tools only. Your REsimpli key stays in Settings, API & Webhooks, and Cotlet does not use it.
Is the MCP server different from the REST API?
The tools are the same 15, with the same inputs, answers, key and price. Agents connect over MCP; scripts, cron jobs and HTTP steps use REST.
Is Cotlet affiliated with REsimpli?
No. Cotlet is independent and not affiliated with REsimpli.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.