A workshop manager types into his chat window: “Which vehicles have a vehicle inspection appointment in the next 14 days?” – Seconds later, the complete list appears, including license plate numbers, customer names, and phone numbers. No report generator, no filters, no Excel exports. This is exactly what’s possible today when an auto repair shop uses an open platform. The use of MCP and API for auto repair shops with CATAMA Software transforms workshop data into a directly queryable, intelligent knowledge base—without the data ever leaving the shop’s own server.
The reality in many workshops has been quite different so far: a parts catalog here, accounting there, a shop floor system next to it, and a separate workshop scheduler on top of that. These are siloed solutions that must be laboriously integrated by hand. CATAMA brings all these elements together into a cohesive system via open interfaces —and is now taking a decisive step forward: through the Model Context Protocol (MCP), the software is becoming AI-enabled.
Key Takeaways
- CATAMA is API-first: The REST API allows you to programmatically read and write invoices, inventory, appointments, and master data.
- The Model Context Protocol (MCP) makes every CATAMA instance AI-enabled—workshop data can be accessed via voice commands using assistants like Claude.
- Security by Design: Read-only operations, predefined tool parameters, no free SQL—data sovereignty remains with the organization.
- With over 26 interfaces to parts catalogs, accounting, e-commerce, and vehicle data—no more duplicate data entry.
- Future-proof: open standards (REST, JSON-RPC 2.0, MCP Streamable HTTP) instead of proprietary dead ends.
What is MCP—and why is it relevant for repair shops?
The Model Context Protocol is a standardized interface that allows AI assistants to access business data in a secure and structured manner. Instead of granting AI direct access to databases (which is dangerous and uncontrollable), MCP defines clear, vetted tools that the assistant is permitted to use.
For automotive service shops, this represents a quantum leap: Each CATAMA instance also serves as its own MCP server under /api/mcp. No additional cloud storage, no external data pool—the workshop retains full control over its data.
Practical benefits in everyday workshop use
Questions that arise in day-to-day operations can now be asked in natural language:
- “Which customers have birthdays in the next 10 days?”
- “Show me the complete service history for license plate M-AB 1234.”
- “What is the annual revenue of Kunde Müller GmbH?”
- "Which vehicles are due for a vehicle inspection next month?"
Instead of creating reports, setting filters, or scrolling through lists, you simply ask the question—and get a structured answer.
Security by Design
The AI never has unrestricted access. It only translates free-form text into predefined, verified tool parameters—in read-only mode. Writing operations are strictly prohibited.
The concept thus meets two key requirements for automotive service shops when using MCP and API: convenience and control. The AI acts like an extremely fast, error-free assistant—but it can’t break anything.
An Overview of CATAMA MCP Tools
CATAMA provides a wide range of clearly defined tools via the MCP interface. Each tool has a specific purpose and fixed parameters:
| Tool | Function |
|---|---|
customer_search |
Filter customers (birthday, location, ZIP code, VIP status, follow-up, vehicle inventory) |
customer_get |
Customer details, including revenue and assigned vehicles |
customer_revenue |
Sales Analysis (net, by year, excluding credits) |
vehicle_get |
Vehicle details: VIN, license plate, chassis number/transmission number, mileage, vehicle inspection, maintenance, warranty |
customer_invoices_list |
Invoice and Service History by Customer |
vehicle_invoices_list |
Complete order history for each vehicle |
It is precisely these tools that make the difference: A question such as “Which VIP customers within a 50-kilometer radius haven’t placed an order in over 12 months?” can be formulated using the available building blocks—without the AI having to improvise.
Anyone who wants to understand the underlying data models—such as how HSN, TSN, and KBA key numbers are structured—will find clearly documented fields for each in CATAMA.
Practical Implementation
Theory is one thing; practical implementation is another. This demonstrates just how mature the use of MCP and API is for automotive businesses using CATAMA.
Claude Desktop via mcp-remote-Bridge
The most common way to get started: Claude Desktop is connected to your own CATAMA instance via the mcp-remote bridge. Once you've entered the necessary information in the configuration file, you can use the standard chat window to query the workshop data.
Authentication is handled via the existing CATAMA API token—either as a bearer header or a parameter. No new access management, no additional accounts. Anyone already using API integrations already has the token.
Built-in CATAMA Assistant
Even more convenient: The CATAMA interface includes an input field that provides AI responses via webhook. The advantage: The MCP token never leaves the browser—the request is made server-to-server. For many workshops, this is exactly the convenience they’re looking for: AI power within their familiar system, without the need for external tools.
n8n Orchestration
Those who need more complex workflows—such as “Sending a list of all vehicles due for HU via email to the dispatch department every Monday”—can use n8n as an orchestrator. The open protocols (JSON-RPC 2.0, MCP Streamable HTTP) are vendor-neutral and future-proof.
Practical example: The workshop manager at a medium-sized company opens Claude in the morning and asks, “Which vehicles are due for their annual inspection in the next 14 days and belong to customers I haven’t seen in over six months?” The AI responds
vehicle_getwith an HU filter, thencustomer_invoices_listfor activity reconciliation and generates a neatly formatted table. The scheduler calls the customers—before even having their first cup of coffee.
The REST API: Getting Data In and Out
While MCP serves as the AI front end, the traditional REST API remains the backbone of all integrations. It allows you not only to read data but also to write it—for example, to book appointments, create items, or retrieve invoices. For more background information, see the overview of the automotive invoicing program with DATEV and e-invoicing.
Orders and Invoices
The Endpoint /api/invoices/list provides reports by time period, status, and customer—including credit memos. Perfect for external reporting, business intelligence tools, or custom dashboards. Those who consolidate monthly KPIs from multiple locations can skip the manual export process.
Stock and Item Inventory
About /api/inventory You can check inventory levels, create items, and maintain accurate master data via lookup endpoints. This is particularly valuable for businesses with an online store or multiple warehouse locations.
Workshop dates
With /api/workshop-appointments available slots can be identified and appointments booked automatically—for example, through an online booking form on the website. Anyone who intelligent workshop planner can use the API to seamlessly integrate it into their own channels.
The following applies in all cases:
- Token-based authentication (Bearer)
- Clear field references with data types
- Defined error responses (HTTP codes plus structured JSON errors)
- Version-stable endpoints
The Integration Ecosystem: 26+ Interfaces
The use of MCP and API for automotive businesses is just part of the story. CATAMA also offers an ecosystem with over 26 ready-to-use integrations with key industry partners. The interface overview provides a summary.
Parts catalogs
This is where CATAMA really shines:
- Stakis / Stahlgruber – including seamless Stakis 4.0 integration
- WMKat, PartsFinder, Bullkat, Atevis, Dolphin
- AAG, Easypart, Matthies, Auteon, PV Kompass, ATP Plus
Catalog access via VIN, KBA, or license plate; shopping cart import directly into the order—no need for duplicate data entry.
Vehicle Data and Cost Estimation
- DAT / SilverDAT – Damage Estimation, Parts Prices, Partslink Import
- Audaris, RepDoc, Glavista
Accounting
- lexoffice – Full integration with invoice and customer synchronization
- DATEV Export for Invoices, Credit Memos, and Goods Receipts
E-commerce and Communication
- Shopware 6 – Product, Order, and Category Sync
- Spryng SMS, SMTP/Email Templates
- Google Calendar – Two-way calendar synchronization
CATAMA Network
For multi-location businesses, multiple CATAMA instances can be networked—with master data, inventory, and orders organized centrally, decentrally, or in a hybrid manner.
Tangible benefits for automotive businesses
The question on every owner’s mind: What are the concrete benefits? Is investing in open interfaces justified?
Time savings through automation
No more duplicate data entry. Parts from the catalog are automatically added to the order, appointments from the online form are automatically entered into the workshop scheduler, and invoices are automatically sent to accounting. For detailed examples, see the article “How Auto Repair Shops Save Time and Money with CATAMA.”
Fewer mistakes
Automatic product mapping, price calculation, and VAT logic instead of manual data entry. Every typo in a product code or price costs money—sometimes hundreds of euros per transaction. APIs eliminate this source of error.
Greater customer loyalty
Proactive customer outreach is becoming a breeze: birthdays, vehicle inspection due dates, service intervals—all retrieved in seconds via AI queries, rather than sifting through filtered lists. Setting up automatic appointment reminders completes the process.
Data sovereignty
Data remains within your own instance—AI accesses it only in read-only mode and under strict controls. No data is shared with third parties. In an era of growing concern for data protection, this is a factor that should not be underestimated. For more details, see the information on data centers and data security.
Future-proof
Open standards—REST, JSON-RPC 2.0, MCP—instead of proprietary dead ends. If you integrate today, you won’t have to rebuild everything from scratch in five years when the next AI provider enters the market.
Comparison Table: Traditional Software vs. CATAMA with API/MCP
| Requirement | Classic workshop software | CATAMA with API/MCP |
|---|---|---|
| Retrieve data | Reports, Filters, Excel Export | Question in natural language |
| Parts Catalog Integration | Manual entry or individual import tools | 12+ catalogs via shopping cart import |
| Accounting | CSV Export, Post-processing | Live sync with lexoffice/DATEV |
| Online appointments | Separate channel | Automatic booking via API |
| Use of AI | Not provided for | MCP-compatible, ready to use |
| Data sovereignty | Often cloud-only | Dedicated instance, controlled AI access |
Sample workflows from everyday workshop operations
Three specific scenarios illustrate how the building blocks can be combined.
Workflow 1: Tire Change Season
Ahead of the next peak season for tire changes, the dispatcher asks, “Which customers have tires in storage with us but haven’t booked an appointment yet?” The AI combines the customer list, stored tire sets, and available appointment slots—and the call list is ready.
Workflow 2: HU Reminder
The REST API retrieves all vehicles due for a vehicle inspection within the next 30 days. An n8n workflow uses this data to generate personalized text messages via Spryng and bookable slots from the workshop scheduler. The customer replies with “Appointment 2”—and the appointment is set.
Workflow 3: Keeping an Eye on Management
Every morning, the managing director opens the CATAMA Assistant: “How did last week’s revenue compare to the week before, broken down by workshop and parts sales?” The answer comes in seconds—without a BI tool, without Excel.
Getting Started: How to Get Started with the API/MCP
If you've never worked with APIs before, you should take it one step at a time.
- Enable API tokens – in the CATAMA instance under API settings.
- Initial read-only tests —for example, using tools like Postman or directly in the browser to retrieve invoice lists.
- Try the MCP connection with Claude Desktop – set it up once, and you’re ready to go.
- Basic automation —such as syncing appointments with Google Calendar.
- Scalability – n8n workflows, custom dashboards, store integration.
For most businesses, making the switch is worthwhile once they’ve gained some initial experience with an automotive workshop ERP system. Those who already maintain well-structured data in CATAMA have done their homework.
Conclusion
CATAMA isn’t just management software—it’s an open platform. Built with an API-first approach, it’s now also AI- and MCP-ready in operation. Auto shops that rely on open interfaces today can automate routine tasks and free up time for what really matters: their core business with customers and vehicles.
For automotive businesses, using MCP and API is not just a technical playground for tech-savvy individuals, but a tangible competitive advantage. Those who can retrieve data using voice commands instead of clicking through reports work faster. Those who automate the flow of parts, appointments, and invoices make fewer mistakes. Those who use open standards stay future-proof.
Next Steps
- Request a demo: View the plan that best suits your business on the CATAMA product overview.
- Try it for free: Sign up to launch a free trial instance.
- View API documentation: Every customer can access the complete API reference through their personal account.
- Test the MCP connection to Claude: Configure it once—and your workshop database becomes a talking knowledge base.
- Advice: If you have specific requirements, we recommend contacting the CATAMA team directly.
The market is changing. AI assistants will become the standard interface for business data in the coming years. Those who set the course now will be participants—not spectators—in the first real AI boom in the automotive repair industry.
