Overview
What is MCP Tekmetric?
MCP Tekmetric is a Model Context Protocol (MCP) server that enables AI assistants to interact with Tekmetric data in a read-only manner. It is designed for users who want to automate or retrieve information from their Tekmetric instance through an AI interface.
How to use MCP Tekmetric?
Obtain a Tekmetric API key and set it as the TEKMETRIC_API_KEY environment variable. Run the server locally with uvicorn mcp_tekmetric.servers.main:asgi_app --host 0.0.0.0 --port 8080 or via Docker using docker run -e TEKMETRIC_API_KEY=your_key -p 8080:8080 mcp-tekmetric. Connect your AI assistant (e.g., VS Code Copilot) by configuring an SSE server at http://localhost:8080/sse.
Key features of MCP Tekmetric
- Read-only access to Tekmetric data
- Local Python or Docker deployment
- SSE transport for MCP connections
- Health check endpoint (
/healthz)
Use cases of MCP Tekmetric
- Check details of upcoming appointments
- Retrieve shop contact information
- Get the current status of a repair order
FAQ from MCP Tekmetric
What is required to authenticate with MCP Tekmetric?
You need a Tekmetric API key, which you obtain from your Tekmetric account settings. Set it as the TEKMETRIC_API_KEY environment variable.
Does MCP Tekmetric support write operations?
Currently, this integration supports read-only actions only. Your AI can retrieve information but cannot create or modify data.
How do I run MCP Tekmetric?
You can run it locally using Python (install dependencies with pip install -e . and start with uvicorn) or with Docker (docker build then docker run, passing your API key).
What transport does MCP Tekmetric use?
The server uses SSE (Server-Sent Events) transport, exposed via an HTTP endpoint at http://localhost:8080/sse.
How can I verify the server is running?
Send a GET request to http://localhost:8080/healthz. A successful response returns {"status": "ok"}.
