CueAPI MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to CueAPI scheduling and evidence-backed execution reports: Do outcome reports retain their evidence and attribution rather than equating a scheduled task with completion?

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

Best fit

Schedule agent follow-up work and record evidence-backed outcomes in CueAPI.

What we know

Schedule agent work and report write-once outcomes via CueAPI from any MCP host. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@cueapi/mcp 0.4.1 published 2026-05-02T19:30:18.782Z

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.
Schedule and invoke worker/webhook jobs according to key scope Writes: Schedule or trigger work; Update/pause/delete cues; Claim and report execution outcomes.
CueAPI API key
Sensitive access: API key, Webhook destinations, Execution payloads

Potential high-impact side effects: Schedule or trigger work, Update/pause/delete cues, Claim and report execution outcomes.

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

All limitations / Review context

Do outcome reports retain their evidence and attribution rather than equating a scheduled task with completion?

The bounded review of the publisher's documented CueAPI scheduling and evidence-backed execution reports 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.

Potential high-impact side effects: Schedule or trigger work, Update/pause/delete cues, Claim and report execution outcomes.
Schedule and invoke worker/webhook jobs according to key scope
CueAPI API key
Cue schedules, payloads, execution metadata and external evidence URLs are sent to CueAPI or configured self-hosted deployment.
Reviewed write actions: Schedule or trigger work; Update/pause/delete cues; Claim and report execution outcomes
Sensitive access: API key, Webhook destinations, Execution payloads
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.
cost: plans, pay-per-call charges, and payment authorization details
Cue execution can trigger worker or webhook activity
One-shot and recurring triggers must not be mistaken for harmless metadata writes

Original activity observations

@cueapi/mcp 0.4.1 published 2026-05-02T19:30:18.782Z

Technical identity

npm/@cueapi/mcp

Exact implementation source: https://www.npmjs.com/package/@cueapi/mcp ↗
Reviewed resource type: MCP Server
Repository identity: cueapi/cueapi-mcp
Package identity: npm:@cueapi/mcp

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 ↗
@cueapi/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
cueapi/cueapi-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Create CUEAPI_API_KEY; stdio MCP for API orchestration. Publisher documents Claude Desktop configuration.
publisher install or stdio launch · Publisher instructions
npx -y @cueapi/mcp
Configure / authenticate
MCP100 setup guide
Publisher: `npx -y @cueapi/mcp` with CUEAPI_API_KEY in client env; an optional self-hosted base URL is `CUEAPI_BASE_URL`.
Check connection
Suggested check
Inspect tool discovery and a read-only account status operation; never test a paid mutation.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `cueapi-mcp`, run `claude mcp remove cueapi-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove cueapi-mcp

Official Documentation & Sources

What it does

Schedule agent work and report write-once outcomes via CueAPI from any MCP host. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Schedule agent follow-up work and record evidence-backed outcomes in CueAPI.

Representative uses

Create one-time or cron cues
Fire/pause/resume/update/delete cues
Claim execution and submit outcome proof
Inspect execution history

Limitations

Cue execution can trigger worker or webhook activity
One-shot and recurring triggers must not be mistaken for harmless metadata writes

Reviewed access

Access & risk

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

Authentication: CueAPI API key
Permissions: Schedule and invoke worker/webhook jobs according to key scope
Data handling: Cue schedules, payloads, execution metadata and external evidence URLs are sent to CueAPI or configured self-hosted deployment.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Schedule or trigger work, Update/pause/delete cues, Claim and report execution outcomes.

Access scope and cautions

Write actions: Schedule or trigger work Update/pause/delete cues Claim and report execution outcomes
Sensitive access: API key Webhook destinations Execution payloads
Risk level: high

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: Create one-time or cron cues; Fire/pause/resume/update/delete cues; Claim execution and submit outcome proof; Inspect execution history.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @cueapi/mcp. Recorded transport: stdio. Recorded environment-variable notes: CUEAPI_API_KEY; CUEAPI_BASE_URL (optional). No configuration values are supplied here. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: CueAPI API key

Can it modify data or perform write operations?

Documented write actions include: Schedule or trigger work; Update/pause/delete cues; Claim and report execution outcomes. Recorded permission boundary: Schedule and invoke worker/webhook jobs according to key scope

What data-handling boundary should I consider?

Cue schedules, payloads, execution metadata and external evidence URLs are sent to CueAPI or configured self-hosted deployment. Recorded sensitive-access context: API key; Webhook destinations; Execution payloads.

What limitations and risks should I check before use?

Potential high-impact side effects: Schedule or trigger work, Update/pause/delete cues, Claim and report execution outcomes. Cue execution can trigger worker or webhook activity. One-shot and recurring triggers must not be mistaken for harmless metadata writes. 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.