Croft

net.oncroftPublished by oncroft.netOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Lets an AI assistant deploy and host the apps it builds, giving them a real server, database, and shareable URL.

What you can do
Croft is a remote MCP endpoint that lets an assistant take an app it has built and put it online. According to the description, it provides a real server, a database, and a shareable URL for the deployed app. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant to move from generating code to running a hosted app that others can open through a link, rather than keeping it local.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP, plus OAuth sign-in with the provider. No packages, environment variables, or headers are declared.
Before you install
Deployment publishes apps to a shareable URL, so anything deployed may be publicly reachable. Hosting and a database are provided by the third party, meaning your app content and data are sent to and stored with that provider. Access is tied to an OAuth account. Tool-level behavior is not documented in the manifest.

Installation

In SourceWeft

  1. Open Croft in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.oncroft%2Fcroft/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.