Bring Sandboxes
to LangChain
Learn how to connect Daytona (Dev Workspaces) to LangChain and start using 28 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Daytona (Dev Workspaces) MCP Server?
Connect your Daytona account to any AI agent to orchestrate cloud-based development environments through natural language. Daytona provides standardized, ephemeral sandboxes that can be provisioned and managed on demand.
What you can do
- Sandbox Orchestration — List, create, start, stop, and delete sandboxes with specific CPU, memory, and disk configurations.
- Snapshot Management — Create and manage snapshots to preserve environment states or activate them for new sandboxes using
create_snapshotandactivate_snapshot. - API Key Control — Manage your authentication keys directly, including listing and creating new access tokens via
list_api_keysandcreate_api_key. - Resource Scaling — Dynamically resize sandbox resources (vCPU, RAM, Disk) to match your workload requirements using
resize_sandbox. - Volume & Storage — Inspect and manage persistent volumes and snapshots for your dev environments.
How it works
- Subscribe to this server
- Enter your Daytona API Key
- Start managing your dev infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — Automate the lifecycle of test environments and sandboxes.
- Software Developers — Spin up fresh coding environments without leaving the chat or IDE.
- QA Teams — Quickly recover sandboxes from error states or fork existing environments for debugging.
Built-in capabilities (28)
Activate a snapshot
Archive a sandbox
Create a new Daytona API key
Create a new Daytona sandbox
Create a new snapshot
Create a new volume
Deactivate a snapshot
Delete an API key by name
Delete a sandbox
Delete a snapshot
Delete a volume
Fork an existing sandbox
Get details of a specific API key by name
Get details of the currently authenticated API key
Get details of a specific sandbox
Get a signed preview URL for a specific port on a sandbox
Get details of a specific snapshot
Get details of a specific volume by ID
Get details of a specific volume by name
List Daytona API keys
List all Daytona sandboxes
List all Daytona sandboxes (paginated)
List all Daytona snapshots
List all Daytona volumes
Recover a sandbox from an error state
Resize sandbox resources
Start a stopped sandbox
Stop a running sandbox
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Daytona (Dev Workspaces) through native MCP adapters. Connect 28 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Daytona (Dev Workspaces) MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Daytona (Dev Workspaces) queries for multi-turn workflows
Daytona (Dev Workspaces) in LangChain
Daytona (Dev Workspaces) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Daytona (Dev Workspaces) to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Daytona (Dev Workspaces) in LangChain
The Daytona (Dev Workspaces) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 28 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Daytona (Dev Workspaces) for LangChain
Every tool call from LangChain to the Daytona (Dev Workspaces) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I change the resources of an existing sandbox?
Yes, you can use the resize_sandbox tool to update the CPU, memory, or disk size of a specific sandbox by providing its ID or name.
How do I create a new environment with a specific Docker image?
Use the create_sandbox tool and provide the image parameter with the desired Docker or OCI image name.
What should I do if a sandbox is in an error state?
You can use the recover_sandbox tool to attempt to restore a sandbox from an error state back to a functional one.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
LiftedWork
6 toolsConnect job seekers with employment opportunities through a platform that matches skills to openings and tracks applications.
Notion
12 toolsManage your Notion workspace, databases, and pages via AI.
Google Maps
4 toolsEmpower location intelligence via Google Maps — perform geocoding, search millions of places, retrieve rich venue details, and calculate directions directly from any AI agent.
Duolingo
8 toolsTrack language learning progress on Duolingo — view profiles, streaks, XP, leaderboards and dictionary hints.