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)

Related MCP server: Nexar MCP Server

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

Product Details

Pricing & Stock

Other

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.

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.