Echo Env FAQs

Question 1

Can I configure or override the environment variables Echo Env uses?

Accepted Answer

Yes, Echo Env offers flexible configuration. It loads environment variables from `.env` files found in the current working directory, and values exported in the shell environment (e.g., via `WORKSPACE_SLUG=my-slug pnpm start`) take precedence, allowing for dynamic overrides per run.

Question 2

What is Echo Env and what is its primary purpose?

Accepted Answer

Echo Env is an MCP (Micro-Container Protocol) server designed to echo selected environment variables, specifically `PWD` and `WORKSPACE_SLUG`. Its main purpose is to help developers verify that an MCP client or agent correctly propagates workspace context into the server process during execution.

Question 3

Is Echo Env compatible with various MCP clients?

Accepted Answer

Absolutely. Echo Env is designed to work with any MCP client that supports stdio servers. Documentation provides examples for integration with popular clients such as Codex CLI, Playwright MCP runner, and Jina MCP tools, making it versatile for different development setups.

Question 4

How does Echo Env help in verifying MCP client behavior?

Accepted Answer

By launching Echo Env within a target workspace and connecting an MCP client, developers can invoke the `env_echo` tool. Echo Env then reports the `PWD` and `WORKSPACE_SLUG` it received, allowing you to confirm if your client or agent is accurately forwarding the expected environment context.

Question 5

Which environment variables does Echo Env specifically echo?

Accepted Answer

Echo Env is configured to echo `PWD` (present working directory) and `WORKSPACE_SLUG`. These are crucial for defining workspace context in many development environments. The tool intentionally ignores any other user-supplied keys to focus solely on these core variables.

Echo Env

Acerca de

Características Principales

Casos de Uso