Croft MCP Server

by oncroft Your server? Claim it

answering

Croft is answering right now. Last checked 8 min ago. It exposes 26 tools.

Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.

Uptime history 71 days of history · worst day 92%

71 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

220 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

14 Aug a tool appeared request_public_data_access

14 Aug a tool description was rewritten set_database_sharing

14 Aug a tool changed the parameters it asks for set_database_sharing

12 Aug a tool description was rewritten grant_connector

11 Aug 6 tools appeared describe_connector, grant_connector, list_connectors and 3 more

11 Aug a tool description was rewritten invite_user

11 Aug a tool changed the parameters it asks for invite_user

Nothing serious here today

Today is the operative word: we check Croft every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add croft --transport http https://mcp.oncroft.net

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "croft": {
      "url": "https://mcp.oncroft.net"
    }
  }
}

~/.codex/config.toml

[mcp_servers.croft]
url = "https://mcp.oncroft.net"

.cursor/mcp.json

{
  "mcpServers": {
    "croft": {
      "url": "https://mcp.oncroft.net"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "croft": {
      "url": "https://mcp.oncroft.net"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

app

create_app

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.

delete_app

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.

get_app

Get an app's file manifest, recent releases, and secret key names.

grant

grant_access

Grant an existing user access to an app.

grant_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.

secret

list_secret_keys

List an app's secret key names (never values).

set_secret

Set (or replace) an env secret for an app. Value is stored encrypted and injected at deploy.

apps

list_apps

List the apps in this workspace with their URLs, status, and last release.

connectors

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.

database

set_database_sharing

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. By default apps that have PUBLIC routes cannot read this shared data (a leak guard); an owner/admin can pass allow_public: true to let public apps read it too. Turn sharing on for an app whose data other apps should reuse — e.g. a CRM's contacts list that an invoicing app also needs.

deploy

deploy

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.

describe

describe_connector

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.

file

read_file

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.

files

write_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.

grants

list_grants

Lists the connectors an app can reach and each grant's state.

invite

invite_user

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.

logs

logs

Recent runtime logs for an app (relayed from its box).

platform

get_platform_conventions

Return the Croft golden-path rules that every app on this workspace must follow.

propose

propose_connector

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).

public

set_public_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.

request

request_public_data_access

For an app that has PUBLIC routes: request permission for it to use protected resources (its granted connectors AND other apps' shared data). Public apps are blocked from these by default so a public page can't leak workspace data. If you (the caller) are an owner or admin, this is granted immediately; if you're a creator it creates a request that an owner/admin approves (they're emailed). Call this when building a public app that also needs a connector or shared data.

revoke

revoke_access

Revoke a user's access to an app.

rollback

rollback

Re-deploy the previous release of an app.

schedules

set_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.

status

status

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.

users

list_users

List the people in this workspace and which apps they can access.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.oncroft.net	streamable-http	sign-in	143 ms	8 min ago

Alternatives to Croft

same job, measured the same way

blitz.cloud

by blitz

Host apps in the EU from your assistant: App Store, Docker, GitHub, databases, logs.

answering

Ployz

by ployz

Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.

answering

Orbit

by orbitapps

An app builder for agents. Your agent creates screens, a Postgres database, and a live URL.

answering

dFlow

by dflow

Deploy apps, databases, and services in your dFlow workspace.

answering

Schema

by schemalabs

The AI that understands raw data: Schema over your tables and databases, as MCP tools.

answering

SeedBase Test Data

by marcelglaeser

Generate realistic, FK-consistent synthetic test data for your databases from your AI assistant.

38 installs/wk 6 tools answering

Homespun

by homespun

Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.

590 installs/wk 27 tools answering

openLCA MCP Server

by below280

Connect AI assistants to openLCA. 35 tools for database search, model building, and LCIA.

399 installs/wk local only

Croft — questions

Answers built from our own checks of this server.

What can Croft do?

It exposes 26 tools, read directly from the server on our last check. Among them: create_app, delete_app, deploy, describe_connector, get_app, get_platform_conventions and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Croft mostly used for?

Its tools cluster around app, grant and secret. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Croft working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 220 ms. The bar chart above shows every period we have measured.

How do I connect Croft?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Croft?

No API key is involved. Croft answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Croft?

It answers our handshake in 220 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.