Glossary · Distribution

MCP server

A Model Context Protocol endpoint that exposes Twin as agent tools (run, compile_skill, run_skill) to MCP clients like Cursor, Claude Desktop, Claude Code, and Cline.

What is mcp server?

An MCP server implements the Model Context Protocol so any compatible AI client can discover and call its tools over a standard interface. Twin’s MCP server exposes the execution layer as tools — `run` (execute a goal), `compile_skill`, and `run_skill` — so an agent in Cursor, Claude Desktop, Claude Code, or Cline can drive a real browser without bespoke integration code.

Why it matters

MCP is becoming the universal socket between agents and tools. Shipping a Twin MCP server means your IDE or desktop agent gets a browser — plus the semantic cache and replay economics — by adding one server, instead of wiring an SDK per client.

See it in context: read how Twin compiles and replays a run, follow the cost-cutting guide, or browse use cases and comparisons.

Put your agent to work

Give your agent a real browser, connect the accounts you authorize, and keep control of every step. Repeated runs compile into skills that replay at near-zero cost.