How to Use the Huddle01 (Web3 Video API) MCP in Windsurf

Q: How do I add the Huddle01 (Web3 Video API) MCP Server to Windsurf?

Open your /.codeium/windsurf/mcpconfig.json file and add the server configuration under the mcpServers key. Alternatively, use the Windsurf Settings UI, navigate to Cascade, and add it via the MCP Servers panel. Once saved, click Refresh in the MCP panel to let Cascade discover the tools.

Q: Can Windsurf handle room locking during creation with Huddle01 (Web3 Video API)?

Yes, the createroom tool requires a parameter specifying if the room is locked. When you tell Cascade to provision a room, it reads this parameter and applies the lock setting during the API call.

Q: Can I filter meeting recordings by session ID?

Yes, the getrecordings tool accepts a sessionId filter. This allows you to pinpoint the exact recording file for a specific meeting instance instead of parsing a massive list.

Let Windsurf autonomously chain room creation, live session tracking, and meeting recording checks without leaving your editor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Huddle01 (Web3 Video API) MCP to Windsurf

Create your Vinkius account to connect Huddle01 (Web3 Video API) to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Huddle01 (Web3 Video API) with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomously spin up token-gated rooms

The `create_room` tool generates a new Huddle01 meeting space and requires you to declare if the room is locked. When you ask Cascade to set up a new meeting environment, it reads your local project context, determines if the room requires host validation, and executes the call. You don't need to write boilerplate setup scripts. Windsurf handles the room configuration and feeds the resulting room ID straight into your ongoing development flow.

Chain live session monitoring with Cascade

The `get_live_sessions` tool fetches currently active rooms, allowing Windsurf to keep tabs on your live traffic. When Cascade notices active sessions, it automatically steps through `get_live_session_details` and `get_live_session_participants` to map out who is online. This workflow happens without manual intervention. Your agent chains these queries to build a live picture of your dApp's video usage and hands you the structured data immediately.

Audit past meetings using this MCP Server

The `get_room_sessions` tool retrieves every meeting held in a specific room, giving your IDE direct access to historical call logs. If you need to track down specific recordings, Cascade triggers `get_recordings` with a sessionId filter to locate the exact media files. Instead of jumping back and forth to an external developer portal, you let your agent pull the files. It handles the API requests in the background and presents the file paths right in your active workspace.

Setup guide

Set up Huddle01 (Web3 Video API) MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Huddle01 (Web3 Video API) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Huddle01 (Web3 Video API) payment history." If connected, Cascade will call the Huddle01 (Web3 Video API) tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "huddle01-web3-video-api-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Huddle01. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Huddle01 (Web3 Video API) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Huddle01 (Web3 Video API) MCP in Windsurf

Open your `~/.codeium/windsurf/mcp_config.json` file and add the server configuration under the `mcpServers` key. Alternatively, use the Windsurf Settings UI, navigate to Cascade, and add it via the MCP Servers panel. Once saved, click Refresh in the MCP panel to let Cascade discover the tools.

Yes, the `create_room` tool requires a parameter specifying if the room is locked. When you tell Cascade to provision a room, it reads this parameter and applies the lock setting during the API call.

Cascade reads your prompt, realizes it needs real-time data, and calls `get_live_sessions`. It then takes those active session IDs and automatically queries `get_live_session_participants` without waiting for your permission.

Yes, the `get_recordings` tool accepts a sessionId filter. This allows you to pinpoint the exact recording file for a specific meeting instance instead of parsing a massive list.

Your Huddle01 API key remains inside the local Windsurf configuration file on your machine. The MCP Server executes inside a secure V8 isolate sandbox, meaning your usage metrics retrieved via `get_metrics` are never exposed to external third-party servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript