Echo Env

You can run a lightweight MCP server that echoes essential workspace environment variables to verify that an MCP client forwards context like the working directory and workspace slug. This enables quick sanity checks and practical experimentation with MCP workflows.

How to use

Start the server locally from the workspace you want to inspect. The server reads the current environment and exposes a tool that returns the workspace path and slug. You can also override values per run to test different contexts.

How to install

Prerequisites you need installed on your system: Node.js with npm or a compatible package manager (such as npx or pnpm). You will also use the server binary directly or via a package runner.

# Quick start using npx without prior installation
npx mcp-server-echo-env

# Or run directly after installing locally
npm install -g mcp-server-echo-env
mcp-server-echo-env

Additional content

Configuration and runtime behavior are designed to reflect workspace context. On startup, the server derives defaults from the current directory if no environment overrides are provided. You can explicitly set values for a given run to validate how an MCP client propagates these variables.

Key environment variables you’ll interact with include WORKSPACE_SLUG and PWD. You can override them per run to test different workspace contexts, for example: WORKSPACE_SLUG=demo PWD=/path/to/workspace mcp-server-echo-env.

Logging can be adjusted with MCP_ECHO_ENV_LOG_LEVEL. Choose from: silent, error, info, or debug. Logs appear on stderr to avoid affecting the JSON payload returned to MCP clients.

Available tools

env_echo

Returns the current WORKSPACE_SLUG and PWD values from the server, confirming that environment context is being propagated from the MCP client to the server.