Overview

The connector acts as a thin translation layer between Claude and the warenquelle backend API. It receives MCP tool calls, translates them into REST requests, and returns structured JSON responses.

Claude
  ↓  MCP / Streamable HTTP
mcp.warenquelle.store  (Vercel Edge Function)
  ↓  HTTPS + Bearer Token
api.warenquelle.store/mcp/*  (PHP REST endpoints)
  ↓
warenquelle Database

Technical Specifications

PropertyValue
TransportStreamable HTTP (MCP spec 2024-11-05)
MCP Server URLhttps://mcp.warenquelle.store/mcp
Auth typeOAuth 2.0 with Authorization Code + PKCE
RuntimeVercel Edge Functions
BackendPHP 8.x on dedicated server
Data accessRead-only
Multi-tenantYes – one API key per merchant/market

OAuth Endpoints

EndpointURL
Well-known https://mcp.warenquelle.store/.well-known/oauth-authorization-server
Authorization https://mcp.warenquelle.store/authorize
Token https://mcp.warenquelle.store/token

Multi-tenant Design

Each API key is tied to a specific MERCH_UUID and MARKET_UUID stored in the wq_mcp_api_keys table. All backend queries are automatically scoped to the authenticated merchant – it is not possible to access another merchant's data.

Read-only All tools have readOnlyHint: true and destructiveHint: false. No data is written, modified, or deleted.