Skip to content

STDIO Transport

The STDIO transport runs a local MCP server as a child process. ChatShell starts the process, communicates with it over stdin/stdout, and automatically discovers the tools it provides.

  1. Go to Settings → MCP Servers
  2. Click Add Server
  3. Select STDIO as the transport type
  4. Fill in the configuration fields
  5. Click Test Connection to verify
  6. Click Save

Tip: Already have a claude_desktop_config.json or similar config file? Click Paste JSON config to import the server definition directly — no manual field entry needed. See JSON Config Import for supported formats.

FieldRequiredDescription
CommandYesThe executable to run (e.g., npx, node, python)
ArgsNoCommand-line arguments as a list
EnvNoEnvironment variables to set for the process
Working DirectoryNoWorking directory for the process (defaults to home directory)

Many MCP servers are distributed as npm packages and can be run directly with npx:

Command: npx
Args: -y @modelcontextprotocol/server-filesystem /Users/you/projects

This runs the Filesystem MCP server, giving the AI enhanced filesystem access to the specified directory.

Command: python
Args: -m my_mcp_server
Working Directory: /Users/you/my-mcp-project

Use the Env field to pass configuration to the MCP server:

{
"API_KEY": "your-api-key",
"BASE_URL": "https://api.example.com"
}

Security note: ChatShell sanitizes the environment passed to STDIO processes. Only essential system variables (PATH, HOME, USER, SHELL, etc.) are inherited automatically. All other variables must be explicitly configured in the Env field.

ServerCommandDescription
Everythingnpx -y @modelcontextprotocol/server-everythingSample server for testing
Filesystemnpx -y @modelcontextprotocol/server-filesystem /pathEnhanced file access
GitHubnpx -y @modelcontextprotocol/server-githubGitHub API tools
Brave Searchnpx -y @modelcontextprotocol/server-brave-searchBrave Search API

Process fails to start Check that the command is installed and in your PATH. For npx, ensure Node.js is installed.

No tools discovered The process may have crashed on startup. Check the logs in ChatShell’s developer console.

Environment variable not found Remember that environment variables are not automatically inherited. Add them explicitly in the Env field.