INDIVIDUAL MCP TOOL
find_tools_for_task
Which software can your agent use for a job, from AgentDrives's test drives: say the task in plain words (e.
LIVE ENDPOINT
https://agentdrives.com/api/mcp
Connect to this endpoint to inspect the live schema for find_tools_for_task and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.agentdrives-directory-public]
url = "https://agentdrives.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"agentdrives-directory-public": {
"type": "http",
"url": "https://agentdrives.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: agentdrives-directory-public
Remote MCP URL: https://agentdrives.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"agentdrives-directory-public": {
"url": "https://agentdrives.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"agentdrives-directory-public": {
"type": "http",
"url": "https://agentdrives.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "agentdrives-directory-public",
"transport": "streamable-http",
"url": "https://agentdrives.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search_tools— Find software an AI agent can really use, from AgentDrives's directory of products test-driven by an AI agent: use it before you pick a tool for a task or ask a person to sign up for one.get_tool— One product's full test-drive result, for when you need to know exactly how far an agent gets with it and where it stops (search_tools gives the slug; an unknown slug is an error that says how to find one): the agent level, the five outcomes (find, access, use, pay, leave, by any way in the product offers; stages: the four that decide the level, under their older keys), how an agent gets in (access, with the core tasks done on each way), the part scores, the nine checkpoints in the order of the agent's eight steps (Find: none, it is the Agent-ready setup; Learn: docs; Sign up: sign-up, verify; Get a key: key, first call; Do the work: first action; Pay: pay; Cancel: cancel; Leave: delete), what an agent can and cannot do, tips for agents, pay_options (the ways to pay it offers an agent, the payment our side proved with its transaction, and what the owner could add), the bot check that stopped our agent on a way in, even where it got in another way (agent_check: vendor, step, type networlist_categories— Every category in the directory: its id (for search_tools' category filter), its name, the number of products driven in it and the best agent level in it (0-5).