feedback — agdata MCP Tool
feedback
(feedback) is one of 31 tools on the
agdata
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call feedback from your client
- Claude Code agdata feedback run in your project directory
- Claude Desktop agdata feedback ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agdata feedback ~/.cursor/mcp.json
- VS Code agdata feedback .vscode/mcp.json
- Zed agdata feedback ~/.config/zed/settings.json
- Windsurf agdata feedback ~/.codeium/windsurf/mcp_config.json
- Cline agdata feedback ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agdata feedback ~/.gemini/settings.json
- Grok agdata feedback .mcp.json (in your project root)
- ChatGPT agdata feedback Settings → Connectors → Advanced → Developer mode
- Claude.ai agdata feedback Settings → Connectors → Add custom connector
- LangChain agdata feedback pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agdata https://agdata.shveik.dev/mcpOther tools on this server
- unblock
- google-maps
- tiktok
- youtube
- amazon
- google-search
- google-maps-reviews
- youtube-transcript
- screenshot
- linkedin-jobs
- indeed-jobs
- shopify-products
- google-news
- amazon-reviews
- google-play-reviews
- linkedin-company
- web-search
- x-replies
- youtube-comments
- tiktok-comments
- instagram-comments
- ebay-sold
- meta-ads
- linkedin-profile-email
- linkedin-posts
- search-plus
This list was read from the server itself, by connecting to it and calling tools/list on 12 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.