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.

Trace one tool

The existing external-transport test starts with this configuration:

{
	"transport": "external",
	"method": "GET",
	"baseUrl": "https://api.example.test",
	"endpoint": ""
}

This example and the source links below require private-beta repository access. Without it, GitHub returns 404. See Release status for source availability, or Getting started to try the Cloud beta.

Run it from a source checkout:

bun run --cwd apps/mcp test:run src/mcp/handler-external.test.ts -t 'allows OpenAPI root path'

The test mocks the upstream response and verifies { "ok": true }. It needs no provider account and does not install a live integration. Follow the test (apps/mcp/src/mcp/handler-external.test.ts) into ToolHandler (apps/mcp/src/mcp/handler.ts) to see execution, then the tool schema (packages/db/src/schema/tools.ts) for persisted configuration. Live tools also require tenant-owned connection credentials and an explicit scope decision; see the MCP agent guide in the source tree (apps/mcp/AGENTS.md).