MCP app platform

Tedix uses the Model Context Protocol (MCP) as a standard way to connect workers and compatible clients to tools, prompts, resources, and interactive application components.

Tenant-scoped connections

A shared application definition can be connected separately for each organization. Credentials and policy remain tenant-scoped, so installing the same integration for two customers does not mix their data or authority.

Configured at runtime

Tedix applications are configured from durable metadata. Tool schemas, required scopes, identity rules, and UI resources can evolve without creating a separate Worker deployment for every tenant.

MCP and durable work

MCP calls can participate in durable Tedix work:

• tools are attributed to the worker and run that used them;
• long-running operations can return durable task identifiers;
• policies can require confirmation before sensitive mutations;
• results can be attached to rationale and audit records.

MCP provides the connection surface. Tedix adds tenant identity, governance, durability, and evidence around that surface.