[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Tekmetric API and MCP server: Let your AI agent work your Tekmetric Job Board. > 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. 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. [MCP setup](https://cotlet.dev/integrations/tekmetric-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/tekmetric-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Tekmetric - Page: https://cotlet.dev/integrations/tekmetric-api-mcp-server ## What can you automate in Tekmetric? - 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 ## Does Tekmetric have an MCP server or an API? - 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. | What you need | Tekmetric API | GitHub MCP server | Cotlet | |---|---|---|---| | 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](https://api.tekmetric.com/), [Tekmetric integrations](https://www.tekmetric.com/integrations), [Tekmetric pricing](https://www.tekmetric.com/pricing), [Tekmetric Terms of Service](https://www.tekmetric.com/legal/site-product-terms) ## How does Cotlet connect to Tekmetric? 1. **Sign in to Tekmetric.** 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 Tekmetric password, and no text, estimate or appointment reaches a customer until you approve it. ## 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. **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. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as a new MCP server or connector in your agent. 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, 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: Tool: tekmetric_write ``` ## 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 | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Reads one repair order with its jobs, parts and authorization state. Use `get_repair_order` in your configured business report. | | Make | HTTP > Make a request | Lists appointments on the shop calendar for a date range. Use `list_appointments` in your configured business report. | | Python or Node.js | REST API | Reads the messages of one Tekmessage thread. Use `get_message_thread` in your configured business report. | Send `Authorization: Bearer ` 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](https://cotlet.dev/integrations/tekmetric-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Tekmetric API endpoints and MCP tools ### Job Board and repair orders 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 repair orders** (`list_job_board`, read): Lists repair orders on the Job Board, by column. - **Get a repair order** (`get_repair_order`, read): Reads one repair order with its jobs, parts and authorization state. - **Share an estimate** (`share_estimate`, write, asks first): Sends the estimate of a repair order to the customer, like Share Estimate in the app. ### Customers and appointments Search by name, phone or email; the vehicle ID from a customer record is what an appointment is booked on. - **Search customers** (`list_customers`, read): Finds customers by name, phone number or email. - **Get a customer** (`get_customer`, read): Reads a customer with their phone numbers, vehicles and repair orders. - **List appointments** (`list_appointments`, read): Lists appointments on the shop calendar for a date range. - **Create an appointment** (`create_appointment`, write, asks first): Books an appointment on the shop calendar for a customer and vehicle. ### Tekmessage customer texts Needs Two-Way Texting, which Tekmetric sells on Scale, and the "Can message customers" permission. Reading a thread leaves it unread. - **List customer text threads** (`list_message_threads`, read): Lists Tekmessage threads, newest first. - **Read a text thread** (`get_message_thread`, read): Reads the messages of one Tekmessage thread. - **Text a customer** (`send_message`, write, asks first): Sends a text to a customer from the shop number through Tekmessage. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/tekmetric-api-mcp-server#tools ## 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](https://cotlet.dev/security.md)). We have no SOC 2 report and no third-party pentest yet. ## Is it against Tekmetric's terms? Account safety > 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](https://www.tekmetric.com/legal/site-product-terms) 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. ## What happens when Tekmetric changes? - **12 h** between tests of the Job Board, customer and calendar tools - **$0** for a call to a Tekmetric tool paused for a fix 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](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the board.** Completed column, with customer and vehicle per card. 2. **Skips the texted.** Checks each thread for a ready text sent today. 3. **Waits for your OK.** Every draft text shows up in your Cotlet console. 4. **Reports back.** Sent, skipped and why, with the thread of each. | Action | Undo | |---|---| | Send a text | No, Tekmetric cannot delete a sent message | | Share an estimate | No, the customer has the link | | Create an appointment | Edit or delete it on the Tekmetric calendar | | Read the board or a thread | Nothing 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. ## How much does the Tekmetric MCP server cost? **About $45 a month** for one shop writing about 10 repair orders a day, 7,760 credits. Your Tekmetric plan stays billed by Tekmetric. | Job | Calls | Credits | |---|---|---| | Morning briefing: board and today's appointments | 2 × 26 | 520 | | Chase 2 estimates waiting on authorization | 7 × 26 | 1,820 | | Car-ready texts, about 4 a day | 6 × 26 | 1,560 | | Read unread texts, answer the simple ones | 6 × 26 | 1,560 | | Book an appointment from a text or email | 4 × 20 | 800 | | Cloud Browser, 30 days | | 1,500 | | Total | | 7,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. ## Tekmetric MCP server on GitHub, partner apps or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [beetlebugorg/tekmetric-mcp](https://github.com/beetlebugorg/tekmetric-mcp) | Go 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-tekmetric](https://github.com/prismware/mcp-tekmetric) | Python server, MIT, read-only, listed on Glama as patclarke/mcp-tekmetric. | Last commit 9 May 2025, same API credentials needed. | | [Carly](https://www.usecarly.com/blog/tekmetric-api/) | AI 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, Cinch | Approved 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. ## Who runs Cotlet 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 AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) 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](https://cotlet.dev/about.md) 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.