Agkit

cloud.agkitPublished by agkit.cloudv0.6.0Updated Oct 24, 2026

AgentKit management-plane CLI + MCP server (agkit).

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server and CLI for managing the AgentKit management plane, letting an assistant work with AgentKit resources from the desktop.

What you can do
The input lists no tools, so capabilities come from the description only. It is described as an AgentKit management-plane CLI that also runs as an MCP server, so an assistant could reach AgentKit management-plane operations through it. It runs as a local process over stdio rather than as a remote endpoint. No further detail on specific operations is provided.
When to use it
Consider it when you already use the AgentKit management plane and want an assistant on your desktop to act on it through MCP instead of a separate CLI session. The sparse description gives little basis for other uses.
Requirements
Runs as a local process over stdio, installed from the npm package @storybloq/agkit, so a Node.js runtime and npm are needed. Desktop only; no web executable. No authentication, environment variables or headers are declared, but the CLI may still expect its own configuration.
Before you install
It is a management-plane tool, so operations may change or delete AgentKit resources; confirm what each action does before letting an assistant run it. No credentials are declared, but any configuration the CLI reads is not described here. The description is very brief, so review the package before installing.

Installation

In SourceWeft

  1. Open Agkit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.6.0LatestSep 29, 2026
  2. v0.3.0Sep 16, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.