Verified component catalog over remote MCP: agents pick ids and get a project that builds.
Scored across 16 tools
Most tools map cleanly to a resource+action (search_components vs get_component vs purchase_scaffold; get_/set_ pairs for projects, siteprofile, adminpageset). The main soft spots are get_github vs set_github, which both discuss connect/install flows and installUrl, and get_component vs purchase_scaffold, whose boundary is only clarified inside the description text.
Consistent get_/set_ prefix pairs plus a few action verbs (search_, purchase_, verify_, report_), so an agent can predict names. Minor deviations: cramped compound nouns like get_adminpageset and get_siteprofile that do not match the 'admin_page_set' / 'site_profile' spelling used in the descriptions, and get_projects plural vs get_component singular.
16 tools is at the upper end but each corresponds to a real operation in a multi-resource domain (catalog, purchasing, verification, projects, profiles, admin page sets, GitHub). Four symmetric get_/set_ resource pairs plus lifecycle tools earn their place, though the set could be trimmed by folding account/help/status helpers together.
The catalog → purchase → verify → maintain → refetch loop is fully covered, along with profile, admin-page-set, and GitHub configuration. Gaps are minor: no way to delete a named site profile or admin page set (only full replace), no credit-balance check despite credit-based purchasing, and no explicit list of prior purchases beyond get_projects.
No params. Says whether you are signed in (authenticated) and account tools work (accountToolsReady). Never returns a key.
Inputs: no named parameters.
Lists this account's admin page set names (omit name), or returns one set's exact files (pass name). These are the file trees purchase_scaffold's admin_page_set param bakes into a dedicated forked repo. Requires a linked account (transport auth).
Inputs: name.
One component's source files, UNRENDERED (EJS markers, not build-ready): inspect only; use purchase_scaffold for real files. Free, 32/day, signed-in account.
Inputs: component (required).
Shows whether this account has a GitHub repo connected, or lists files under a path in that repo. If not connected, the result includes installUrl — open it (GitHub App) to grant read access to one repo. Sign in on botkelp.com with GitHub first so the install is tied to your account.
Inputs: path.
Free. Short usage index. Then search_components to pick ids.
Inputs: no named parameters.
Lists this account's saved scaffold projects (id, name, description, repo, components, maintain state). Use the projectid with get_scaffold to re-fetch a scaffold — no project_api_key is needed as a tool argument.
Inputs: no named parameters.
Refetches a scaffold you purchased (fresh clone command), no extra credits. Credit-flow projects need Maintain on. Same site_profile/delivery options as purchase_scaffold.
Inputs: projectid (required), delivery, site_profile.
Your site profiles (privacy, terms, cookies, licence, custom_field) as JSON. list: true for names, or siteprofilename for one; field filters. Use next.arguments when a purchase reply says incomplete: true.
Inputs: list, field, cursor, siteprofilename.
Buys a CI-green starter repo for component ids (credits via your signed-in account, or x402). Returns a git clone command and projectid. Red builds are refused and not charged. delivery "inline" returns files instead (more tokens).
Inputs: components (required), project, delivery, maintain, +3 more.
Report a catalog/code bug or request a component (files an issue on botkelp/components). Signed-in account, 10/day. No secrets.
Inputs: description (required), projectid.
Free. Compact catalog TSV: id, provides, requires, conflictsWith. Omit args for all.
Inputs: query, detail, provides.
Creates or fully replaces one named admin page set for this account — real file source (React/Next.js), not text config. purchase_scaffold's admin_page_set param bakes a chosen set into a brand-new, dedicated repo. An account may keep more than one named set.
Inputs: name (required), files (required).
Returns a GitHub App install URL so the user can grant BotKelp read access to one of their repos. Open the URL, pick a single repo, approve. Then purchase_scaffold template_files: [{ source: "app/legal/" }] copies those pages into the clone. disconnect: true drops the connection. Prefer signing in with GitHub on botkelp.com first.
Inputs: disconnect.
Turn Maintain on/off for a project and/or rotate its project key. Off keeps existing clones; it stops future get_scaffold access.
Inputs: projectid (required), rotate, maintain.
Creates or updates one named site profile for this account. Fields omitted from field keep their current saved value (or blank, if the profile is new); pass only what changed. custom_field entries are merged key-by-key. An account may keep more than one named profile (e.g. one per brand/site).
Inputs: field (required), siteprofilename (required).
Remote npm install && npm run build of your edited files (send every file). Call with files -> WAIT + jobId; call again with jobId -> OK or FAIL with the error tail. Needs a purchased projectid.
Inputs: projectid (required), files, jobId, envVariables.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
MCP Server for an Agent Task Marketplace
Governed MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution.
Remote MCP for Android CLI agent build gate, structured receipts, audit logs, and reviewer-ready evi
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Add one secure layer between your agents and this server.
