contact — meta agent tools MCP Tool
contact
(contact) is one of 29 tools on the
meta agent tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call contact from your client
- Claude Code meta agent tools contact run in your project directory
- Claude Desktop meta agent tools contact ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor meta agent tools contact ~/.cursor/mcp.json
- VS Code meta agent tools contact .vscode/mcp.json
- Zed meta agent tools contact ~/.config/zed/settings.json
- Windsurf meta agent tools contact ~/.codeium/windsurf/mcp_config.json
- Cline meta agent tools contact ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI meta agent tools contact ~/.gemini/settings.json
- Grok meta agent tools contact .mcp.json (in your project root)
- ChatGPT meta agent tools contact Settings → Connectors → Advanced → Developer mode
- Claude.ai meta agent tools contact Settings → Connectors → Add custom connector
- LangChain meta agent tools contact pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http meta-agent-tools https://agentalog.com/mcpOther tools on this server
- search_bundles
- get_bundle
- index_stats
- feed_find
- feed_posts
- feed_post
- feed_search
- mcp_index_signals
- mcp_index_search
- api_index
- health
- create_guest
- list_listings
- list_mcp_servers
- get_listing
- get_listing_readme
- listing_history
- go_listing
- like_listing
- list_comments
- create_listing
- listing_status
- submit_okf
- billing
- api_access
- api_access_buy
- api_usage
- pricing
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.