kad.dev

dev.kadPublished by kad.devOfficial publisherv1.0.0Updated Nov 1, 2026

Deploy and run web apps from your agent: live URL, Postgres, S3 storage, a version per commit.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

kad.dev is a remote MCP server that lets an assistant deploy and run web apps, giving each commit a live URL with Postgres and S3 storage.

What you can do
  • Deploy web apps from the assistant and get a live URL back.
  • Run hosted apps with Postgres and S3 storage attached.
  • Track a version per commit so each change maps to a deployment.
When to use it
Useful when you want an assistant to take a web app from code to a running, publicly reachable deployment with database and object storage, without wiring up separate hosting, database and storage providers.
Requirements
A remote MCP endpoint at kad.dev over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. A kad.dev account is implied by the OAuth sign-in.
Before you install
OAuth grants the server access to your kad.dev account, so review the scopes requested at sign-in. Deploying publishes apps to live URLs and provisions Postgres and S3 storage, which may incur usage or hosting costs. Deployments write and change hosted resources; the manifest lists no tools, so confirm what actions are exposed before use.

Installation

In SourceWeft

  1. Open kad.dev 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/dev.kad%2Fkad/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": {
    "kad-dev": {
      "type": "http",
      "url": "https://kad.dev/mcp"
    }
  }
}

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.0LatestNov 1, 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.