Local stdio MCP Server Examples
Copy common stdio command, args, and environment variable settings for Playwright, filesystem, GitHub, and Stripe MCP servers.
Use stdio MCP servers when the server runs as a local command inside the CloudCLI environment. In CloudCLI, add these from Settings > Configuration > Organization 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.
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 to navigate pages, click controls, fill forms, capture screenshots, or verify UI behavior from inside the environment.
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.
GitHub MCP, local Docker mode
Use GitHub's local server when your MCP host cannot use the hosted GitHub MCP server or when you want to run the server in a container.
| Field | Value |
|---|---|
| Name | github |
| Transport | stdio |
| Command | docker |
| Arguments | run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server |
| Environment variables | GITHUB_PERSONAL_ACCESS_TOKEN=<token> |
CloudCLI modal values:
Command
docker
Arguments
run
-i
--rm
-e
GITHUB_PERSONAL_ACCESS_TOKEN
ghcr.io/github/github-mcp-server
Environment variables
GITHUB_PERSONAL_ACCESS_TOKEN=<github-personal-access-token>Use a fine-scoped token. If Docker is not available in your environments, use the hosted HTTP GitHub MCP server instead.
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
- GitHub MCP Server: https://github.com/github/github-mcp-server
- Stripe MCP Server: https://docs.stripe.com/mcp