MarketSharp MCP Server

Leads, appointments and jobs in your MarketSharp contractor CRM.

托管 MCP 服务器

npx add-mcp 'https://cotlet.dev/mcp/v1/marketsharp'

可安装到 Claude Code、Codex、Cursor 等客户端

文档

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

MarketSharp API and MCP server: Let your AI agent keep MarketSharp up to date.

MarketSharp has no MCP server. Its OData API is read only and comes with the Ultimate plan; writing data needs the REST API, which MarketSharp keeps for partners who serve at least 20 MarketSharp customers (checked 24 Oct 2026). Cotlet runs 14 MarketSharp tools hosted, over MCP for agents and REST for scripts.

Connect MarketSharp contacts, appointments and jobs to your reporting workflow. Use an AI agent through MCP or REST requests from automation tools and scripts.

MCP setup REST API guide

What can you automate in MarketSharp?

  • Turn lead emails into leads
  • Book the sales visit
  • Result appointments from rep texts
  • Add the rep's notes
  • Email tomorrow's visits to reps
  • Report sold jobs and contracts

Does MarketSharp have an MCP server or an API?

  • OData reads contacts, inquiries, appointments, jobs and activities with keys your admin makes under API Maintenance. It cannot add a lead, set an Appt Result, add a note or change a job.
  • The Zapier app and Zapier MCP have one action, Submit Lead, and no triggers. n8n has no MarketSharp node.
  • MarketSharp sends no webhooks to customers. Its only webhook endpoint takes events in from EverPro Edge, a supplier rebate program.
What you needOData API (Ultimate)ZapierCotlet
Search contacts, read appointments and jobsYes, in code you writeNoYes
Add a lead and book the sales visitNoLead only, no visitYes, after your OK
Result appointments and add notesNoNoYes, after your OK
Activities and job statusRead onlyNoYes
What you need firstUltimate, $499 a monthA Custom Lead CaptureYour own login, any plan
Allowed by MarketSharp's termsYes, officialYes, officialUses the web app

Checked 24 Oct 2026. Sources: MarketSharp API documentation (help center), How to connect to the MarketSharp API (OData), MarketSharp pricing, Zapier MCP for MarketSharp

How does Cotlet connect to MarketSharp?

  1. Sign in to MarketSharp. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your MarketSharp password, and no lead, result, note or email goes in until you approve it.

Connect MarketSharp 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.

  1. Enable MarketSharp for agents. Create a Cotlet account, log in to MarketSharp in its Cloud Browser with your own user, then press Enable for agents.
  2. Add the Cotlet address. Add https://cotlet.dev/mcp/v1 to your agent as an MCP server or custom connector.
  3. Sign in or use a key. Chat apps open a Cotlet sign-in. Editors, n8n and scripts send an API key made in the console.

MarketSharp shares https://cotlet.dev/mcp/v1 with every other app you enable. Turned MarketSharp on after you connected? Refresh the connector and the 14 tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-marketsharp \
  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-marketsharp": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-marketsharp]
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: marketsharp_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: marketsharp_write

How to use the MarketSharp REST API

Create your Cotlet API key

Create a Cotlet API key with access to MarketSharp and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Sign in to MarketSharp in its Cotlet Cloud Browser and enable the app for agents. Your MarketSharp role must allow access to the contacts, appointments and jobs you request.

Make your first MarketSharp API request

cURL:

curl "https://cotlet.dev/api/v1/marketsharp/jobs?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read jobs within a dated selection

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": "marketsharp",
  "tool": "list_jobs",
  "result": {
    "jobs": [
      {
        "job_id": "j_5531",
        "job_number": "1042",
        "customer": "Dana Miller",
        "job_status": "Sold",
        "contract_status": "Signed",
        "sold_on": "2026-10-08",
        "start_date": "2026-11-02"
      }
    ]
  }
}

Read result.jobs. Job lists default to 50 records and accept at most 200, without a cursor, page or offset input.

Narrow sold-date or status filters for large job lists instead of assuming a complete export beyond that limit. Compare contract and production status as well as job IDs.

Appointments require from and to dates. Activities default to the current user and today, excluding completed items unless requested.

MarketSharp workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestCombine jobs and job details into a contract and production report, comparing changing status.
MakeHTTP > Make a requestRead unresulted appointments into a visit-results follow-up queue without entering results.
Python or Node.jsREST APICombine activities and contact details into a salesperson's daily briefing without changing records.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads MarketSharp; 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.

