← ManufactCONTENT HISTORY

Update to Manufact

Snapshot Oct 24, 2026 · 12:57 UTC · version 2.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Manufact and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use right after a user connects the Manufact Cloud MCP server, or when they ask what Manufact is, what they can do with it, or where to start. Explains the platform model (users, organizations, servers, deployments), inspects the user's account, and routes them to deploying, managing, or publishing an MCP server.",
  "included_files": [],
  "name": "manufact-onboarding",
  "skill_md_contents": "---\nname: manufact-onboarding\ndescription: Use right after a user connects the Manufact Cloud MCP server, or when they ask what Manufact is, what they can do with it, or where to start. Explains the platform model (users, organizations, servers, deployments), inspects the user's account, and routes them to deploying, managing, or publishing an MCP server.\nmetadata:\n  owner: manufact\n---\n\n# Onboard a new Manufact user\n\nManufact Cloud hosts MCP servers and MCP apps. It is built by the team behind the\nopen-source mcp-use SDKs, but it hosts servers built with any framework. Users\ndeploy from GitHub, get a live MCP URL, and then test, observe, and publish the\nserver to clients such as ChatGPT, Claude, and Cursor.\n\nThe user is already signed in: connecting this MCP server completed the OAuth\nflow. Never ask them for passwords, API keys, or tokens.\n\n## How Manufact Cloud is organized\n\n```text\nUser\n└── Organizations        (a user belongs to one or more)\n    └── Servers          (each server is one MCP server)\n        └── Deployments  (each server has many; one serves production)\n```\n\n- **User**: the signed-in account. It can belong to several organizations.\n- **Organization**: owns servers, GitHub connections, members, billing, and\n  credits. New accounts get a Primary organization automatically.\n- **Server**: one MCP server. It has a GitHub repository, build settings,\n  environment variables, domains, analytics, checklist runs, eval suites,\n  submission packs, and an optional public chat page.\n- **Deployment**: one build of the server from a branch and commit.\n  - The production branch (usually `main`) deploys on every push and serves\n    `https://<slug>.run.mcp-use.com/mcp`.\n  - Other branches get preview URLs.\n  - A newer deployment can fail while an older one keeps serving traffic.\n\nTools follow the same hierarchy. Organization IDs scope servers, server IDs\nscope deployments, and so on down. Use only IDs that tools return or that the\nuser gives you. Never guess an ID.\n\n## First conversation\n\n1. **Introduce Manufact briefly.** One or two sentences is enough, unless the user\n   asks for more.\n2. **Look at the account before suggesting anything.**\n   - Call `list_organizations`.\n     - One organization: use it without asking.\n     - Several organizations: ask which one to work in, unless the conversation\n       already makes it clear.\n   - Call `list_servers` for that organization.\n3. **Summarize what you found**, in plain language: which organization, how many\n   servers, and each server's name and latest deployment status. Call\n   `get_server` only for a server the user wants to look at more closely.\n4. **Offer the next steps that fit their state**, as the table below shows. Offer\n   two or three concrete options, not the whole tool list.\n\n| User's state | Suggested next step |\n| --- | --- |\n| No servers, has an MCP server repo on GitHub | Deploy it. Follow the `manufact-deploy` skill. |\n| No servers, no code yet | Scaffold one with `npx create-mcp-use-app@latest`, push it to GitHub, then deploy. |\n| Server with a failed latest deployment | Debug it with the recovery steps in the `manufact-deploy` skill. |\n| Healthy server, not yet published | Check publishing readiness. Follow the `manufact-publish-ready` skill. |\n| Healthy server, wants others to try it | Enable a public chat page (`configure_public_chat`, Hobby plan or higher). |\n| Server, wants to understand usage or errors | Follow the `manufact-analytics` skill to inspect scoped metrics and evidence. |\n| Server hosted elsewhere | Connect it in the dashboard (see below), then run the checklist. |\n\n## What each area covers\n\n| Area | Main tools | Use for |\n| --- | --- | --- |\n| Organizations and team | `list_organizations`, `create_organization`, `list_team_members`, `send_team_invite` | Choose a workspace and invite teammates. |\n| GitHub | `list_github_installations`, `get_github_connect_url`, `connect_github_repo_to_server` | Give Manufact access to repositories. |\n| Servers and deployments | `create_server`, `deploy`, `get_deployment`, `list_deployments`, `promote_deployment` | Ship code and follow builds. |\n| Configuration | `get_server_configuration`, `update_server_deployment_settings`, `create_environment_variable` | Change build settings and secrets. |\n| Domains | `get_server_domains`, `update_server_subdomain`, `add_server_custom_domain` | Change the server's URLs. |\n| Observability | `get_server_analytics_summary`, `get_server_analytics_catalog`, `get_deployment_runtime_logs` | See usage and errors; follow `manufact-analytics` for deeper questions. |\n| Publishing | `run_publishing_checklist`, `run_eval_suites`, `generate_submission_pack`, `configure_public_chat` | Get ready for app directories. |\n\n## What happens outside this MCP server\n\nSend the user to the dashboard at https://manufact.com, or to the CLI, for these:\n\n- **Connecting a server hosted elsewhere** (by URL, optionally proxied through\n  Manufact). No tool here creates external servers.\n- **Deploying without GitHub.** Run `npx @mcp-use/cli login`, then\n  `npx @mcp-use/cli deploy --no-github` from the project directory. This\n  uploads the source directly.\n- **Billing and plan upgrades.** Preview deployments, GitHub organization\n  repositories, public chat, end-to-end checklist checks, and submission packs\n  require the Hobby plan or higher.\n- **Installing the GitHub App.** `get_github_connect_url` returns the link, but\n  the user must finish the install on GitHub.\n\nDocs are at https://docs.manufact.com.\n\n## Ground rules\n\n- **Confirm before anything destructive or billable.** Destructive tools:\n  `delete_server`, `delete_eval_suite`, `disconnect_server_repository`,\n  `delete_server_custom_domain`, and `promote_deployment` (it switches production\n  traffic). Billable tools: `run_publishing_checklist`, `run_eval_suites`, and\n  `generate_submission_pack` consume credits.\n- **Changes need a new deployment to take effect.** This applies to environment\n  variables, build settings, and subdomain changes. Say so, and offer to `deploy`.\n- **Don't retry blindly.** After a write with an uncertain result, inspect with\n  the matching get or list tool before retrying.\n- **Present links as clickable links.** This covers GitHub connect links,\n  authentication links, and dashboard URLs.\n"
}

SHA-256 of public snapshot: cef68a728749b8dda69dfdea05eb52594e7526864660eb19184af66116c78e26