MDPModel Drive Protocol

The ultimate solution for connecting models with everything.

Quick Start

Playground

JavaScript SDK

Abstract diagram of MDP connecting models and runtimes

Structured Tool Catalog

Read the bridge surface by individual tool instead of scanning one long aggregate page.

See tools

Split Client APIs

Connection setup and external interfaces are separated so transport details are easier to navigate.

See APIs

Protocol Reference

Jump from server behavior into the underlying protocol lifecycle and message model.

See protocol

For Browsers, IDEs, Apps, and Local Agents

Let models call runtime capabilities directly.

You do not need to rebuild browsers, IDEs, apps, or local processes as services. Register the capability, then expose it through one fixed bridge.

1stable bridge for every host

3path types: endpoints / prompts / skills

2transport modes: WebSocket / HTTP loop

Pick A Path

Pick the entry point, then go deeper only when you need to.

Start Fast

Quick Start

The fastest end-to-end path.

Integrate Precisely

Tools

Browse each bridge tool as its own reference page.

Talk to the Runtime

APIs

Read connection setup separately from the external interfaces.

Embed MDP

JavaScript SDK

Embed MDP into browsers, local processes, or custom runtimes.

Try It Live

Playground

Try connections and inspect path behavior.

Typical Flow

From runtime to agent in four steps.

Configure the bridge

Start the server CLI and configure it in your MCP tool.

Connect runtimes

Connect one or more clients.

Register path catalogs

Call them through MCP

Use them from any MCP-capable tool.

Good Fits

Best when the capability must stay inside the runtime that owns it.

Browser and extension session capabilities

IDE features tied to local workspace state

App-local, device-local, or process-local actions

Local agent or backend flows exposed through MCP

Need exact formats? Go to Tools, APIs, Protocol Reference, or Playground.