StreamYard (No MCP Server Available)
Updated June 2026The StreamYard (No MCP Server Available), built by StreamYard (no MCP server yet), provides no Model Context Protocol server exists for StreamYard today, official or community. It is community-built and best for Communication.
by StreamYard (no MCP server yet)
About
No Model Context Protocol server exists for StreamYard today, official or community. A GitHub Search API sweep for "streamyard mcp" returned zero results, and a broader "streamyard" search surfaces only clones and side projects — StreamYard clone tutorials, a past-broadcast downloader, an Elgato Stream Deck control guide, and a browser extension that adds Google Meet keybindings to broadcasts — none of which speak MCP. The `streamyard` GitHub organization does exist but holds just three forked developer utilities (ts-node-dev, typeorm, pnpm-isolate-workspace) with no product or API tooling, and no `streamyard-mcp` package is published on npm. The underlying reason is that StreamYard, now owned by Hopin, does not offer a public REST API for stream, guest, or branding management, so there is no surface for anyone to wrap in an MCP server. StreamYard itself remains a popular browser-based live studio for multi-guest interviews, branded overlays, and simultaneous streaming to YouTube, Facebook, and LinkedIn. If you need AI-assistant control over a live broadcast today, the practical alternatives in this same category are the Restream MCP Server, which exposes real channel management, stream start/stop, and analytics tools over Restream's public API v2, and the OpusClip MCP Server for post-broadcast clipping and social publishing. This entry is kept as a placeholder so the "streamyard mcp" search term stays discoverable and will be replaced with real data if StreamYard or the community ships a server.
Trust verdict
How grades are computed →No repository for this entry resolves against the live GitHub API, so there is nothing to verify. It is deliberately left unscored rather than given a number we cannot stand behind.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Source verificationunknown
No repository for this entry resolves against the live GitHub API. Without a confirmed source there is nothing to inspect, so this entry is excluded from trust scoring entirely rather than scored on catalog metadata alone.
Categories
Works With
Frequently Asked Questions
What is StreamYard (No MCP Server Available)?
Who built StreamYard (No MCP Server Available)?
Is StreamYard (No MCP Server Available) free?
How do I install StreamYard (No MCP Server Available)?
What does StreamYard (No MCP Server Available) integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Install
- source
Repo recency not yet available for this server.
Quick Info
- Install Type
- source
- Author
- StreamYard (no MCP server yet)
- Categories
- 2
- Integrations
- 2
Related Servers
Slack MCP Server
The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.
Figma MCP Server
There are three different Figma MCP servers and the install command on most listings belongs to the one Figma no longer leads with, so start with which you are choosing. **Figma's recommended server is now the hosted remote one at `https://mcp.figma.com/mcp`** — nothing to install, OAuth in the client, attached with `claude mcp add --transport http figma https://mcp.figma.com/mcp`. It is also the only one with the write and cross-file tools (`use_figma`, `generate_figma_design`, `generate_diagram`, `create_new_file`, `search_design_system`, asset upload and download). **The Dev Mode desktop server ships inside the Figma Desktop app** — enable it in Dev Mode (Shift+D) from the MCP server section of the inspect panel and the app opens a local endpoint at `http://127.0.0.1:3845/mcp`. Figma's docs now describe the desktop server as being for specific organisation and enterprise cases and recommend the remote one instead. Because it runs in the app, it reads whatever you have selected on the canvas: exact colors, typography, spacing, auto-layout constraints, component variants, and — the part a token-based reader cannot do — your Code Connect mappings, so it emits your component names rather than generic divs. It requires a Dev or Full seat on a paid plan and the desktop app must be open. The repository linked here is `figma/mcp-server-guide`, Figma's own setup guide; Figma does not publish the server's source. **The community alternative is Figma-Context-MCP by GLips** (15,500+ stars), installed as `npx figma-developer-mcp --figma-api-key=YOUR_FIGMA_ACCESS_TOKEN`. It authenticates with a Personal Access Token from Figma Settings → Personal Access Tokens and calls the REST API, so it needs no desktop app, works headlessly in CI, and can read any file your account can open — including from a free plan. It exposes the document JSON, node lookup by ID, component listing, text extraction, and rendered-image download. The practical split: pick the official server when design-to-code fidelity and Code Connect matter and you are already paying for Dev Mode; pick GLips when you need automation, a free plan, or a machine with no Figma app installed. Both let an assistant translate a frame into accurate React, Tailwind, or plain HTML/CSS instead of guessing from a screenshot.
Twilio MCP Server
Twilio's official MCP server, built by the Twilio Alpha team and published as @twilio-alpha/mcp, exposes the entirety of Twilio's public API surface to AI assistants over the Model Context Protocol. Rather than hand-writing tool wrappers, the server auto-generates MCP tools directly from Twilio's OpenAPI specs, so it stays in sync with new Twilio products (Voice, Messaging/SMS, Verify, Lookup, Conversations, and more) as they ship. Because a full API surface can blow past an LLM's context window, the server supports --services and --tags flags to scope which Twilio products are loaded into a given session, keeping tool lists small and relevant. Authentication uses a Twilio Account SID paired with an API Key/Secret pair (created in the Twilio Console), passed as a single credential string at launch rather than long-lived account credentials. The monorepo also ships a companion openapi-mcp-server package that can turn any OpenAPI spec into an MCP server using the same generator, useful for teams building on top of Twilio's partner or vertical APIs. Twilio's security guidance explicitly recommends against running community MCP servers alongside the official one to reduce the risk of a compromised third-party tool touching production SMS, voice, or verification workflows tied to real phone numbers and customer data.
SendGrid MCP Server
There is no official SendGrid MCP server, and that is the first thing worth knowing if you searched for one. Twilio owns SendGrid and does publish an official MCP server at twilio-labs/mcp, but that server is generated from Twilio's own Public API specs and covers none of SendGrid's v3 email endpoints — connecting it will not give an assistant a way to send an email or touch a contact list. Twilio's own developer blog acknowledges the gap by publishing a walkthrough on building a SendGrid MCP server yourself rather than shipping one. This entry therefore tracks the most established community implementation, Garoth/sendgrid-mcp (TypeScript, 29 stars), which wraps the SendGrid v3 Marketing API. Its tool surface is broader than most email servers: contact management (list_contacts, add_contact, delete_contacts, get_contacts_by_list), list management (list_contact_lists, create_contact_list, delete_list, add_contacts_to_list, remove_contacts_from_list), sending (send_email for one-off transactional mail with optional dynamic-template data, and send_to_list which creates a SendGrid Single Send against one or more list IDs), dynamic templates (create_template, list_templates, get_template, delete_template), plus get_stats, validate_email, list_verified_senders and list_suppression_groups. Those last two exist because SendGrid rejects sends from unverified senders and requires either a suppression_group_id or a custom_unsubscribe_url on a Single Send, so an agent has to look both up before it can complete a campaign. The README is explicit that only v3 APIs are supported — legacy templates will not work. Install is from source: git clone, npm install, then point your client at the built entrypoint with SENDGRID_API_KEY in the environment. Two cautions. The npm package named sendgrid-mcp is a different project (deyikong/sendgrid-mcp, 3 stars, which does offer a READ_ONLY mode) — do not assume npx installs the repo described here. And this server exposes delete_contacts, delete_list and delete_template, which are irreversible against a live marketing database; scope the API key narrowly rather than granting full access.
Resend MCP Server
The Resend MCP Server is Resend's official Model Context Protocol integration, letting AI assistants send and receive transactional email, manage contacts, broadcasts, and domains directly from Claude, Cursor, or any MCP-compatible client. Resend offers two ways to connect: a fully hosted remote server at mcp.resend.com (Streamable HTTP, no local install, OAuth login on first connect) that works well for Claude web/desktop and Cursor, or the same open-source code run locally via `npx resend-mcp` (published to npm as `resend-mcp`) using stdio or HTTP transport for CI, headless agents, or self-hosted setups. Authentication is either OAuth (hosted mode, browser-based) or a Resend API key passed as a Bearer token — handy for servers where a browser login isn't possible. Setup is documented for Claude Code, Claude Desktop/web, Cursor, Windsurf, Codex, and GitHub Copilot in VS Code. Typical use: ask Claude to "send a welcome email to this new signup using our verified domain" or "list contacts added to the newsletter audience this week," and the MCP server routes the request through your existing Resend account — no custom SMTP or REST integration code required. With 546+ GitHub stars, it's one of the most widely adopted first-party MCP servers in the email/transactional-messaging category.
Sponsored
ElevenLabs
Free TierThe leading voice AI platform. Add lifelike text-to-speech to your Claude agents via the ElevenLabs MCP server.
Try ElevenLabs free →