Tekmetric API and MCP server Let your AI agent work your Tekmetric Job Board.

Job board, repair orders, customers, appointments and texts in your shop. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Tekmetric
Tekmetric logo Tekmetric Cloud Browser

10 tools Read and write

Six jobs for the counter

What can you automate in Tekmetric? Use an AI agent, a workflow or a script.

  • Chase estimates waiting on authorization

  • Text customers when the car is ready

  • Brief you on the Job Board each morning

  • Book appointments without a clash

  • Sort unread Tekmessage threads

  • Find a customer and their vehicles

Partner API only

Does Tekmetric have an MCP server or an API? An API for approved partners, with no texting. No MCP server.

Tekmetric has no MCP server (checked 28 Oct 2026). Its REST API at api.tekmetric.com covers repair orders, customers, vehicles and appointments, but credentials come only after an API Application form and a review of 2 to 3 weeks, which Tekmetric may decline "at Tekmetric's sole discretion". Cotlet runs 10 Tekmetric tools hosted, over MCP for agents and REST for scripts, in your own employee login.

  • The API has no messaging endpoint, so no agent on it can read or answer a Tekmessage thread. Its share-link call marks an estimate, invoice or inspection as shared; the docs do not say it texts the customer.
  • Zapier and n8n have no Tekmetric app (both pages answer 404). The one AI product Tekmetric sells is the Receptionist add-on, a voice agent for inbound calls.
  • The two Tekmetric MCP servers on GitHub are read-only and need the same approved API credentials.
Tekmetric with its partner API, a GitHub MCP server and Cotlet compared
What you need Tekmetric APIGitHub MCP serverCotlet
Read the Job Board, repair orders and customers Yes Yes Yes
Book an appointment Yes No, read-only Yes, after your OK
Send an estimate to the customer Marks it shared No Yes, after your OK
Read and answer customer texts No endpoint No Yes, on Scale
What you need first Approved application, 2 to 3 weeks Approved API credentials Your Tekmetric login

Checked 28 Oct 2026. Sources: Tekmetric API docs · Tekmetric integrations · Tekmetric pricing · Tekmetric Terms of Service

Set up once

How does Cotlet connect to Tekmetric? One account, two ways to connect.

  1. 1Sign in to Tekmetric

    Use your own account in its Cotlet Cloud Browser.

  2. 2Choose MCP or REST

    Connect your agent or create a Cotlet API key.

  3. 3Run your workflow

    Ask your agent or send an HTTP request.

We never keep your Tekmetric password, and no text, estimate or appointment reaches a customer until you approve it. Who can see your session

Any MCP client

Connect Tekmetric 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. 1

    Enable Tekmetric for agents. Create a Cotlet account, sign in to Tekmetric with your employee login in its Cloud Browser and press Enable for agents.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as a new MCP server or connector in your agent.

  3. 3

    Let the agent in. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scheduled scripts take an API key from the console.

The address https://cotlet.dev/mcp/v1 is shared: Tekmetric shows up there next to any other app you enable. Turned Tekmetric 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-tekmetric \
  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-tekmetric": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet-tekmetric]
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: tekmetric_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: tekmetric_write
Scripts and HTTP

How to use the Tekmetric REST API

Create your Cotlet API key

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

Connect Tekmetric in Cotlet and enable it for agents. Account access: Your own Tekmetric employee login; what your agent can reach follows your employee permissions (texting needs "Can message customers").

Make your first Tekmetric API request

