LLM-Friendly Embed Codes MCP server

Which servers in the official MCP registry are LLM-Friendly Embed Codes's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to LLM-Friendly Embed Codes

Whose server it is

Registry nameio.github.wistia/wistia-api-mcpendpoint on the vendor's domain

The server's endpoint is on wistia.com and its publisher carries the brand's name. That is the weakest of the three ties: an endpoint alone proves less than a verified namespace.

When we asked itchecked 2026-10-08

Staterequires sign-inchecked 2026-10-08

On 2026-10-08 the server answered and asked for a sign-in with a LLM-Friendly Embed Codes account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "wistia-api-mcp": {
      "type": "http",
      "url": "https://api.wistia.com/mcp/api"
    }
  }
}

The first time it connects, the client opens a LLM-Friendly Embed Codes sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.