MCP Clients
Copy the correct StaticX MCP configuration for Claude Code, Claude Desktop, Cursor, Cline, Windsurf, Zed, and generic clients.
Pick your agent
One server. Familiar setup everywhere.
StaticX runs as a local stdio MCP server. The agent starts it with npx and passes the scoped token through environment variables.
Claude Code
Add StaticX from the terminal.
claude mcp add staticx \
--env STATICX_API_TOKEN=sx_replace_with_your_token \
--env STATICX_API_BASE_URL=https://staticx.site/api/v1 \
-- npx -y @staticx/mcp-server
claude mcp list
Claude Desktop · Cursor · Codex · Cline · Windsurf
Use the standard mcpServers config.
Open the client’s MCP settings, add this server, then restart or refresh MCP tools. Cline can also open its MCP Servers panel; Cursor shares configured servers with its CLI.
{
"mcpServers": {
"staticx": {
"command": "npx",
"args": [
"-y",
"@staticx/mcp-server"
],
"env": {
"STATICX_API_TOKEN": "sx_replace_with_your_token",
"STATICX_API_BASE_URL": "https://staticx.site/api/v1"
}
}
}
}Zed
Add a custom context server.
Add the entry to Zed settings under context_servers. Keep tool approval set to confirm for write operations.
{
"context_servers": {
"staticx": {
"command": "npx",
"args": [
"-y",
"@staticx/mcp-server"
],
"env": {
"STATICX_API_TOKEN": "sx_replace_with_your_token",
"STATICX_API_BASE_URL": "https://staticx.site/api/v1"
}
}
}
}Local HTTP debugging
Inspect MCP over a local endpoint.
STATICX_API_TOKEN=sx_replace_with_your_token npx @staticx/mcp-server http
# MCP endpoint
http://localhost:3100/mcp
Local HTTP mode is for debugging clients that support Streamable HTTP. The normal recommended setup remains stdio because the token never leaves the local machine.