REST
curl https://cotlet.dev/api/v1/tekmetric/job-boards \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read job board repair orders and apply the operation limits

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": "tekmetric",
  "tool": "list_job_board",
  "result": {
    "repair_orders": [
      {
        "repair_order_id": "ro_30412",
        "column": "estimates",
        "status": "Pending Authorization",
        "customer": "Dana Whitfield",
        "vehicle": "2017 Honda CR-V",
        "jobs": 3,
        "total": "$842.10",
        "estimate_sent": true,
        "estimate_viewed": false
      },
      {
        "repair_order_id": "ro_30415",
        "column": "work_in_progress",
        "status": "In progress",
        "customer": "Luis Ortega",
        "vehicle": "2014 Ford F-150",
        "jobs": 5,
        "total": "$1,620.40",
        "estimate_sent": true,
        "estimate_viewed": true
      },
      {
        "repair_order_id": "ro_30409",
        "column": "completed",
        "status": "Completed",
        "customer": "Priya Nair",
        "vehicle": "2020 Toyota Camry",
        "jobs": 2,
        "total": "$376.00",
        "estimate_sent": true,
        "estimate_viewed": true
      }
    ],
    "next_cursor": null
  }
}

Returns one row per repair order with its column, card status, customer, vehicle, job count and total. Each row says whether the estimate was sent or viewed, the same paper airplane and eye icons the Job Board shows.

Declined and deleted repair orders are not in the default view.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Tekmetric workflows for agents and automations

Tekmetric workflows you configure
ToolConnect throughExample workflow
n8nHTTP RequestReads one repair order with its jobs, parts and authorization state. Use get_repair_order in your configured business report.
MakeHTTP > Make a requestLists appointments on the shop calendar for a date range. Use list_appointments in your configured business report.
Python or Node.jsREST APIReads the messages of one Tekmessage thread. Use get_message_thread in your configured business report.

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

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

7 read, 3 write

Tekmetric API endpoints and MCP tools

Job Board and repair orders3

The three board columns, Estimates, Work-in-Progress and Completed, with card status and whether the estimate was sent or viewed. Inspections and photos stay out.

  • list_job_board Lists repair orders on the Job Board, by column. read

    Returns one row per repair order with its column, card status, customer, vehicle, job count and total. Each row says whether the estimate was sent or viewed, the same paper airplane and eye icons the Job Board shows. Declined and deleted repair orders are not in the default view.

    MCP calltekmetric_read → list_job_board

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/job-boards

    Parameters

    Parameters: list_job_board
    NameTypeDescription
    column string string estimates, work_in_progress or completed. Defaults to all three.
    status string string Card status, for example Not Started, Requires Authorization, Pending Authorization or Declined All.
    employee string string Name of an employee, to see only their repair orders.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "repair_orders": [
        {
          "repair_order_id": "ro_30412",
          "column": "estimates",
          "status": "Pending Authorization",
          "customer": "Dana Whitfield",
          "vehicle": "2017 Honda CR-V",
          "jobs": 3,
          "total": "$842.10",
          "estimate_sent": true,
          "estimate_viewed": false
        },
        {
          "repair_order_id": "ro_30415",
          "column": "work_in_progress",
          "status": "In progress",
          "customer": "Luis Ortega",
          "vehicle": "2014 Ford F-150",
          "jobs": 5,
          "total": "$1,620.40",
          "estimate_sent": true,
          "estimate_viewed": true
        },
        {
          "repair_order_id": "ro_30409",
          "column": "completed",
          "status": "Completed",
          "customer": "Priya Nair",
          "vehicle": "2020 Toyota Camry",
          "jobs": 2,
          "total": "$376.00",
          "estimate_sent": true,
          "estimate_viewed": true
        }
      ],
      "next_cursor": null
    }
  • get_repair_order Reads one repair order with its jobs, parts and authorization state. read

    Returns the customer, vehicle, each job with its status and price, the total and how each job was authorized (digital signature, phone call, text message and so on). Inspections and photos are not returned.

    MCP calltekmetric_read → get_repair_order

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/repair-orders/{repair_order_id}

    Parameters

    Parameters: get_repair_order
    NameTypeDescription
    repair_order_id string required string Repair order ID from list_job_board.

    Example input

    {
      "repair_order_id": "repair_order_8c41d2"
    }

    Example response

    {
      "repair_order_id": "ro_30412",
      "customer": "Dana Whitfield",
      "vehicle": "2017 Honda CR-V",
      "column": "estimates",
      "jobs": [
        {
          "name": "Front brake pads and rotors",
          "price": "$512.30",
          "authorized": false
        },
        {
          "name": "Cabin air filter",
          "price": "$64.80",
          "authorized": false
        },
        {
          "name": "Oil and filter change",
          "price": "$265.00",
          "authorized": false
        }
      ],
      "total": "$842.10"
    }
  • share_estimate Sends the estimate of a repair order to the customer, like Share Estimate in the app. writeasks first

    The customer receives a link to the estimate and can authorize jobs from it. The repair order shows the paper airplane icon after sending. The estimate must be ready to share. By default you confirm each call; you can switch that off for this tool.

    MCP calltekmetric_write → share_estimate

    REST endpointPOST https://cotlet.dev/api/v1/tekmetric/repair-orders/{repair_order_id}/estimate/share

    Parameters

    Parameters: share_estimate
    NameTypeDescription
    repair_order_id string required string Repair order ID from list_job_board.
    channel string string text or email. Defaults to text.

    Example input

    {
      "repair_order_id": "repair_order_8c41d2"
    }

    Example response

    {
      "repair_order_id": "ro_30412",
      "channel": "text",
      "sent_to": "+1 555 0142",
      "status": "sent",
      "sent_at": "2026-10-28T09:12:00Z"
    }