MarketSharp API endpoints and MCP tools

Contacts, leads and notes

Lead sources and product interests must already be in your drop-down lists. MarketSharp cannot merge contacts, so the agent searches before it adds anyone.

  • Search contacts (search_contacts, read): Find prospects, leads and customers by name, phone, email or address, like Quick Find.
  • Get contact (get_contact, read): Full contact record: phones, addresses, inquiries, appointments, jobs, notes and open activities.
  • Create lead (create_lead, write, asks first): New lead with contact details and an inquiry, optionally with a sales appointment.
  • Add note (add_note, write, asks first): Add a note to the Notes tab of a contact.

Sales appointments

A visit hangs on an inquiry. A result with Sold checked in your list turns the lead into a customer.

  • List appointments (list_appointments, read): Sales appointments in a date range with contact, salesperson, set by and Appt Result.
  • Schedule appointment (schedule_appointment, write, asks first): Add a sales appointment to a contact's inquiry; it appears on the Sales Calendar.
  • Result appointment (result_appointment, write, asks first): Set the Appt Result after the visit. A result marked Sold converts the lead to a customer.
  • Issue appointments (issue_appointments, write, asks first): Email and issue appointments to the assigned salespeople, using one of your Issue Appointment templates.

Activity List

Calls and to-dos of your own Activity Types, assigned to any user.

  • List activities (list_activities, read): The Activity List: to-dos for a user and date, with type, contact and due date.
  • Add activity (add_activity, write, asks first): Add a follow-up activity to a contact and assign it to a user.
  • Complete activity (complete_activity, write, asks first): Mark an activity as completed, with an activity result.

Jobs and contracts

Reads products, contract amount and payments. New jobs are still created in MarketSharp.

  • List jobs (list_jobs, read): Jobs with job number, customer, job status, contract status, sale date and start date.
  • Get job (get_job, read): One job: products, contract amount and status, payments, production tasks and dates.
  • Update job status (update_job_status, write, asks first): Change a job's Job Status or Contract Status, for example to Canceled.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/marketsharp-api-mcp-server#tools

Who can see my MarketSharp session, and how do I revoke it?

  • What we store. Your logged-in MarketSharp profile, AES-256-GCM, in Finland. Not the password.
  • What your agent gets. The 14 MarketSharp tools. No cookie, no API keys.
  • What the session sees. What your MarketSharp user sees: contacts, visits, jobs, contract amounts.
  • One of your devices. MarketSharp counts the Cloud Browser as a device on your user license.
  • If MarketSharp signs you out. A web session ends after 8 h with no click. You log in again; we never do.
  • How to cut access. Disable for agents, reset the browser, or have your admin release the session.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Is it against MarketSharp's terms? Account safety

In accessing or using the Service, Customer will not: (c) apply systems to extract or modify information in the Service using technology or method such as those commonly referred to as "web scraping," "data scraping," or "screen scraping"

MarketSharp Master Subscription Agreement, section 2.3, 29 May 2025

Item (j) of the same section bars "any third party" other than Authorized Users, and section 2.6 lets MarketSharp suspend the service for "non-compliant use". Cotlet works in your own user's login, not as a second user, but MarketSharp could still call it screen scraping. We found no public case of an account suspended for automation (checked 24 Oct 2026). The contract runs a year, with 30 days to cure a breach.

How we keep your account looking like you:

  • Your own MarketSharp user, logged in by you
  • One Cloud Browser with its own IP, so one device on your license
  • Leads, results, notes and emails wait for your OK
  • No tool deletes a contact, job or appointment
  • If MarketSharp objects, we pause the MarketSharp tools for everyone within 24 h

Do not share one login across your team to save licenses. Section 2.2 of the terms forbids it, and MarketSharp's session limits are there to catch it.

What happens when MarketSharp changes?

  • 12 h between tests of the MarketSharp reads and writes
  • 24 h between tests of emails your reps would get
  • $0 for a call to a MarketSharp tool paused for a fix

MarketSharp gave Contacts, Sales and Contact Detail a new look every two weeks from 4 Aug 2026. Changes like that land on our side, not in your prompts. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Lists the open visits. Past appointments with no Appt Result, per rep.
  2. Matches the rep's words. To your own result list; asks when two fit.
  3. Waits for your OK. Each result and note shows up in your Cotlet console.
  4. Reports what is left. Results set, follow-ups missing, visits to ask about.
