CloneKit

ai.clonekitPublished by clonekit.aiOfficial publisherv0.1.1Updated Oct 24, 2026

Expert know-how (kits) any AI can read or run, always the latest version.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

CloneKit gives an AI assistant access to expert know-how kits that it can read or run, always at the latest version.

What you can do
CloneKit is a remote MCP endpoint that exposes expert know-how, called kits, to an AI assistant. According to the description, an assistant can read or run these kits, and they are always served at the latest version. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to draw on packaged expert know-how rather than general model knowledge, and you prefer a hosted endpoint over a local install. It is not a fit if you need a documented tool list before adopting a server.
Requirements
A remote MCP connection to the hosted endpoint at clonekit.ai over streamable HTTP. Authentication is required and uses OAuth, so the user must sign in and authorize access. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth, so review which account is authorized and what the consent screen permits. The manifest lists no tools, so what the assistant can read or run, and whether any action changes data, cannot be confirmed from this listing.

Installation

In SourceWeft

  1. Open CloneKit 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/ai.clonekit%2Fclonekit/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": {
    "clonekit": {
      "type": "http",
      "url": "https://clonekit.ai/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

2
  1. v0.1.1LatestOct 18, 2026
  2. v0.1.0Oct 15, 2026

Score

67% 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
  • 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.