Templa developer resources
Templa offers website templates and custom website design. Public buyers and recommendation agents can browse the catalog, product previews and policies without API credentials. The administrative integration below is for an authorized store owner, not customer checkout automation.
Administrative HTTP API
POST https://templa.app/api/v1/mcp (or the compatible /api/mcp alias) with Content-Type: application/json and Authorization: Bearer YOUR_OWNER_TOKEN. Send an action envelope, for example:
{"action":"list_products","args":{"published":true,"limit":10,"offset":0}}
Success: {"ok":true,"data":...}. Failures retain the legacy error string and also include code, message, hint, status, api_version and docs. See the ApiError schema and versioning policy. The documented read-only subset covers list_products, get_product and list_categories. All still require an owner token; published:true limits a catalog query, but does not reduce the token's authority. No public buyer SDK or anonymous catalog API is advertised here.
MCP transport
The existing Templa MCP integration uses a local stdio bridge built with the Model Context Protocol SDK. In the store source repository, install the mcp package dependencies, then configure your client to run npx tsx with the absolute path to mcp/src/index.ts. Provide STORE_BASE_URL=https://templa.app and MCP_API_TOKEN through the client's protected environment configuration. The bridge forwards tool actions to the HTTP API. Do not point a remote MCP client directly at /api/mcp: the HTTP action envelope is not MCP transport. Obtain source and access from the store owner; there is no publicly hosted SDK download implied by these instructions.