Local stdio MCP Server Examples
Copy common stdio command, args, and environment variable settings for Playwright, filesystem, and Stripe MCP servers.
Use stdio MCP servers when the server runs as a local command inside each target CloudCLI environment. In CloudCLI, add these from Settings > Configuration > MCP, choose stdio, then enter the command, arguments, and environment variables.
A stdio MCP server starts when the agent client starts. If you add or edit one, restart the agent session before testing it.
CloudCLI also includes Browser Use for inspecting real web pages, verifying UI behavior, and handing control back to you for login or approval steps. Use Playwright MCP only when you specifically need browser tools exposed through MCP.
Playwright MCP
Playwright MCP lets agents inspect and interact with web pages using browser automation and accessibility snapshots.
| Field | Value |
|---|---|
| Name | playwright |
| Transport | stdio |
| Command | npx |
| Arguments | @playwright/mcp@latest |
| Environment variables | Usually none |
CloudCLI modal values:
Command
npx
Arguments
@playwright/mcp@latestUse Playwright MCP when agents need MCP-native browser automation tools. For everyday CloudCLI page inspection and UI verification, start with Browser Use.
Filesystem MCP
The filesystem server gives agents file read/write tools within explicitly allowed directories. CloudCLI environments already give agents project filesystem access through their normal tools, so add this only when a specific MCP-compatible filesystem interface is required.
| Field | Value |
|---|---|
| Name | filesystem |
| Transport | stdio |
| Command | npx |
| Arguments | -y @modelcontextprotocol/server-filesystem /workspace/<project> |
| Environment variables | Usually none |
CloudCLI modal values:
Command
npx
Arguments
-y
@modelcontextprotocol/server-filesystem
/workspace/<project>Only include directories the agent should access. Avoid broad paths such as /, /home, or a shared secrets directory.
Stripe MCP, local npm mode
Stripe's local MCP server is useful when you prefer to pass a restricted Stripe key to a local command instead of using remote OAuth.
| Field | Value |
|---|---|
| Name | stripe |
| Transport | stdio |
| Command | npx |
| Arguments | -y @stripe/mcp@latest |
| Environment variables | STRIPE_SECRET_KEY=<restricted-or-test-key> |
CloudCLI modal values:
Command
npx
Arguments
-y
@stripe/mcp@latest
Environment variables
STRIPE_SECRET_KEY=<restricted-or-test-key>Use Stripe test mode first. For production, prefer a restricted key over a full secret key.
When stdio is the wrong choice
Use HTTP instead when:
- The provider hosts an official remote MCP endpoint.
- The server needs OAuth sign-in.
- You want one shared hosted integration instead of starting a local process in every environment.
- The command requires local software that is not installed in your CloudCLI environments.
Official references
- Playwright MCP: https://playwright.dev/docs/getting-started-mcp
- Filesystem MCP: https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem
- Stripe MCP Server: https://docs.stripe.com/mcp