deepstack_entity — DeepStack: Independent analysis of the AI economy MCP Tool
deepstack_entity
(deepstack entity) is one of 8 tools on the
DeepStack: Independent analysis of the AI economy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call deepstack_entity from your client
- Claude Code DeepStack: Independent analysis of the AI economy deepstack_entity run in your project directory
- Claude Desktop DeepStack: Independent analysis of the AI economy deepstack_entity ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DeepStack: Independent analysis of the AI economy deepstack_entity ~/.cursor/mcp.json
- VS Code DeepStack: Independent analysis of the AI economy deepstack_entity .vscode/mcp.json
- Zed DeepStack: Independent analysis of the AI economy deepstack_entity ~/.config/zed/settings.json
- Windsurf DeepStack: Independent analysis of the AI economy deepstack_entity ~/.codeium/windsurf/mcp_config.json
- Cline DeepStack: Independent analysis of the AI economy deepstack_entity ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DeepStack: Independent analysis of the AI economy deepstack_entity ~/.gemini/settings.json
- Grok DeepStack: Independent analysis of the AI economy deepstack_entity .mcp.json (in your project root)
- ChatGPT DeepStack: Independent analysis of the AI economy deepstack_entity Settings → Connectors → Advanced → Developer mode
- Claude.ai DeepStack: Independent analysis of the AI economy deepstack_entity Settings → Connectors → Add custom connector
- LangChain DeepStack: Independent analysis of the AI economy deepstack_entity pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http deepstack https://mcp.deepstack.ltd/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 20 October 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.