MCP server for AI agents — Cursor, Claude & more
Remote MCP server for AI agents. Connect Cursor, Claude, and other MCP clients to API-backed tools — converters, SEO, documents, text, and more — with the same plan as REST. One remote URL. Same catalog as the REST API. Same plan and quota — not a separate product.
Why agents need a tools MCP server
Most MCP servers help agents with code, repos, or browsers. ToolYour fills the utilities gap: convert files, run SEO audits, transform text, and process documents — from Cursor, Claude, or any MCP client — without building custom wrappers for every tool.
Task-oriented
Agents call
solve_taskin plain language; the server routes to tools and workflows.Token-efficient discovery
Agents search the catalog on demand instead of loading hundreds of tool schemas upfront.
Same plan as REST
One key, one quota for apps and agents. Free tier includes 500 requests/month.
Connect Cursor, Claude, or any MCP client
- 1
Get an API key
Create a key on your dashboard. MCP shares the same monthly quota as REST.
- 2
Add the remote MCP URL
Point your client at
https://api.toolyour.com/mcpwith headerX-Api-Key. Use the config panel above for Cursor (~/.cursor/mcp.json), Claude Desktop, Claude Code, and other MCP-compatible agents. - 3
Agent workflow
Prefer
solve_taskfirst — describe the goal in plain language (e.g. "SEO audit for https://example.com"). The server auto-picks workflows and tools.solve_task— natural-language goal- If status is
suggest, usetoolSuggestions, thenget_tool_schemaandinvoke_tool - Or search manually:
list_categories→discover_tools→get_tool_schema→invoke_tool
Discovery meta-tools are free and do not count toward quota. Execution bills like REST.
Browser, REST, and MCP — one catalog
Every API-backed tool is available free in the browser for humans, via REST for apps, and via MCP for agents. Website-only tools stay browser-only.
MCP FAQ
- Is this a local or remote MCP server?
- Remote. Agents connect over HTTPS to https://api.toolyour.com/mcp — no local install of ToolYour tools required.
- MCP vs REST — when should I use which?
- Use REST when your app or backend calls tools programmatically. Use MCP when an AI agent (Cursor, Claude, etc.) should discover and run tools in conversation. Both share billing.
- What categories work over MCP?
- File converters, SEO & site tools, documents, text utilities, unit converters, finance calculators, and AI utilities — any tool with API access enabled.
Full reference: MCP quickstart docs.
