Connect Gather Voices to Claude

Manage your video requests, creators, galleries, and groups through natural conversation — powered by Gather Voices' MCP integration with Claude.

What is this?

Gather Voices now supports the Model Context Protocol (MCP), an open standard that lets AI assistants like Claude interact directly with your Gather Voices tenant. Once connected, you can run your video collection program using natural language instead of clicking through the dashboard.

Ask Claude things like:

"How many video submissions came in this week across all groups?"
"Show me open requests in the Marketing group"
"Create a new video request in the Customer Stories group titled 'Q2 testimonials'"
"List the most recent 10 videos submitted to request #4821 and summarize the themes"
"Which galleries are published and what is the embed link for each?"
"Get me the MP4 and thumbnail URL for video 77321"

Claude calls your Gather Voices tenant securely behind the scenes and returns real data from your account — scoped to the API token you provide.

What Claude can do once connected

The Gather Voices connector exposes the following capabilities to Claude:

Domain	Tools
Groups	`list_groups`, `get_group`
Requests	`list_requests`, `get_request`
Videos	`list_videos` (filterable by group, request, user, or recording device), `get_video` (returns MP4 URL, thumbnail, embed code, tags, branded-version pointers)
Galleries	`list_galleries`, `get_gallery` (returns public URL, embed code, featured video, auto-posting config)

Every tool is read-optimized for inspection and reporting. Mutating operations (create/update/archive) are planned — see the Support section for roadmap questions.

Prerequisites

A Gather Voices account with API access enabled
A Claude Pro, Max, Team, or Enterprise plan at claude.ai
Your Gather Voices API access token (generated from the GV admin portal under Settings → API Keys)

Getting started

Step 1 — Add the Gather Voices connector

Open claude.ai or the Claude Desktop app
Go to Settings → Connectors
Click Add custom connector
Enter the Gather Voices MCP server URL:
```
https://mcp.gv-one.com/sse
```
Click Save

Step 2 — Connect and authenticate

After saving, you'll see Gather Voices listed under Settings → Connectors
Click the Connect button next to Gather Voices
A browser window will open showing the Gather Voices authorization page

Paste your credentials:

Field	Description	Example
Access Token	Your Gather Voices API access token from the admin portal	`gv_live_a1b2c3d4e5f6…`

Click Authorize Claude
On success, the browser will redirect back to Claude automatically
The connector status will show as Connected

Tip: If you don't have an API token yet, log in to your Gather Voices admin portal, go to Settings → API Keys, and click Generate new key. Copy it immediately — it won't be shown again.

Step 3 — Start using it

Open a new chat and simply ask Claude about your video program:

You: Hello Gather Voices, how did this week's video collection go?

Claude: Here's your snapshot for the past 7 days:
  - 14 active requests across 5 groups
  - 68 new video submissions
  - Top group: "Customer Stories" with 23 submissions
  - 2 requests near their deadline with fewer than 3 submissions
  - 1 gallery published: "Q2 Testimonials" (12 videos)

Security and privacy

Your API token never passes through Claude. Authentication happens entirely in your browser. The Gather Voices MCP server validates your API token against Gather Voices, then issues a short-lived, signed JWT that wraps it. Claude only ever holds the JWT — never the raw API key.
OAuth 2.1 + PKCE is used for the Claude ⇄ MCP-server handshake, preventing token interception even on shared networks.
Tenant isolation is enforced. Your token is scoped to your Gather Voices tenant. You can only access data within your own account.
API-key permissions apply. The scopes granted to the API token you paste are exactly what Claude can do. Generate a read-only key if you only want Claude to query, not mutate.
The JWT expires in 24 hours. After that Claude re-authenticates automatically using the stored GV token. You can revoke access at any time by deleting the API key in the GV admin portal.
Every tool call is logged. All Claude-initiated actions are recorded in the same audit trail as direct API usage.

Disconnecting

To remove the Gather Voices connector:

Go to Settings → Connectors in Claude
Find the Gather Voices entry
Click Disconnect

This immediately invalidates Claude's JWT. To fully revoke access on the Gather Voices side, also delete the API key from the GV admin portal under Settings → API Keys.

Each user must connect separately

Gather Voices MCP connections are per-user. You cannot share access by sending someone a chat link. Each person must:

Add the connector in their own Claude account
Authenticate with their own Gather Voices API token
Start a new chat after connecting

This ensures every user only sees and modifies data their API token permits.

Reconnecting after a server update

When we release a new version of the Gather Voices MCP server, previously issued JWTs are invalidated and you may see errors like "No active session" or "Connection closed". If this happens:

Go to Settings → Connectors
Click Disconnect next to Gather Voices
Click Connect again and paste your API token

Your underlying API token remains valid — only Claude's session token needs to be refreshed.

Support

Having trouble connecting? Contact us at support@gathervoices.co or visit help.gathervoices.co/mcp for the latest updates.