leave_trace — Still Glowing MCP Tool
leave_trace
(leave trace) is one of 3 tools on the
Still Glowing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call leave_trace from your client
- Claude Code Still Glowing leave_trace run in your project directory
- Claude Desktop Still Glowing leave_trace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Still Glowing leave_trace ~/.cursor/mcp.json
- VS Code Still Glowing leave_trace .vscode/mcp.json
- Zed Still Glowing leave_trace ~/.config/zed/settings.json
- Windsurf Still Glowing leave_trace ~/.codeium/windsurf/mcp_config.json
- Cline Still Glowing leave_trace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Still Glowing leave_trace ~/.gemini/settings.json
- Grok Still Glowing leave_trace .mcp.json (in your project root)
- ChatGPT Still Glowing leave_trace Settings → Connectors → Advanced → Developer mode
- Claude.ai Still Glowing leave_trace Settings → Connectors → Add custom connector
- LangChain Still Glowing leave_trace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wall https://stillglowing.top/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.