@royalti/syynk-mcp

MCP server for Syynk — transcribe audio and export synchronized lyrics and subtitles without leaving your editor.

Not yet published. Building and testing work today; publishing is blocked until @royalti/syynk is re-cut (see Publishing).

Setup

Create an API key at syynk.to/settings/api-keys, then add the server to your MCP client.

Claude Code

claude mcp add syynk --env SYYNK_API_KEY=sk_... -- npx -y @royalti/syynk-mcp

Anything with a JSON config (Claude Desktop, Cursor, …)

{
  "mcpServers": {
    "syynk": {
      "command": "npx",
      "args": ["-y", "@royalti/syynk-mcp"],
      "env": { "SYYNK_API_KEY": "sk_..." }
    }
  }
}

SYYNK_BASE_URL overrides the API host if you are pointing at a non-production deployment.

Tools

| Tool | Cost | What it does | |---|---|---| | syynk_list_projects | free | List your projects, newest first | | syynk_get_project | free | One project with segments and word timings | | syynk_get_lyrics | free | Just the lyrics text, no timestamps | | syynk_export | free | Export a project to lrc, srt, vtt, ttml, json or txt | | syynk_check_credits | free | Remaining credits and plan tier | | syynk_transcribe | paid | Transcribe audio into a new timed project |

syynk_transcribe bills on audio duration: groq-whisper 0 credits/min, whisper-1 3, scribe_v2 5. A long track blocks for several minutes — that is expected, and retrying starts a second billed transcription while the first is still running.

There is deliberately no delete tool.

Local files

This server runs on your machine, so it can read a path you give it:

Transcribe /Users/me/Music/demo.mp3 and export it as LRC

That works only over stdio. MCP has no client-to-server file transfer — tool arguments are JSON, the binary-capable content blocks are result types, and Roots is deprecated as of the 2026-07-28 spec. A remote MCP server therefore only ever accepts a mediaUrl, and this one will say so plainly if you hand it a path it cannot read.

Development

bun run mcp:build   # builds the SDK, then core, then this package — order matters
bun run test        # unit + in-memory protocol round-trip tests

packages/syynk-mcp-core holds every tool definition. This package is a thin adapter onto @modelcontextprotocol/server; the future remote server reuses the same core.

Publishing

Blocked on re-cutting the SDK. @royalti/[email protected] on npm predates the workspace's groq-whisper support at the same version number, so a published build would resolve the January tarball and the free model would not typecheck. Bump and republish @royalti/syynk first.