macro_calendar — Wicked MCP MCP Tool
macro_calendar
(macro calendar) is one of 108 tools on the
Wicked MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call macro_calendar from your client
- Claude Code Wicked MCP macro_calendar run in your project directory
- Claude Desktop Wicked MCP macro_calendar ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Wicked MCP macro_calendar ~/.cursor/mcp.json
- VS Code Wicked MCP macro_calendar .vscode/mcp.json
- Zed Wicked MCP macro_calendar ~/.config/zed/settings.json
- Windsurf Wicked MCP macro_calendar ~/.codeium/windsurf/mcp_config.json
- Cline Wicked MCP macro_calendar ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Wicked MCP macro_calendar ~/.gemini/settings.json
- Grok Wicked MCP macro_calendar .mcp.json (in your project root)
- ChatGPT Wicked MCP macro_calendar Settings → Connectors → Advanced → Developer mode
- Claude.ai Wicked MCP macro_calendar Settings → Connectors → Add custom connector
- LangChain Wicked MCP macro_calendar pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wicked-mcp https://mcp.wickedapi.com/mcpOther tools on this server
- kalshi_probability
- kalshi_market
- funding_oi
- long_short_ratio
- orderbook
- basis
- hyperliquid
- volatility
- sentiment
- defi_tvl
- price
- ohlcv
- atr
- rates
- market_clock
- market_overview
- gas
- fvg
- liquidity_levels
- earnings_calendar
- wallet_portfolio
- verdict
- momentum_score
- chain_balance
- chain_token_balance
- chain_nonce
- chain_block
- chain_ens
- chain_tx
- polymarket
- web_search
- crypto_news
- liquidations
- protocol_health_scoreboard
- protocol_health_list_protocols
- protocol_health_track_protocol
- protocol_health_score
- protocol_health_refresh_all
- protocol_health_sync_universe
- token_risk
- broker_sync_register_user
- broker_sync_connections
- broker_sync_positions
- broker_sync_balances
- broker_sync_transactions
- broker_sync_prop_firms
- filings_freshness
- filings_latest_preview
- filings_search
- filings_8k_events
- filings_insider_trades
- filings_insider_summary
- filings_filing
- wallet_sanctions_check
- wallet_check
- reputation_status
- reputation_statement
- reputation_query
- reputation_tiers
- reputation_transparency
- reputation_leaderboard
- reputation_history
- reputation_erc8004
- reputation_get_nonce
- reputation_register
- reputation_stake
- reputation_unstake
- reputation_withdraw
- registry_search_tools
- registry_tool_detail
- registry_lookup
- registry_onboarding_message
- registry_create_api_key
- registry_key_info
- registry_revoke_key
- registry_featured_tools
- registry_tool_badge
- registry_report_tool
- registry_register_tool
- identity_sandbox_register
- identity_get_test_key
- identity_get_nonce
- identity_register
- identity_get_challenge
- identity_submit_response
- identity_status
- identity_jwks
- sanity_check
- sanity_check_batch
- sanity_get_check
- memory_prepare
- memory_store
- memory_search
- memory_get
- memory_update
- memory_history
- memory_delete
- memory_deletions
- paywall_demo_weather
- paywall_signup
- paywall_get_tenant
- paywall_list_routes
- paywall_create_route
- paywall_import_routes
- paywall_update_route
- paywall_delete_route
- paywall_list_settlements
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.