Guide
Agent-assisted setup
A safe, machine-readable starting point for an assistant helping a human deploy an MCP.
Available today
Read /llms.txt to discover the public docs and use the .md links for plain Markdown. An assistant can inspect supported configuration, explain the deployment steps and prepare a review checklist. MCP Ops does not currently publish a deployment CLI, anonymous provisioning API or autonomous account-signup tool. Do not invent install commands or API routes.
Establish the intended workflow
Ask the owner for the repository or API specification, target client, intended tools and runtime requirements. Start with one read-only business task. Inspect public source only when authorized, and do not request passwords, secret values or customer records in conversation.
Human account ownership
The human creates or signs into their account through the website and completes any required email verification and terms acceptance. Stop for explicit authorization before deploying a billable resource, granting repository access or expanding permissions. Never create an account using an invented identity.
Prepare, review, then deploy
Use the existing-MCP or API-generation documentation to prepare configuration. The owner supplies secrets through the platform controls. Confirm the endpoint, tool permissions and resource limits before rollout. Report a deployment as working only after a permitted client call succeeds.
Future CLI and automation boundary
A future CLI should use browser-approved device authorization, short-lived scoped credentials, structured output, idempotent operations and explicit deployment confirmation. This is a design direction, not a currently available feature.