How do I install ToolYour?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does ToolYour need an API key?

No required environment variable is listed on this record.

When was ToolYour last checked?

Last checked 2026-11-08. Remote MCP: plan, run, verify for SEO/security/ship-gate. Same REST API key; 500 free credits/month.

ToolYour MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://api.toolyour.com/mcp/http

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http com.toolyour-mcp https://api.toolyour.com/mcp/http

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.toolyour-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://api.toolyour.com/mcp/http"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Open-source ToolYour MCP

Remote MCP gateway for AI agents: plan → run playbook/solve → verify until pass.

MIT licensed. Hosted API/SaaS backends are optional — offline evals and local file control-plane run without them.

Product docs: https://www.toolyour.com/developers/mcp
Official registry: com.toolyour/mcp
npm client (separate): @toolyour/sdk (MIT)

Quick start

cp .env.example .env
npm install
npm run build:registry   # from monorepo docs/ when regenerating
npm run build
npm run dev

Endpoint: http://localhost:3090/mcp (SSE) · Streamable HTTP: /mcp/http

Health: GET /health/mcp · Ready: GET /health/mcp/ready · Metrics: GET /health/mcp/metrics (Prometheus text)

Auth

X-Api-Key: ty_...

Same key as ToolYour REST. Free tier: 500 credits/month (tools cost 1–10 credits). MCP exposes API-backed catalog tools only (hasApi).

Host contract

ToolYour does not replace Cursor/Claude. The host keeps editor, git, and terminal. Agents should:

plan_task (free)
run_playbook or solve_task
Apply only rank-1 loop.nextActions in the workspace
verify_task with prior result as baseline until loop.gate is pass (or stop)

Skill-loop responses also include an additive execution envelope (runId, intentId, intentType, idempotencyKey, and projectScope). Preserve it when handing a result to another MCP tool. Async jobs reuse execution.runId as the get_run polling id.

Internally, plan_task, solve_task, run_playbook, run_workflow, and verify_task use one executeIntent lifecycle boundary for correlation and the execution envelope. Credits settle on each gateway tool invoke (billing.settledBy = gateway_per_tool) — MCP does not double-bill. Free recall_context recalls purpose-typed memory before rebuilds.

Saved Playbooks (private beta)

Saved Playbooks turns a repeatable ToolYour workflow into a named, versioned recipe that an MCP-capable agent can run again. V1 deliberately points only to existing ToolYour skills or workflows; it does not store arbitrary shell commands, control another agent, or bypass host approval. Each account gets owner-scoped playbooks and durable run receipts.

Enable this only on a private/default MCP deployment with PLAYBOOKS_BETA=true. The beta adds create_saved_playbook, list_saved_playbooks, get_saved_playbook, update_saved_playbook, run_saved_playbook, and get_saved_playbook_run. It is intentionally excluded from /mcp/chatgpt so the reviewed public 21-tool surface stays unchanged.

See Saved Playbooks beta design for the data model, safe execution boundary, and rollout guidance.

Offline evals (no API key)

npm run ci                 # build + lint + unit/contract/integration + evals
npm run eval:golden        # routing + jobReport fields + verify gate
npm run eval:playbooks     # skill → workflow → synthesizer matrix + fixture coverage
npm run golden:tier1       # host work-package shapes

Fixtures: tests/eval/synth-fixtures.json · Goals: tests/eval/goals.jsonl

Observability (open protocols)

Signal	How
JSON logs	Always (`LOG_LEVEL`)
In-process counters	`/health/mcp` + `/health/mcp/metrics`
Spans	Set `OTEL_LOG_SPANS=1` and/or `OTEL_EXPORTER_OTLP_ENDPOINT` (OTLP/HTTP JSON → Collector / Jaeger / Tempo)

No proprietary APM required.

What stays hosted (optional)

Live tool execution via gateway + API key
Feature Memory / verification profiles (SaaS Mongo)
Redis for multi-replica async get_run

Local defaults use file-backed control-plane jobs.

License

MIT — see LICENSE.

ToolYour

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install ToolYour?

Does ToolYour need an API key?

What transport does ToolYour use?

When was ToolYour last checked?

Documentation

Open-source ToolYour MCP

Quick start

Auth

Host contract

Saved Playbooks (private beta)

Offline evals (no API key)

Observability (open protocols)

What stays hosted (optional)

License