logs_projects_list — LogsLoom MCP Tool
logs_projects_list
(logs projects list) is one of 4 tools on the
LogsLoom
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call logs_projects_list from your client
- Claude Code LogsLoom logs_projects_list run in your project directory
- Claude Desktop LogsLoom logs_projects_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LogsLoom logs_projects_list ~/.cursor/mcp.json
- VS Code LogsLoom logs_projects_list .vscode/mcp.json
- Zed LogsLoom logs_projects_list ~/.config/zed/settings.json
- Windsurf LogsLoom logs_projects_list ~/.codeium/windsurf/mcp_config.json
- Cline LogsLoom logs_projects_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LogsLoom logs_projects_list ~/.gemini/settings.json
- Grok LogsLoom logs_projects_list .mcp.json (in your project root)
- ChatGPT LogsLoom logs_projects_list Settings → Connectors → Advanced → Developer mode
- Claude.ai LogsLoom logs_projects_list Settings → Connectors → Add custom connector
- LangChain LogsLoom logs_projects_list pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http logsloom https://mcp.logsloom.com/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.