Sandbox MCP integration
Run JavaScript, Python, or shell commands in an isolated managed sandbox. Uses workspace integration settings for persistence and filesystem mounting.
Sign in and add Sandbox in Apps. No Sandbox account is required.
Tools
| Name | Description |
|---|---|
run_codeExecute JavaScript, Python, or shell commands in an isolated managed runtime. Uses the workspace integration sandbox policy for persistence and storage. | Execute JavaScript, Python, or shell commands in an isolated managed runtime. Uses the workspace integration sandbox policy for persistence and storage. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('advanced-code', 'run_code', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'advanced-code',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Sandbox MCP server through Weavz?
Yes. Add the Sandbox integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 1 Sandbox actions.
What can an AI agent do with Sandbox?
Available actions include Run Code. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Sandbox to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Sandbox, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Sandbox through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Sandbox require?
This catalog integration does not require a stored external account connection. Provider terms, rate limits and tool-specific inputs can still apply.
How do I review sensitive Sandbox actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Sandbox?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
Connect Sandbox in minutes
Get 20,000 free action executions every month. No credit card required.