Twin Browser
Get an API key
PlatformOverviewHow it worksAll toolsREST APIMCP serverIntegrationsDocs
CapabilitiesSemantic dispatch cacheDeterministic replayCross-tenant skill corpusToken-efficient DOMHuman-in-the-loopLive view & videoCredential vaultOverviewSolutions
SolutionsAll use casesAI agentsRPA replacementQA & test automationData extraction
ResourcesGuidesGlossaryBlogCompareFAQStatus
Pricing
Log in

Glossary · Integration

MCP server

A Model Context Protocol server exposing the browser layer as 35 tools to clients like Cursor, Claude Desktop, Claude Code and Cline.

Start freeAll terms

What is mcp server?

An MCP server implements the Model Context Protocol so any compatible client can discover and call its tools over a standard interface. Twin's server runs over stdio and registers 35 tools across six groups — core execution and skills, async jobs, observation and data, monitors, sessions and credentials, and recording — so an agent in an editor can drive a real browser with no bespoke integration code.

Why it matters

MCP is becoming the universal socket between agents and tools. Registering the server means your editor or desktop agent gets a browser, the semantic cache and the replay economics by adding one entry to a config file, rather than an SDK per client.

Related terms

See it in context

Back to the full glossary

Put your agent to work. Keep the decision.

Give your agent a real browser, authorize the accounts it may use, and keep control of every step. Repeated runs compile into skills that replay without a model.

Start freeSee pricing