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