events — tide MCP Tool
events
(events) is one of 38 tools on the
tide
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call events from your client
- Claude Code tide events run in your project directory
- Claude Desktop tide events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor tide events ~/.cursor/mcp.json
- VS Code tide events .vscode/mcp.json
- Zed tide events ~/.config/zed/settings.json
- Windsurf tide events ~/.codeium/windsurf/mcp_config.json
- Cline tide events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI tide events ~/.gemini/settings.json
- Grok tide events .mcp.json (in your project root)
- ChatGPT tide events Settings → Connectors → Advanced → Developer mode
- Claude.ai tide events Settings → Connectors → Add custom connector
- LangChain tide events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://api.tide.ad/mcpOther tools on this server
- explain_transaction
- wallet_profile
- wallet_history
- balance_at
- token_info
- trace_funds
- search
- perp_market
- price
- sql
- explain_unsigned
- yield_options
- yield_plan
- build_transaction
- withdraw_plan
- receipt_for_transaction
- confirm_execution
- verify_receipt
- agent_pass_report
- agent_pass_precheck
- agents_overview
- agent_wallet
- owner_agents
- billing_status
- billing_topup
- get_object
- get_object_at
- object_children
- package_info
- checkpoint
- candles
- nfts
- staking
- order_book
- walrus_blob
- address_kind
- docs
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.