AGKit MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to AgentKit generated management-plane tools and plan/apply workflow: Do CLI and MCP share the same required scopes and confirmation ceremony as the command registry evolves?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Manage AGKit Cloud configuration and reviewed action workflows from local developer tools.

What we know

AGKit CLI includes a local stdio MCP server. After login it can inspect Cloud state and, with explicit write scopes, prepare/review/apply supported configuration changes. The product model emphasizes user approval for actions.

Maintenance / activity evidence

@storybloq/agkit 0.6.0 published 2026-09-29T02:47:24.519Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read configuration by default; optional management/write actions with explicit scopes. Reported action classes: Apply supported Cloud configuration changes when write scopes are granted. Complete write authority is not verified.
CLI login with scoped permissions.
Sensitive access: Cloud configuration, App/action metadata, CLI credentials

Scope/confirmation model is a real control boundary; do not assume default login can mutate everything.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do CLI and MCP share the same required scopes and confirmation ceremony as the command registry evolves?

The bounded review of the publisher's documented AgentKit generated management-plane tools and plan/apply workflow and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Scope/confirmation model is a real control boundary; do not assume default login can mutate everything.
Read configuration by default; optional management/write actions with explicit scopes.
CLI login with scoped permissions.
AGKit Cloud configuration/action data is processed by service; local MCP reuses CLI credentials.
Reviewed write actions: Apply supported Cloud configuration changes when write scopes are granted
Sensitive access: Cloud configuration, App/action metadata, CLI credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
full current management tool inventory
Default sign-in grants read access; management needs additional write scopes.
MCP uses CLI credentials.
Specific action/write inventory is version-dependent and should be read from `agkit reference`.

Original activity observations

@storybloq/agkit 0.6.0 published 2026-09-29T02:47:24.519Z

Technical identity

npm/@storybloq/agkit

Exact implementation source: https://www.npmjs.com/package/@storybloq/agkit ↗
Reviewed resource type: Gateway
Package identity: npm:@storybloq/agkit

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@storybloq/agkit
Recorded package identity, distribution or download evidence.
Evidence source ↗
agkit.cloud/start
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
Install CLI then authenticate using publisher browser/device flow; MCP runs from CLI.
publisher documented install or connect · Publisher instructions
npm install -g @storybloq/agkit
publisher documented step or launch · Publisher instructions
claude mcp add agkit -s user -- agkit mcp serve
Configure / authenticate
MCP100 setup guide
Official path is global agkit install, then OAuth login and project/model tier setup. `npx @storybloq/agkit init` is first-touch bootstrap, not a substitute for supported primary install.
Environment variables referenced by this route (respect the alternatives above): AGKIT_TOKEN
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

AGKit CLI includes a local stdio MCP server. After login it can inspect Cloud state and, with explicit write scopes, prepare/review/apply supported configuration changes. The product model emphasizes user approval for actions.

Capability: Developer Tools
Resource type: Gateway
Best fit: Manage AGKit Cloud configuration and reviewed action workflows from local developer tools.

Representative uses

Inspect account/configuration
Prepare reviewed actions
Apply supported management changes with write scope
Use CLI reference for exact scope/confirmation requirements

Limitations

Default sign-in grants read access; management needs additional write scopes.
MCP uses CLI credentials.
Specific action/write inventory is version-dependent and should be read from `agkit reference`.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: CLI login with scoped permissions.
Permissions: Read configuration by default; optional management/write actions with explicit scopes.
Data handling: AGKit Cloud configuration/action data is processed by service; local MCP reuses CLI credentials.
Cost: plan_based
Risk and cautions: Scope/confirmation model is a real control boundary; do not assume default login can mutate everything.

Access scope and cautions

Write actions: Not verified Apply supported Cloud configuration changes when write scopes are granted
Sensitive access: Cloud configuration App/action metadata CLI credentials
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect account/configuration; Prepare reviewed actions; Apply supported management changes with write scope; Use CLI reference for exact scope/confirmation requirements.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install -g @storybloq/agkit && agkit login && agkit mcp serve. Recorded transport: stdio. Prerequisites: AGKit account; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: CLI login credentials; default grant is read, management requires relevant write scopes.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Apply supported Cloud configuration changes when write scopes are granted. Recorded permission context: Read configuration by default; optional management/write actions with explicit scopes.

What data-handling boundary should I consider?

AGKit Cloud configuration/action data is processed by service; local MCP reuses CLI credentials. Recorded sensitive-access context: Cloud configuration; App/action metadata; CLI credentials.

What limitations and risks should I check before use?

Scope/confirmation model is a real control boundary; do not assume default login can mutate everything. Default sign-in grants read access; management needs additional write scopes. MCP uses CLI credentials. Specific action/write inventory is version-dependent and should be read from `agkit reference`. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.