mcp server
Croft
Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-08-06.
What this server can do
25 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_app(name, description)- Provisions an empty app on this workspace: a git repo, subdomain, port, and golden-path scaffold files. It contains no feature implementation and is not yet live. Required: name.
delete_app(app, confirm)- Permanently deletes an app: removes its containers, data, and source code from the server, then deletes the app record. Irreversible. Does not affect other apps or the server. Deletes only when confirm is true. Required: app, confirm.
deploy(app, message)- Commits, builds (Nixpacks), and deploys the app. Returns a deploy job id; the build runs in the background and its deploy_state moves through queued and running before it ends in succeeded or failed. The app is live only once the deploy has succeeded. Required: app.
describe_connector(name)- Returns a connector's full manifest — base URL, auth style, and the named operations (method, path, params) an app can call. Never returns the credential. Required: name.
get_app(name)- Get an app's file manifest, recent releases, and secret key names. Required: name.
get_platform_conventions- Return the Croft golden-path rules that every app on this workspace must follow.
grant_access(app, email)- Grant an existing user access to an app. Required: email, app.
grant_connector(app, connector)- Gives one of your apps access to a connector. The app can then call the connector's operations. Note: this lets the app's code, and everyone the app is shared with, use the connector's credential. A connector an admin has marked admins-only can only be granted by an admin. Some connectors require admin approval: when a creator grants one of those, the grant is created as 'requested' and an owner/admin must approve it (they're emailed) before the app can use it — owners/admins granting it are approved automatically. Required: app, connector.
invite_user(apps, role, email)- Invite someone by email, set their workspace role, and grant app access. role is member (use apps), creator (can build their own apps), or admin. apps is 'all' or a list of app names. Required: email.
list_apps- List the apps in this workspace with their URLs, status, and last release.
list_connectors- Lists the workspace's API connectors (external services apps can call without holding the credential) and their state. `active` connectors are usable; `draft` ones still need a workspace admin to add the credential.
list_grants(app)- Lists the connectors an app can reach and each grant's state. Required: app.
list_secret_keys(app)- List an app's secret key names (never values). Required: app.
list_users- List the people in this workspace and which apps they can access.
logs(app, lines)- Recent runtime logs for an app (relayed from its box). Required: app.
propose_connector(name, base_url, auth_param, auth_style, operations, description)- Creates a new API connector as a DRAFT from the vendor's API docs: you supply the base URL, auth style, and an operations manifest. A workspace member (owner, admin, or creator) then opens the panel and adds the credential to activate it — the credential never passes through you. auth_style is bearer|header|query|basic; for header/query also give auth_param (the header/param name). Required: name, base_url, auth_style, operations.
read_file(app, path)- Read one file from an app's own git repo on this Croft workspace. No external API — the path is resolved inside the app's repository. Required: app, path.
revoke_access(app, email)- Revoke a user's access to an app. Required: email, app.
rollback(app)- Re-deploy the previous release of an app. Required: app.
set_database_sharing(app, shared)- Turns this app's database sharing on or off. Off by default (the database is private). When on, other apps in the same workspace may read AND write this app's SQLite database through Croft's internal broker at http://croft-data:8080/q/<this-app-name> (send {"sql":"…","params":[…]}), and this app is listed to other apps as reusable shared data. Turn it on for an app whose data other apps should reuse — e.g. a CRM's contacts list that an invoicing app also needs. Required: app, shared.
set_public_paths(app, paths)- Sets which of an app's paths are reachable WITHOUT login. By default an app is fully private (workspace login required everywhere). Pass the complete desired list of specific paths (e.g. ["/survey"]); each listed path and everything under it becomes public, everything else stays private. An empty list makes the app fully private again. The whole app cannot be made public — root or wildcard paths are rejected. Required: app, paths.
set_schedules(app, schedules)- Sets the app's scheduled tasks. Each is { name, cron, path }: on the cron (standard 5-field, UTC) Croft makes an internal POST to the app's path, and the app does the work (e.g. send a daily email, sync an API). Use this for anything recurring instead of writing your own cron — it survives deploys and reboots and is shown in the panel. Also implement the endpoint (e.g. a POST route at that path). Pass the full desired list; an empty list clears all schedules. Required: app, schedules.
set_secret(app, key, value)- Set (or replace) an env secret for an app. Value is stored encrypted and injected at deploy. Required: app, key, value.
status(app)- Reports an app's deploy and health status. `live` is true only when the latest deploy has fully succeeded; `deploy_state` gives the current stage (queued, running, succeeded, or failed). Read-only and safe to call repeatedly — each call returns the current stage, so it can be polled to follow a deploy's progress. Required: app.
write_files(app, files)- Writes files into an app's git repo and commits them (as 'Claude via Croft'). files is a list of {path, content}. Committed files are staged in the repo; they are not built or published until the app is deployed. Required: app, files.
Last successful function declaration observed on . Source: https://mcp.oncroft.net. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.oncroft.net.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 25 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.oncroft.net | |
| mcp endpoint status | ok | The server listed 25 functions when asked. | as of probe | mcp.oncroft.net |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json