Cueport

Name: Cueport
Author: CloudCorpRecords

by CloudCorpRecordsversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.CloudCorpRecords/cueport

Install

Overview

Description from the maker (original English)

CueAPI agent-work scheduling: cues, executions, claiming, heartbeats, and outcomes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cueport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/cueport",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add cueport -- npx -y @reneturcios/cueport mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cueport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/cueport",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cueport": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/cueport",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32466 servers in this category
Published to the registry more recently than 88% of the other 32466 servers in this category
Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cueport safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

cueport

cueport gives an MCP host or a terminal access to CueAPI, the coordination layer for agent work: schedule cues (recurring cron or one-time), fire them on demand, watch their executions, claim worker executions, keep a claim alive with heartbeats, and close the loop by reporting an outcome backed by evidence. One binary serves a command-line interface and a stdio MCP server.

An API key is required. Set CUEAPI_API_KEY to a key from your CueAPI account; every call sends it as Authorization: Bearer , and a missing key fails before any request is attempted. Self-hosting or testing against another host? Set CUEAPI_BASE_URL alongside the key; when it is unset, calls go to https://api.cueapi.ai.

Install

npx @reneturcios/cueport list-cues

Or run the container image:

docker run -i ghcr.io/cloudcorprecords/cueport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

cueport create-cue --name digest --schedule "0 9 * * *" --callback-url https://example.test/hook

cueport list-cues --status active --limit 5 cueport get-cue cue_abc123 cueport fire-cue cue_abc123 --payload-override '{"topic":"release notes"}' cueport update-cue cue_abc123 --name "morning digest" cueport pause-cue cue_abc123 cueport resume-cue cue_abc123 cueport delete-cue cue_abc123 cueport list-executions --cue-id cue_abc123 --status failed cueport get-execution exec_123 cueport list-claimable --task digest --agent worker-a cueport claim-execution exec_123 --worker-id worker-7 cueport claim-next --task-name digest --worker-id worker-7 cueport heartbeat exec_123 --worker-id worker-7 cueport report-outcome exec_123 --outcome succeeded --external-id ext_42 --result-url https://example.test/result

cueport --version

Commands print the upstream JSON payload. Exit codes: 0 on success, 1 when a call fails (including a missing API key or an upstream API error), 2 for usage errors.

Two behaviours are worth knowing. Pausing and resuming are not separate endpoints: both are a PATCH /v1/cues/{id} carrying only a status field (paused or active). And claim-next is a fan-out, not a single call: the claim endpoint has no task filter, so the tool first fetches the server-side filtered claimable list, picks the oldest entry, and then claims that execution by id.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

npx -y @reneturcios/cueport mcp

MCP client configuration:

"mcpServers": { "cueport": { "command": "npx", "args": ["-y", "@reneturcios/cueport", "mcp"], "env": { "CUEAPI_API_KEY": "cue_sk_..." } } } }

Add CUEAPI_BASE_URL to the env block to point the server at a different CueAPI-compatible host.

Tools

Tool	Input	What it does
`cueapi_create_cue`	`name`, `schedule` (required); optional description, callback, method, timezone, payload, task and platform fields	Create a recurring or one-time cue.
`cueapi_list_cues`	`status`, `limit` (optional)	List cues, filtered by status.
`cueapi_get_cue`	`cue_id`	Fetch one cue.
`cueapi_fire_cue`	`cue_id`; optional `payload_override`, `merge_strategy` (`merge` default, or `replace`)	Fire a cue immediately.
`cueapi_update_cue`	`cue_id` plus any mutable cue fields	Sparse update; only provided fields are sent.
`cueapi_pause_cue`	`cue_id`	Pause a cue (PATCH with status `paused`).
`cueapi_resume_cue`	`cue_id`	Resume a cue (PATCH with status `active`).
`cueapi_delete_cue`	`cue_id`	Delete a cue permanently.
`cueapi_list_executions`	`cue_id`, `status`, `limit` (optional)	List executions, filtered by cue and status.
`cueapi_get_execution`	`execution_id`	Fetch one execution, with state and outcome.
`cueapi_list_claimable_executions`	`task`, `agent`, `limit` (optional)	List unclaimed worker executions, filtered server-side.
`cueapi_claim_execution`	`execution_id`; optional `worker_id`	Atomically claim one execution.
`cueapi_claim_next_execution`	`task_name`, `worker_id` (optional)	Claim the oldest claimable execution.
`cueapi_execution_heartbeat`	`execution_id`, `worker_id` (both required)	Extend a claim lease; `worker_id` travels in the `X-Worker-Id` header.
`cueapi_report_outcome`	`execution_id`, `outcome` (required); optional evidence fields	Report a write-once outcome with evidence.

Development

npm install

npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures) npm run dev # run the CLI from source via tsx

License

MIT — see LICENSE.

Cueport

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

HotCodePush

README from the maker

cueport

Install

CLI

MCP server

Tools

Development

License