Cicadas local MCP

io.github.kevinwowoPublished by GitHub account kevinwowov0.1.0Updated Oct 24, 2026

Local Cicadas MCP for models, quotes and status. Authenticated API flows not yet verified.

The publisher's own server: LMCP

VerifiedSTDIODesktop onlyFinanceMedia & Design

Overview

AI-generated overview

Experimental local bridge to the Cicadas.ai customer API, letting an assistant list video models, check credit balance, quote costs and look up owned video jobs

What you can do
List the available text-to-video model catalog and read the account credit balance and key budget without creating a job. Validate a video request and estimate its credit cost. Retrieve the status of an owned video job, or recover an owned request by its original UUID without resubmitting generation. Optional source-only settings can expose video creation and downloading, but these are disabled in the supplied bundle.
When to use it
Useful when you want an assistant to inspect Cicadas video models, check remaining credits, estimate the cost of a video request, or look up the status of an existing job. It is an early experimental release whose authenticated flows have not been verified against production, so treat it as a trial rather than a dependable production tool.
Requirements
Runs as a local stdio process on the desktop, not a hosted endpoint. Needs Node.js 22 or newer and an MCP host that supports MCPB Node bundles, or running from source. Requires a Cicadas customer API key with customer API access enabled, supplied through the CICADAS_API_KEY environment variable or the bundle's sensitive configuration field. Network access to the Cicadas API is needed.
Before you install
The API key is a secret: keep it out of prompts, logs, screenshots, issue reports and committed configuration, and prefer a read-only key. Authenticated catalog, balance, quote, job lookup, key revocation, generation, download and refund flows are unverified, and no real key or paid generation was used for acceptance. Existing-job status reads may trigger provider status or refund maintenance. Optional generation spends credits and requires explicit confirmation, a request ID and a credit cap; a

Installation

In SourceWeft

  1. Open Cicadas local MCP 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.

Other MCP clients

Follow the launch instructions in the repository.

README

Cicadas local MCP

Experimental local stdio bridge for the Cicadas.ai customer API.

Authenticated functionality has not yet been verified against production. This release passed local contract tests and a packaged MCP handshake/tool-list check. No real customer API key was used for acceptance. Live account-bound catalog, balance, quote, job lookup, key revocation, generation, download and refund flows remain unverified for this release. No paid generation tests were performed.

What it exposes

Default toolIntended customer API operation
list_video_modelsRead the available text-to-video model catalog
get_credit_balanceRead the account balance and key budget
quote_videoValidate a request and estimate its credit cost without creating a job
get_video_jobRetrieve an owned job's status
get_video_requestRecover an owned request by its original UUID without resubmitting generation

All tools require a valid Cicadas customer API key. A browser session, provider key or administrator key is not a substitute. Account access is not included in this package. Existing-job status reads may perform provider status/refund maintenance; see customer API details.

Install the MCPB bundle

Download cicadas-local-mcp-0.1.0.mcpb from this repository's v0.1.0 release. Use an MCP host that supports MCPB Node bundles and Node.js 22 or newer. Import the bundle and enter a privately stored, preferably read-only, customer API key in its sensitive configuration field.

The supplied MCPB configuration sets CICADAS_ENABLE_GENERATION=0; it exposes only the five tools above. Never put keys in prompts, issue reports, logs, screenshots or committed configuration.

Run from source

Requires Node.js 22 or newer.

sh
npm ci --ignore-scriptsnpm testnpm start

Configure the MCP host to run node /absolute/path/to/src/server.mjs and provide CICADAS_API_KEY using the host's private environment configuration. The API base defaults to https://cicadas.ai/api/v1/. This is a local stdio program, not a hosted remote MCP endpoint or OAuth connector.

Optional source configuration

The underlying bridge supports CICADAS_ENABLE_GENERATION=1 to expose create_video. This is disabled in the supplied bundle. Generation additionally requires a generation-enabled customer key, explicit confirmSpend: true, a UUID request ID and a credit cap. Paid generation and delivery have not been tested for this release.

CICADAS_DOWNLOAD_DIRECTORY optionally exposes download_video for an existing local directory. Downloads use UUID filenames, refuse overwrites and report a local path plus SHA-256. Download delivery has not been verified against production for this release.

Custom HTTPS bases require CICADAS_ALLOW_CUSTOM_ORIGIN=1; loopback HTTP additionally requires CICADAS_ALLOW_HTTP_LOOPBACK=1. These are local operator settings, never tool inputs. Redirects and cookie authentication are refused. The bridge does not automatically retry paid generation after uncertainty. Recover with the original request UUID instead.

Validation and scope

  • Existing bridge contract tests: 6 passed on Node.js 22.23.2.
  • Extracted MCPB: SDK handshake and listing of five default tools passed; generation was not exposed.
  • The two bridge source files are unchanged from the existing Cicadas downloadable bridge.
  • Local tests use fixture servers. They do not establish authenticated production usability, provider output, storage delivery, payment/refund behavior or visual quality.
  • This repository contains only the standalone bridge and its documentation, not the Cicadas website application.

Website · Customer API details · Privacy policy

Source: README.md at commit a5e50fa

Tools

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

Version history

1
  1. v0.1.0LatestOct 14, 2026

Score

40% 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
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Local-Mcp integrations