impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Giggy speech tools for AI agents: discover voices, generate speech and transcribe recordings.
教 AI 做这类工作的 Skill,可与本项一起使用
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-09 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Giggy Speech MCP。按照 https://mcp.popnx.com/i/giggy-speech.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(giggy.ai) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Giggy Speech MCP 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Giggy Speech MCPhttps://giggy.ai/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsGiggy Speech MCP
用 Giggy Speech MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Giggy Speech MCP,或回答中出现 Giggy Speech MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Giggy Speech MCP
Giggy Speech MCP 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Giggy Speech MCP 的应用
B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Giggy Speech MCP 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user speech https://giggy.ai/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Giggy Speech MCP 在列表中并显示已连接
用 Giggy Speech MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Giggy Speech MCP,或回答中出现 Giggy Speech MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Giggy Speech MCP 的密钥(在开发者网站创建)
在 Giggy Speech MCP 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Giggy Speech MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Giggy Speech MCP,或回答中出现 Giggy Speech MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Giggy Speech MCP 的密钥(在开发者网站创建)
在 Giggy Speech MCP 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Giggy Speech MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Giggy Speech MCP,或回答中出现 Giggy Speech MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://giggy.ai/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user speech https://giggy.ai/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"speech": {
"url": "https://giggy.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"speech": {
"type": "http",
"url": "https://giggy.ai/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过域名 giggy.ai 验证(注册中心会核实域名所有权)
代码最后更新于14天前
不适用:由 giggy.ai 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 289 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/giggy-speech)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于14天前,最新版本(1.0.3)于8天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
The Figma MCP server brings Figma design context directly into your AI workflow.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| 本项 Giggy Speech MCP | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| 许可证 | ISC | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Giggy MCP is a remote Streamable HTTP Model Context Protocol (MCP) server for using Giggy text-to-speech and recorded-audio speech-to-text from coding agents and AI clients.
It provides Giggy speech tools to Codex, Claude Code, Cursor, VS Code, Cline, Windsurf-compatible clients, and other MCP clients.
Giggy's remote speech MCP endpoint is:
https://giggy.ai/mcp
This repository contains the publication artifacts for:
server.jsonopenai-plugin/.claude-plugin/plugin.jsonSee directory submission status and requirements.
A public registry listing, plugin submission, and approved plugin publication are separate steps. Consult the submission document for verified status.
npx skills add giggy-ai/giggy-mcp --skill giggy-speech
The skill guides TTS, recorded STT, live microphone WebSocket STT, SDK and Pipecat integrations without requiring an MCP connection. Executing MCP tools still requires an authenticated connection. Check the current package and workflow guide at https://giggy.ai/llms-full.txt before implementing.
claude plugin marketplace add giggy-ai/giggy-mcp
claude plugin install giggy-speech@giggy
Follow the existing Codex MCP setup below.
"Use Giggy to list available English voices, generate a short Batch speech sample saying 'Hello from Giggy', and return the completed audio URL."
| Goal | Existing path | Check |
|---|---|---|
| Write integration code | Install the skill and read the current SDK/API guide | No MCP connection or inference is needed for code-only work. |
| Execute speech tools | Configure MCP for your client with its own key | Inspect tools/list; expect the five tools below. Read-only discovery is separate from billable generation. |
| Run live microphone STT | Use the documented server-side WebSocket or SDK live workflow | MCP recorded transcription is not the live transport. |
| Install a local plugin | Use the existing plugin/client instructions | Local installation does not establish marketplace approval. |
| Check public availability | Read the dated directory-status document | A prepared archive or historical portal sign-in does not prove approval today. |
For Codex, use the environment-backed TOML below. Claude Code has its JSON example below. Cursor, VS Code, Cline and Windsurf client examples are in examples/. Use the configuration format supported by your installed client; do not paste a shared key into manifests or chat.
The API-key bearer setup is the documented path in this repository. OAuth is separate: verify the hosted server, client and per-user authorization together before claiming it works. Candidate OAuth source code is not a verified hosted flow. Respect the user's budget and existing authorization; validating setup does not authorize paid Fast/Streaming or microphone calls.
For a code-only first task ask: "Use the Giggy skill to implement explicit Batch TTS that saves SDK audio bytes, or recorded STT that retrieves final text. MCP workflows poll the returned UUID for their completed result URL. Check current docs; do not execute requests." For a live integration ask: "Implement the documented live WebSocket flow, preserving readiness, stop and final verification; write code only."
Set GIGGY_API_KEY in your environment, then add to ~/.codex/config.toml:
[mcp_servers.giggy-speech]
url = "https://giggy.ai/mcp" bearer_token_env_var = "GIGGY_API_KEY"
Set GIGGY_API_KEY, then configure:
{
"mcpServers": { "giggy-speech": { "type": "http", "url": "https://giggy.ai/mcp", "headers": { "Authorization": "Bearer ${GIGGY_API_KEY}" } } } }
Keep API keys out of configuration files committed to source control.
https://giggy.ai/mcp
Transport:
Streamable HTTP
The current Giggy MCP endpoint is stateless and accepts POST requests.
Use a Giggy API key:
Authorization: Bearer $GIGGY_API_KEY
Giggy API keys begin with:
giggy_sk_
Keep the key in your MCP client's secret or environment configuration.
Do not:
This repository documents these Giggy speech tools:
list_voices
list_my_voices generate_speech get_speech_generation transcribe_audio
Read the connected server's tool schemas before calling these tools. Recorded transcription is asynchronous admission, followed by durable status/result retrieval. MCP does not transport live microphone frames; use the Python or Node.js SDK for that workflow.
Connect MCP with your own Giggy API key, then ask: "Use Giggy to transcribe my authorised recording with the available recorded-audio tool, retain the generation UUID, and retrieve the completed transcript."
The assistant must inspect transcribe_audio's current schema, prepare the supported input and use one idempotency key per intended operation. Poll get_speech_generation without resubmitting. Retrieve the canonical transcript only after completion; do not treat admission as final text. Check pricing and limits before paid usage. The current transcript contract does not provide speaker diarization, word timestamps, sentiment or PII redaction.
For SDKs, Pipecat, n8n and learning resources, use the developer tool guide.
list_voices or list_my_voices.voice_id.generate_speech with explicit mode=batch for the free queued workflow; paid modes require authorization.idempotency_key for each new intended generation.generation.generation_uuid.get_speech_generation while the status is queued or processing.completed, use generation.result.url.Do not resubmit a new generation while polling an existing generation.
Set:
export GIGGY_API_KEY="giggy_sk_..."
Then add this to:
~/.codex/config.toml
[mcp_servers.giggy-speech]
url = "https://giggy.ai/mcp" bearer_token_env_var = "GIGGY_API_KEY"
A ready-to-copy version is included at:
examples/codex-config.toml
Verify:
codex mcp list
Set:
export GIGGY_API_KEY="giggy_sk_..."
A project MCP configuration is included at:
examples/claude-code.mcp.json
Its contents are:
{
"mcpServers": { "giggy-speech": { "type": "http", "url": "https://giggy.ai/mcp", "headers": { "Authorization": "Bearer ${GIGGY_API_KEY}" } } } }
Copy that configuration to:
.mcp.json
in the project where Claude Code should use Giggy.
Then run:
claude mcp list
or use:
/mcp
inside Claude Code.
Ready-to-copy client configurations are included for:
| Client | Example |
|---|---|
| Codex | examples/codex-config.toml |
| Claude Code | examples/claude-code.mcp.json |
| Cursor | examples/cursor.mcp.json |
| VS Code | examples/vscode.mcp.json |
| Cline | examples/cline.mcp.json |
| Windsurf-compatible clients | examples/windsurf.mcp.json |
Set:
export GIGGY_API_KEY="giggy_sk_..."
Copy or merge:
examples/cursor.mcp.json
into:
.cursor/mcp.json
for project configuration, or:
~/.cursor/mcp.json
for global configuration.
Copy or merge:
examples/vscode.mcp.json
into:
.vscode/mcp.json
This example uses the VS Code Local harness and its password-style ${input:giggy-api-key} prompt. It is not a universal Copilot-harness configuration: input/command secrets from the VS Code format are not forwarded to that harness. Check the official MCP configuration reference for the environment-variable header format supported by your selected harness. Do not replace a secret placeholder with a key in a committed file.
Open Cline's MCP server configuration and copy the contents of:
examples/cline.mcp.json
Replace:
YOUR_GIGGY_API_KEY
in your local configuration only.
Do not commit the configured file.
For installations that use:
~/.codeium/windsurf/mcp_config.json
merge the contents of:
examples/windsurf.mcp.json
and replace:
YOUR_GIGGY_API_KEY
in the local configuration only.
Set:
export GIGGY_API_KEY="giggy_sk_..."
Initialize:
./examples/initialize.sh
List tools:
./examples/list-tools.sh
List public voices:
./examples/list-voices.sh
generate_speech returns durable generation metadata.
It does not return live MP3 or PCM audio bytes through MCP.
For progressive PCM audio, use:
POST https://api.giggy.ai/v1/text-to-speech
with:
mode=streaming
output_format=pcm_24000
Speech API documentation:
https://giggy.ai/docs/speech-api
OpenAPI:
https://api.giggy.ai/v1/openapi.json
Runnable examples:
https://github.com/giggy-ai/giggy-examples
Pricing:
https://giggy.ai/pricing
Official SDK and runnable examples: