TME MCP Server
Enables searching and retrieving detailed information on electronic components from TME, including pricing, stock, datasheets, and delivery estimates.
README
TME MCP Server
A Model Context Protocol server for the TME electronic components API, built with FastMCP. Docker-first, designed for the Docker MCP Toolkit.
TME is a major European electronic components distributor based in Poland. Provides 13 tools: product search, details, pricing (with volume tiers), stock levels, datasheets, delivery time, and URL generation.
Prerequisites
- TME API credentials -- Register at developers.tme.eu, create an application to get your App Token and App Secret
- Docker (recommended) or Python 3.10+
- Docker MCP Toolkit -- included with Docker Desktop (requires MCP Toolkit support)
Project Structure
tme-mcp/
├── mcp_app.py # Shared FastMCP instance
├── tme_mcp_server.py # Main server -- all 13 tools
├── tme_auth.py # HMAC-SHA1 signing + API request helper
├── Dockerfile # Docker image with embedded metadata
├── pyproject.toml # Project metadata
└── LICENSE # MIT
Quick Start -- Docker MCP Toolkit
The recommended way to run this server. The Docker MCP gateway manages the container lifecycle, injects secrets, and exposes tools to MCP clients like Claude Code or Claude Desktop.
1. Build the Docker image
git clone https://github.com/simon-77/tme-mcp.git
cd tme-mcp
docker build -t tme-mcp:latest .
2. Create a custom catalog
The gateway discovers servers through catalog files. Create one at ~/.docker/mcp/catalogs/custom.yaml (or add to an existing one):
version: 3
name: custom
displayName: Custom MCP Servers
registry:
tme:
description: TME electronic components -- search, pricing, stock, datasheets
title: TME
type: server
image: tme-mcp:latest
secrets:
- name: tme.TME_APP_TOKEN
env: TME_APP_TOKEN
- name: tme.TME_APP_SECRET
env: TME_APP_SECRET
env:
- name: TME_COUNTRY
value: "PL"
- name: TME_LANGUAGE
value: "EN"
- name: TME_CURRENCY
value: "PLN"
tools:
- name: search_products
- name: autocomplete
- name: get_categories
- name: search_parameters
- name: get_products
- name: get_parameters
- name: get_product_files
- name: get_similar_products
- name: get_prices
- name: get_stocks
- name: get_prices_and_stocks
- name: get_delivery_time
- name: generate_tme_url
prompts: 0
resources: {}
Change the env values to match your locale (e.g., AT/EN/EUR for Austria).
3. Register the catalog and enable the server
docker mcp catalog import ~/.docker/mcp/catalogs/custom.yaml
docker mcp server enable tme
Re-run catalog import whenever you modify custom.yaml.
4. Set secrets
docker mcp secret set tme.TME_APP_TOKEN
docker mcp secret set tme.TME_APP_SECRET
You'll be prompted to enter each value. Secret names must be prefixed with the server name (tme.).
5. Connect an MCP client
docker mcp client connect claude-code
This adds the gateway to your project's .mcp.json:
{
"mcpServers": {
"MCP_DOCKER": {
"command": "docker",
"args": ["mcp", "gateway", "run"],
"type": "stdio"
}
}
}
When the MCP client starts, the gateway launches the tme-mcp:latest container, injects secrets as environment variables, and proxies tool calls.
Rebuilding after changes
docker build -t tme-mcp:latest .
# Restart your MCP client to pick up the new image
No need to re-import the catalog or re-set secrets -- just rebuild and restart.
Alternative: Docker standalone
Run the container directly without the MCP Toolkit. You manage secrets and lifecycle yourself.
docker build -t tme-mcp .
docker run --rm -i \
-e TME_APP_TOKEN="your-token" \
-e TME_APP_SECRET="your-secret" \
-e TME_COUNTRY=AT \
-e TME_CURRENCY=EUR \
tme-mcp:latest
.mcp.json for MCP clients:
{
"mcpServers": {
"tme": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-e", "TME_APP_TOKEN",
"-e", "TME_APP_SECRET",
"-e", "TME_COUNTRY=AT",
"-e", "TME_CURRENCY=EUR",
"tme-mcp:latest"
]
}
}
}
When using -e TME_APP_TOKEN (without =value), Docker passes through the value from your shell. Make sure to export them first:
export TME_APP_TOKEN="your-token"
export TME_APP_SECRET="your-secret"
Locale env vars are optional -- defaults are PL/EN/PLN (see Configuration).
Alternative: Standalone (pip)
Run without Docker. Requires Python 3.10+.
git clone https://github.com/simon-77/tme-mcp.git
cd tme-mcp
pip install .
cat > .env <<EOF
TME_APP_TOKEN=your-token
TME_APP_SECRET=your-secret
TME_COUNTRY=AT
TME_LANGUAGE=EN
TME_CURRENCY=EUR
EOF
python tme_mcp_server.py
.mcp.json for MCP clients:
{
"mcpServers": {
"tme": {
"command": "python",
"args": ["tme_mcp_server.py"],
"cwd": "/path/to/tme-mcp",
"env": {
"TME_APP_TOKEN": "your-token",
"TME_APP_SECRET": "your-secret",
"TME_COUNTRY": "AT",
"TME_CURRENCY": "EUR"
}
}
}
}
Locale env vars are optional -- defaults are PL/EN/PLN (see Configuration).
Tools
Search & Browse
| Tool | Description |
|---|---|
search_products |
Search products by keyword or part number, paginated |
autocomplete |
Type-ahead suggestions for a search phrase |
get_categories |
Browse the product category tree |
search_parameters |
Get available filter parameters for a category |
Product Details
| Tool | Description |
|---|---|
get_products |
Full product details for up to 50 symbols |
get_parameters |
Technical specifications/attributes for up to 50 symbols |
get_product_files |
Datasheets, photos, and documents for up to 50 symbols |
get_similar_products |
Find alternative/similar parts |
Pricing & Stock
| Tool | Description |
|---|---|
get_prices |
Pricing with volume discount tiers for up to 50 symbols |
get_stocks |
Inventory levels for up to 50 symbols |
get_prices_and_stocks |
Combined pricing and stock in a single call |
Other
| Tool | Description |
|---|---|
get_delivery_time |
Estimated delivery time for up to 50 symbols |
generate_tme_url |
Generate a product page URL for a TME symbol |
Configuration
All settings are controlled via environment variables. In Docker MCP Toolkit mode, these are set in the catalog env block or as secrets. In standalone mode, use a .env file.
| Variable | Default | Description |
|---|---|---|
TME_APP_TOKEN |
(required) | API token from developers.tme.eu |
TME_APP_SECRET |
(required) | HMAC secret for request signing |
TME_COUNTRY |
PL |
Country code (e.g. AT, DE, PL) |
TME_LANGUAGE |
EN |
Language code |
TME_CURRENCY |
PLN |
Currency code (e.g. EUR, PLN) |
Authentication
TME uses HMAC-SHA1 per-request signing (not OAuth2). Each API call is individually signed using your App Secret. No token refresh or caching needed -- this means credentials never expire and there are no session/token issues.
Troubleshooting
Gateway shows 0 tools: Verify the tools list in your catalog matches the tool names in the Tools section above.
Signature errors: If searches with special characters fail, ensure you're running the latest image. Earlier versions had a signing bug with spaces in search queries.
Catalog changes not taking effect: Re-run docker mcp catalog import ~/.docker/mcp/catalogs/custom.yaml after editing the catalog file. Restart your MCP client afterward.
Secret errors: Verify your credentials with docker mcp secret list. Secret names must be prefixed: tme.TME_APP_TOKEN, not TME_APP_TOKEN.
License
MIT License -- see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.