Customers and appointments4

Search by name, phone or email; the vehicle ID from a customer record is what an appointment is booked on.

  • list_customers Finds customers by name, phone number or email. read

    Returns matching customers newest first with their phone numbers and vehicle count. Use customer_id with get_customer for the full record.

    MCP calltekmetric_read → list_customers

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/customers

    Parameters

    Parameters: list_customers
    NameTypeDescription
    query string required string Name, phone number or email.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "query": "query"
    }

    Example response

    {
      "customers": [
        {
          "customer_id": "cu_8841",
          "name": "Dana Whitfield",
          "phone": "+1 555 0142",
          "vehicles": 2
        },
        {
          "customer_id": "cu_8853",
          "name": "Dana Whitaker",
          "phone": "+1 555 0177",
          "vehicles": 1
        }
      ],
      "next_cursor": null
    }
  • get_customer Reads a customer with their phone numbers, vehicles and repair orders. read

    Returns the contact details on the customer profile, each vehicle with its ID, and recent repair orders. The agent uses the vehicle ID to book an appointment.

    MCP calltekmetric_read → get_customer

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/customers/{customer_id}

    Parameters

    Parameters: get_customer
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.

    Example input

    {
      "customer_id": "customer_8c41d2"
    }

    Example response

    {
      "customer_id": "cu_8841",
      "name": "Dana Whitfield",
      "phones": [
        "+1 555 0142"
      ],
      "vehicles": [
        {
          "vehicle_id": "ve_5520",
          "name": "2017 Honda CR-V"
        },
        {
          "vehicle_id": "ve_5521",
          "name": "2011 Mazda 3"
        }
      ],
      "repair_orders": [
        {
          "repair_order_id": "ro_30412",
          "column": "estimates"
        }
      ]
    }
  • list_appointments Lists appointments on the shop calendar for a date range. read

    Returns appointments in time order with customer, vehicle and the appointment type, which shows who waits at the shop and who drops off the vehicle and returns later.

    MCP calltekmetric_read → list_appointments

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/appointments

    Parameters

    Parameters: list_appointments
    NameTypeDescription
    from string required string First day, YYYY-MM-DD.
    to string string Last day, YYYY-MM-DD. Defaults to the same day.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "from": "from"
    }

    Example response

    {
      "appointments": [
        {
          "appointment_id": "ap_2201",
          "start": "2026-10-29T08:00:00",
          "customer": "Luis Ortega",
          "vehicle": "2014 Ford F-150",
          "type": "Drop off",
          "title": "Brake inspection"
        },
        {
          "appointment_id": "ap_2204",
          "start": "2026-10-29T09:00:00",
          "customer": "Dana Whitfield",
          "vehicle": "2017 Honda CR-V",
          "type": "Waiting",
          "title": "Oil change"
        }
      ],
      "next_cursor": null
    }
  • create_appointment Books an appointment on the shop calendar for a customer and vehicle. writeasks first

    Adds the appointment to the calendar and blocks that time. The customer may be told about it, so the call waits for your OK. It does not check the bay calendar for you: call list_appointments first. By default you confirm each call; you can switch that off for this tool.

    MCP calltekmetric_write → create_appointment

    REST endpointPOST https://cotlet.dev/api/v1/tekmetric/customers/{customer_id}/appointments

    Parameters

    Parameters: create_appointment
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    vehicle_id string required string Vehicle ID from get_customer.
    start string required string Start time, ISO 8601, in the shop time zone.
    title string required string What the visit is for, for example Oil change.
    type string string Waiting or Drop off.

    Example input

    {
      "customer_id": "customer_8c41d2",
      "vehicle_id": "vehicle_8c41d2",
      "start": "start",
      "title": "title"
    }

    Example response

    {
      "appointment_id": "ap_2209",
      "start": "2026-10-29T09:00:00",
      "customer": "Dana Whitfield",
      "vehicle": "2017 Honda CR-V",
      "title": "Oil change",
      "type": "Waiting",
      "status": "booked"
    }

Tekmessage customer texts3

Needs Two-Way Texting, which Tekmetric sells on Scale, and the "Can message customers" permission. Reading a thread leaves it unread.

  • list_message_threads Lists Tekmessage threads, newest first. read

    Needs Tekmessage turned on for the shop and the "Can message customers" permission for your employee. Returns the customer, the last message and whether it is unread. Reading does not mark a thread as read.

    MCP calltekmetric_read → list_message_threads

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/message-threads

    Parameters

    Parameters: list_message_threads
    NameTypeDescription
    unread_only boolean boolean Only threads with unread messages.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "threads": [
        {
          "thread_id": "th_9017",
          "customer_id": "cu_8841",
          "customer": "Dana Whitfield",
          "last_message": "Can you do the brakes but skip the filter?",
          "unread": true
        },
        {
          "thread_id": "th_9011",
          "customer_id": "cu_8870",
          "customer": "Sam Reyes",
          "last_message": "What time do you close today?",
          "unread": true
        }
      ],
      "next_cursor": null
    }
  • get_message_thread Reads the messages of one Tekmessage thread. read

    Returns messages in time order, each marked as from the customer or from the shop, with delivery state. Estimates and invoices shared from the repair order appear as links.

    MCP calltekmetric_read → get_message_thread

    REST endpointGET https://cotlet.dev/api/v1/tekmetric/threads/{thread_id}/message-thread

    Parameters

    Parameters: get_message_thread
    NameTypeDescription
    thread_id string required string Thread ID from list_message_threads.

    Example input

    {
      "thread_id": "thread_8c41d2"
    }

    Example response

    {
      "thread_id": "th_9017",
      "customer": "Dana Whitfield",
      "messages": [
        {
          "from": "shop",
          "text": "Your estimate is ready: https://example.tekmetric.test/e/abc123",
          "delivered": true
        },
        {
          "from": "customer",
          "text": "Can you do the brakes but skip the filter?",
          "delivered": true
        }
      ]
    }
  • send_message Sends a text to a customer from the shop number through Tekmessage. writeasks first

    Sends from the shop number and the text reaches a real person. Tekmetric does not allow deleting a sent message. Needs Tekmessage on and the "Can message customers" permission. By default you confirm each call; you can switch that off for this tool.

    MCP calltekmetric_write → send_message

    REST endpointPOST https://cotlet.dev/api/v1/tekmetric/customers/{customer_id}/messages

    Parameters

    Parameters: send_message
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    body string required string Message text.

    Example input

    {
      "customer_id": "cu_8841",
      "body": "Hi Dana, your CR-V is ready for pickup. We close at 6 pm. Thanks, Main Street Auto."
    }

    Example response

    {
      "message_id": "msg_55210",
      "customer": "Dana Whitfield",
      "thread_id": "th_9017",
      "status": "delivered",
      "sent_at": "2026-10-28T09:14:00Z"
    }
