Verified component catalog over remote MCP: agents pick component ids and get a stamped project repo that builds. Connect at https://www.botkelp.com/mcp. Auth: MCP OAuth 2.1, or a Bearer bk_live_ API key; initialize and tools/list are open.
Scored across 16 tools
Most tools are cleanly split by resource (admin page sets, site profiles, projects, GitHub, components) with clear get/set pairs, and the descriptions explicitly disambiguate tricky cases like get_component (unrendered source) vs purchase_scaffold (real files) and get_scaffold (re-fetch) vs purchase_scaffold (buy). The main soft spot is get_github vs set_github, which both surface an install URL when no repo is connected, and get_help vs search_components overlap as free discovery entry points.
Every tool is snake_case verb_noun, and resources follow a predictable get_/set_ pairing for admin page sets, site profiles, projects, and GitHub. Action tools (purchase_scaffold, verify_scaffold, search_components, report_issue) use the same verb-first convention.
At 16 tools it sits at the upper end of comfortable, but nearly every tool maps to a distinct resource-action or to a small utility (status, help, issue reporting) that earns its place. The get/set symmetry keeps the surface from feeling bloated.
The purchase lifecycle is well covered: discovery (search/get_component), buying, re-fetching, verifying builds, project maintenance, plus profile/admin-page authoring and GitHub wiring. Gaps are minor — there is no explicit delete/remove for saved projects or site profiles, only a Maintain toggle and replace-in-place semantics.
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 your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Add one secure layer between your agents and this server.
