@vidofy/mcp 0.1.0

package/dist/index.d.ts

@@ -0,0 +1,49 @@
+#!/usr/bin/env node
+/**
+ * @vidofy/mcp — the Vidofy MCP server.
+ *
+ * Lets a desktop AI client (Claude Desktop, Cursor, …) generate media with
+ * Vidofy, billed to the user's own account. Runs locally over stdio; the
+ * client launches it, so nothing here listens on a port.
+ *
+ * Nine tools: list_modes → list_models → get_model to choose, estimate_cost to
+ * price it, generate to run it, get_status and get_result to follow it, plus
+ * get_balance and get_usage.
+ *
+ * Eight of the nine are read-only. `generate` is the only one that spends the
+ * user's balance, and it is the only one whose annotations say so — which is
+ * what a client reads to decide whether to ask the user first.
+ *
+ * `upload_file` is deliberately absent: /app/v1 has no upload route at all
+ * (it is /api/v1 + an API key only), so on the account door files travel
+ * multipart with the submit itself, exactly as the studio posts them. It was
+ * planned as a key-mode tool; key mode is not served (see the refusal below),
+ * so nothing would ever call it. Nine tools is the whole set, not nine of ten.
+ *
+ * WHY stdout IS OFF LIMITS
+ * ------------------------
+ * stdio transport means stdout IS the protocol channel — one stray
+ * console.log() writes a non-JSON-RPC line into the stream and the client
+ * drops the connection with an error that names nothing. Every diagnostic in
+ * this package goes to stderr, which the client shows in its logs and ignores
+ * otherwise. There is a `log()` helper below; use it and never console.log.
+ */
+import { Server } from '@modelcontextprotocol/server';
+import { type Config } from './config.js';
+import { log } from './log.js';
+export { log };
+/** The version from package.json, so the User-Agent cannot drift from the release. */
+export declare function readVersion(): string;
+/**
+ * Build a fully wired Server for one credential — everything except the
+ * transport.
+ *
+ * Extracted from main() so the remote transport can reuse it (src/http.ts).
+ * The split matters for one reason that is easy to miss: over stdio this
+ * process serves exactly ONE account for its whole life, while over HTTP each
+ * request carries a different person's token. So the Server cannot be a
+ * module-level singleton — it is built per caller, around that caller's Config,
+ * and `cfg` being a parameter rather than a global is what makes spending the
+ * wrong account's coins impossible by construction.
+ */
+export declare function buildServer(cfg: Config, version: string): Server;