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