Encrypted, revocable

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

  • What we store

    Your signed-in Tekmetric profile, AES-256-GCM encrypted, in Finland. No password.

  • What your agent gets

    The 10 Tekmetric tools, never your cookie or login.

  • What the session sees

    What your employee role sees: board, customers, phone numbers, texts.

  • What no tool touches

    Invoices, inventory, employees, shop settings and deletes.

  • If Tekmetric signs you out

    You get an email with a sign-in link. We never type your password.

  • How to cut access

    Disable for agents, reset the browser, or remove the employee in Tekmetric.

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

Account risk

Is it against Tekmetric's terms? Account safety Yes, and texting is named.

"use any robot, spider, crawler, scraper, or other automated means or interface not provided by us to access the Platform or to extract data or to send messages through our Platform; use automated bots or other software to send messages through our Platform"
Tekmetric Terms of Service, Product & Website, read 28 Oct 2026

The same terms let Tekmetric suspend any user "for any reason, at any time", and allow use only "through specific channels provided by us". Tekmetric's own channel is the partner API, which has no texting. So the riskiest tool here is send_message: it is the exact thing the clause names. The shop also stays responsible for consent under the TCPA for every text.

How we keep your account looking like you

  • Your own employee login, signed in by you
  • One Cloud Browser with steady cookies and IP
  • Texts, estimates and appointments wait for your OK
  • Texts only to customers already in your Tekmetric
  • If Tekmetric objects, we pause the Tekmetric tools for everyone within 24 h

Text customers about their own car, not a promotion. Campaigns belong in Tekmetric Marketing, which handles opt-outs.

Tested every 12 h

What happens when Tekmetric changes? We fix the tool; your prompt stays.

between tests of the Job Board, customer and calendar tools
12 h
for a call to a Tekmetric tool paused for a fix
$0

When Tekmetric renames a board column or moves a field, the fix happens on our side and the same prompt keeps working. status.cotlet.dev checks the site, console and API every 3 minutes.

3 tools ask first

Approvals, undo and mistakes Customers hear nothing until you say so.

  1. 01 Reads the board Completed column, with customer and vehicle per card.
  2. 02 Skips the texted Checks each thread for a ready text sent today.
  3. 03 Waits for your OK Every draft text shows up in your Cotlet console.
  4. 04 Reports back Sent, skipped and why, with the thread of each.
Which Tekmetric actions can be undone
ActionUndo
Send a textNo, Tekmetric cannot delete a sent message
Share an estimateNo, the customer has the link
Create an appointmentEdit or delete it on the Tekmetric calendar
Read the board or a threadNothing to undo; threads stay unread

3 of 10 tools ask first: send_message, share_estimate and create_appointment, the three a customer may notice. The reads run at once. You can switch the wait off per tool for a scheduled run.

create_appointment does not check for a clash. The agent reads list_appointments first.

