Claude connector — Stillhaven

Connecting

Stillhaven is not in Claude's connector directory, so you add it yourself. It takes about a minute and you only do it once. You need a paid Stillhaven plan and a version of Claude that allows custom connectors.

1. Open the connector settings in Claude

Settings, then Connectors, then Add custom connector.

2. Fill in these four things

Claude asks for more than a name and an address. The two dropdowns matter, and the defaults are not what you want, so it is worth copying this exactly.

Name: Anything you like. Stillhaven is the obvious one.
URL: https://mcp.stillhaven.io/mcp
Authentication: Required when the server asks. Not "None", even if Claude has ticked it for you. Claude checks by asking our server what it can do without signing in, and the answer is "see the list of tools" — so it concludes no sign-in is needed. It is wrong: reading your library needs one, and every tool will fail if you leave it on None.
OAuth client: Use your own OAuth client, with the client ID below. The other two options cannot work with our sign-in provider: it offers neither dynamic registration nor hosted client metadata.

3. The client ID

Paste this into the Client ID box:

5bdgij25frdr8uu8e4deu4k6as

Leave the client secret blank. There isn't one. This is a public OAuth client, which is why the ID above can sit on a documentation page: it identifies the application, it does not authorise anything. Your sign-in is what grants access, and the exchange is protected by PKCE.

4. Connect, and sign in

Press Connect. Claude sends you to our sign-in page, where you sign in with your Stillhaven account and approve what the connector may do. The sign-in is ours: Claude never sees your password, and never receives it.

Sign in with the account that has your videos. An email that has never been added to a Stillhaven workspace will be told so rather than left guessing.

Permission is asked for as it is needed, not all at once. Reading your library is approved when you connect; the first time you ask Claude to change something, it asks you to approve that separately.

What it does

The connector gives Claude 13 tools. Claude picks the one that fits what you asked for, and tells you what it did. Nothing runs without you asking for it.

Reading

get_account: Get account and usage
list_videos: List videos
search_videos: Search videos by title
get_video: Get one video
get_video_analytics: Get video analytics
list_channels: List channels
get_channel: Get one channel

Changing things

Claude tells you before it changes anything, and every change here is one you could make yourself in the console.

update_video: Update a video
create_upload: Start a video upload
trash_video: Move a video to trash
restore_video: Restore a video from trash
set_channel_videos: Set a channel playlist
set_allowed_domains: Set where a video may be embedded

Uploading is the one thing the connector cannot finish on its own. It can start an upload and tell you what to send where, but your file goes straight from your machine to storage: video never passes through the connector.

What it cannot do

This list is the point, so it is worth reading. These are not features that have not been built yet. They are decisions, and the connector has no way to do any of them even if it were asked.

Delete anything permanently: Trashing a video is reversible for 30 days, and permanent deletion exists only in the console. There is no API route for it at all, so a connection cannot be talked into one.
Change your plan, your billing, or your card: No scope grants any of it, and the API has no route that touches money.
Add, remove, or change team members: Who can reach your library is decided by a person in the console, not by a conversation.
Read or set share page passwords: A password is write-only even in the console API. Tools can see whether a page is protected, never what the password is.
Invite or remove channel viewers: Granting somebody access to private video is worth doing deliberately. It stays in the console for now.
Change your branding or your logo: How your share pages look is a design decision you make once and expect to stay made. No scope grants it, so a conversation cannot change it by accident.
Create or revoke API keys: A credential that can mint credentials is a credential that never really expires.
See anything belonging to another account: Every request is scoped to the one account you signed in with, and every record is re-read and checked before it is returned or changed.

When it does not work

Every one of these has actually happened, and each has a different fix.

Every tool fails, with no mention of signing in: Authentication is probably set to None. Claude detects that as the answer because our tool list is readable without signing in, but using a tool is not. Edit the connector and set it to Required when the server asks.
Claude cannot complete the sign-in: Check the OAuth client is set to Use your own OAuth client with the client ID above, and that the secret box is empty. Automatic registration and hosted client metadata both fail against our sign-in provider, which supports neither.
It says your sign-in is not attached to a workspace: You signed in with an email that is not on a Stillhaven account. Use the address you use for the console, or ask an admin to invite that one.
It stopped working after you disconnected it in the console: That is the disconnect holding, and it is meant to. Signing in again from Claude will not restore it. Open Settings then API in the console and press Allow Claude again first.
Claude asks to sign in again in the middle of something: Normal. Sign-ins are short lived and renew quietly; you only see it when the renewal cannot happen, such as after a disconnect. Signing in again is safe and changes nothing about your library.
You are on the free plan: The connector is not included. See plans.
You are using Claude Code: It cannot connect to Stillhaven, and this is not something you can configure around. Claude Code signs in through a local address that changes every time, and our sign-in provider only accepts addresses registered in advance. Claude on the web and in the desktop app are unaffected. If you want Stillhaven in a terminal, the API is the way.

Disconnecting

Two ends, and they do different things. Doing both is the thorough version.

From Stillhaven

Sign in to the console, open Settings then API, and press Disconnect Claude on the Claude card. Access stops within moments and stays stopped: signing in again from Claude will not bring it back, because the connection remains switched off until you press Allow Claude again on that same card.

This is the one to use if you think something is wrong. It does not touch your videos.

From Claude

Remove the connector under Settings then Connectors. That clears what Claude holds at its end. Left alone, an unused connection expires on its own after thirty days.

Plans

The connector is included on every paid plan, alongside the API: Creator, Studio and Broadcast. It is not available on the free plan. What Claude can reach still depends on your plan, so a tool that touches private channels will say so on a plan that does not have them.

What Claude sees

Only what a tool returns, only for the account you signed in with, and only when you ask. Titles, folders, durations, view counts, share links and embed codes are the sort of thing a tool hands back.

Your video is never sent to Claude. Tools return links and information about a video, never the file, and never a transcript unless a tool that returns one is added later and this page says so.

The connector holds no copy of your library and no credential of its own. It passes your request to the same API a developer would use, with your own sign-in attached, and passes the answer back.

Building something of your own instead? The API reference covers the same surface directly.