ActionUndo
Result an appointmentClear or change it; a Sold result already made a customer
Create a leadDelete the contact in MarketSharp; there is no merge
Add a noteNo tool removes it
Add an activityDelete it, also in bulk from the Activity List
Issue appointmentsNo, the emails are out

8 of 14 tools ask first: every tool that writes. The six reads run at once. Switch the wait off per tool for a scheduled run, or enable MarketSharp read only.

Appointment Rules fire when a result is saved. A wrong result can add follow-up activities you then delete.

MCP call:

{
  "name": "result_appointment",
  "arguments": {
    "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
    "result": "Sold"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/marketsharp/appointments/a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90/result \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"result":"Sold"}'

Tool output:

{
  "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "result": "Sold",
  "sold": true,
  "contact_type": "customer",
  "next_step": "Create a job for this customer"
}

Scripts and cron jobs call the same tools over REST at /api/v1/marketsharp, with one key and one price. A call your MarketSharp permissions block, such as notes without Edit on Notes, fails and costs nothing. The tools table lists the REST path of each tool.

How much does the MarketSharp MCP server cost?

About $23 a month for a remodeler with 3 reps and 25 sales visits a month, 3,990 credits. MarketSharp bills its plan as before.

JobCallsCredits
New lead with a sales visit booked4 × 251,000
Result a visit and keep the rep's note3 × 25750
Email tomorrow's visits to the reps, weekdays2 × 22440
Follow-up call for a visit with no sale1 × 18180
Sold jobs and contract status, weekly3 × 4120
Cloud Browser, 30 days1,500
Total3,990
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Standard and Pro, not only Ultimate

The month is our example: 40 new leads, 25 sales visits and about 7 sold, the 20 to 30% close rate most home improvement call centers reported to Hatch in 2024. Dollars at the $29 pack rate.

MarketSharp MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Zapier MCP for MarketSharpSubmit Lead from any MCP client; an existing contact gets a new inquiry.One action. Reads, books, results and notes nothing.
madeinutica/sitekickA TypeScript OData client inside a website builder, 0 stars, last commit 10 Mar 2026.Read only, needs Ultimate and admin keys, no license.
Shahram4wd/marketsharpPython importers for OData contacts, jobs and appointments, last commit 28 Oct 2024.A data copy, not a server. Read only.
HatchLead follow-up texting with a two-way MarketSharp sync every hour.Its own follow-up flows; your agent cannot call it.

There is no MarketSharp MCP server on GitHub. Code on the OData API is fine for a dashboard on Ultimate and stops at the first write. Zapier fits a web form that should drop leads in. Cotlet is for the resulting, booking and notes your office types in by hand today.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the MarketSharp tools go to contact@cotlet.dev.

MarketSharp API and MCP: questions

Can I use the MarketSharp 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, open MarketSharp under Integrations in the console and log in to MarketSharp in its Cloud Browser with your own user. The trial starts when you sign up and asks for no card.

How do I connect MarketSharp to ChatGPT or Claude?

Sign up at cotlet.dev, log in to MarketSharp 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 MarketSharp account through Cotlet, in their phone apps too.

What can ChatGPT do in MarketSharp?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in MarketSharp: add leads from email and book the sales appointment; result sales appointments and log the outcome; find appointments with no result. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need an admin to enable the MarketSharp API?

Not for Cotlet. It works in your own MarketSharp user account and does not use the OData API, which an account admin enables under API Maintenance (checked 11 Oct 2026).

Does MarketSharp have webhooks?

Not for customers. MarketSharp sends no events out, and Zapier has no MarketSharp triggers. Run your agent on a schedule instead, for example every morning: list_appointments with unresulted_only, then list_activities for the day.

Does it work on the Standard plan?

Yes. Cotlet works in your own login on Standard, Pro or Ultimate. The OData API is the part MarketSharp keeps for Ultimate, and Cotlet does not use it.

Does the agent need its own MarketSharp license?

No. It works in your user's login, so the Cloud Browser takes one of that user's device sessions. If MarketSharp says the device limit is reached, your admin releases an old session under Manage Team.

Is the MCP server different from the REST API?

Only the way in differs. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; cron jobs and HTTP steps use REST.

Is Cotlet affiliated with MarketSharp?

No. Cotlet is independent and not affiliated with MarketSharp, EverPro or EverCommerce.


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.