MCP call
{
  "name": "send_message",
  "arguments": {
    "customer_id": "cu_8841",
    "body": "Hi Dana, your CR-V is ready for pickup. We close at 6 pm. Thanks, Main Street Auto."
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/tekmetric/customers/cu_8841/messages \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Dana, your CR-V is ready for pickup. We close at 6 pm. Thanks, Main Street Auto."}'
Response
{
  "message_id": "msg_55210",
  "customer": "Dana Whitfield",
  "thread_id": "th_9017",
  "status": "delivered",
  "sent_at": "2026-10-28T09:14:00Z"
}

A cron job or script calls the same tools over REST at /api/v1/tekmetric, with one key and one price. Without Tekmessage or the texting permission the text tools fail, and a failed call costs nothing. The tools table lists the REST path of each tool.

Pay per call

How much does the Tekmetric MCP server cost?

About $45 a monthfor one shop writing about 10 repair orders a day, 7,760 credits. Your Tekmetric plan stays billed by Tekmetric.

A month of Tekmetric jobs for one shop, in credits
JobCallsCredits
Morning briefing: board and today's appointments2 × 26520
Chase 2 estimates waiting on authorization7 × 261,820
Car-ready texts, about 4 a day6 × 261,560
Read unread texts, answer the simple ones6 × 261,560
Book an appointment from a text or email4 × 20800
Cloud Browser, 30 days1,500
Total7,760
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Start and Grow; texting needs Scale

The month is our example of a single-location shop open 26 days. Tekmetric charges per shop, not per user or repair order: Start $199, Grow $349, Scale $439 a month billed monthly (28 Oct 2026). Dollars at the $29 pack rate.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Other options

Tekmetric MCP server on GitHub, partner apps or hosted: which to use Every other route starts with an approved API key.

Other Tekmetric MCP servers and tools, checked 28 Oct 2026
OptionWhat it doesWhere it stops
beetlebugorg/tekmetric-mcpGo server for Claude: customers, vehicles, repair orders, appointments and a service history summary. 7 stars, last commit 19 Oct 2026.Read-only, 25 records a query, needs approved partner credentials, runs on your computer.
prismware/mcp-tekmetricPython server, MIT, read-only, listed on Glama as patclarke/mcp-tekmetric.Last commit 9 May 2025, same API credentials needed.
CarlyAI assistant that uses your own Tekmetric API key for email follow-ups and morning numbers; agents from $35 a month.Waits on the same API application; follows up by email, not through Tekmessage.
Shopgenie, Steer, CinchApproved Tekmetric partners for reminders, campaigns and reactivation.Fixed marketing flows, not an agent you can ask.

A GitHub server suits a shop that already holds API credentials and only wants to ask questions. A partner app suits one marketing job. Cotlet suits a shop without a key that wants its agent to text, share estimates and book.

EU company, since 2019

Who runs Cotlet A company you can look up.

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

Tekmetric API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Tekmetric under Integrations in the console and sign in with your Tekmetric employee login in its Cloud Browser. The trial starts with your first app, with no card.

How do I connect Tekmetric to ChatGPT or Claude?

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

What can ChatGPT do in Tekmetric?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Tekmetric: chase estimates customers have not approved; text customers when the car is ready; morning briefing of the shop. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need an approved Tekmetric API application?

No. Cotlet works in your own signed-in Tekmetric account, so no API application is needed. Tekmetric sends API applicants to api.tekmetric.com and decides who gets access (checked 28 Oct 2026).

Which employee permissions does texting need?

Tekmessage must be turned on for the shop, and the employee needs the "Can message customers" permission, according to Tekmetric's help. Without Tekmessage, Tekmetric only lets staff share estimates, invoices and inspections as one-way messages, so send_message and the thread tools fail.

Does Tekmetric have webhooks?

A shop admin can add outbound webhooks under Settings > Integrations for appointment and repair order events (per Carly's guide, 30 Sep 2026). Cotlet does not listen to them. Run your agent on a schedule instead, for example list_job_board every morning.

Does it work on the Start plan?

The Job Board, customer and appointment tools work on any plan. The three text tools need Two-Way Texting, which Tekmetric includes from Scale ($439 a month billed monthly, 28 Oct 2026).

Does it work for more than one shop?

Yes, as far as your employee login reaches. Each call works in the shop your Cloud Browser has open, so name the shop in your prompt if you run several.

Is the MCP server different from the REST API?

Only in how you call it. Both carry the same 10 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Tekmetric?

No. Cotlet is independent and not affiliated with Tekmetric (Sparkplug Studios LLC).

Can I use the Tekmetric 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.

Give your agent access to Tekmetric.

Free 7-day trial with 2,000 credits, no card needed.