Slate for Claude
MCP server · Team plan
Claude can watch your recordings.
Hand Claude a Slate link and it reads the transcript, sees which page was on screen at each moment, takes screenshots where it matters, and tags or comments on the recording as you.
https://api.slatevideo.com/mcp Works with Claude.ai, Claude Desktop, Claude Code, Cursor, VS Code and anything else that speaks MCP. Agents: this page is also Markdown, and the site has an llms.txt.
What it is for
Recordings Claude can actually use.
- Bug reports, read for you Paste the link to a recording of something breaking. Claude reads what was said, sees which page was open at each moment, takes screenshots where it goes wrong and writes up the ticket.
- Catch up without watching Ask what a walkthrough covered, what a teammate decided, or what the comments asked for. Answers come with the moment in the recording, so you can jump to it.
- Keep the library in order Have Claude tag recordings, give them clearer titles and summaries, answer comments and resolve the ones it has dealt with.
- Hand Slate a file Give Claude a video file, and a .vtt transcript if you have one, and it uploads it to your library, where it gets a transcript, a title and a summary like anything you recorded.
Things to ask
- Here is a bug report: <link>. Find where it fails, screenshot that moment and draft a Jira ticket.
- What did the recordings tagged "onboarding" this week decide? Quote the moments.
- Read the comments on <link> and tell me which ones still need an answer.
- Tag every recording about the billing page with "billing".
How it works
Claude asks. Slate answers.
The connection is pull, not push. Slate sends nothing anywhere on its own: no webhooks, no sync, no copy of your library in Claude. Each time you ask, Claude calls one of Slate’s tools and gets back only what your account could already open.
- 01 You ask Paste a Slate link or ask about your recordings.
- 02 Claude calls a tool Over MCP, signed in as you or as a team key.
- 03 Slate answers Only what that account could already open on the web.
It reads · 10 tools
Transcripts, what was on screen, screenshots, comments, reactions, tags, titles and summaries, and who watched (owners and admins).
It writes · 7 tools
Comments, resolving them, tags, titles and summaries, and new uploads.
It never
It cannot delete recordings, change who can see them, share them, or touch billing or your team.
Connecting
Four steps, under a minute.
- 01 Add the connector Claude.ai or Claude Desktop: Settings, then Connectors, then Add custom connector. Name it Slate and paste the server URL. On a Team or Enterprise plan, an owner adds it once for everyone.
- 02 Choose Connect Claude opens Slate in a new window.
- 03 Sign in to Slate With Google or your email. Already signed in, and this step goes by on its own.
- 04 Approve Slate shows which app is asking and what it will be able to do. Choose Allow, and you are back in Claude with Slate connected.
- Server URL · Claude.ai and Claude Desktop
-
https://api.slatevideo.com/mcp - Claude Code · Then run /mcp inside Claude Code to sign in.
-
claude mcp add --transport http slate https://api.slatevideo.com/mcp - Cursor · .cursor/mcp.json
-
{ "mcpServers": { "slate": { "url": "https://api.slatevideo.com/mcp" } } } - VS Code · .vscode/mcp.json
-
{ "servers": { "slate": { "type": "http", "url": "https://api.slatevideo.com/mcp" } } } - Anything else
- Any client that speaks Streamable HTTP. It finds the sign-in on its own from the server URL (OAuth 2.1 with PKCE and dynamic client registration; metadata at /.well-known/oauth-authorization-server).
Connecting needs a seat on a Slate Team plan. Without one, Claude is told so and pointed at pricing.
Bots, CI and shared agents
A key for the team, not a person.
Signing in connects Claude as you. For a bot in Slack, a CI job that reads bug reports, or an agent the whole team shares, a team API key connects as the team instead: no browser, no one’s account, and nothing it can do beyond what you allowed.
- 01 Make a key A team admin or owner opens Settings, then API keys, names the key, picks what it may do and, if it should run out, when.
- 02 Copy it once The key starts slk_ and is shown that one time. Slate keeps only a hash of it.
- 03 Hand it to the bot Send it as a bearer token to the same server URL. No browser, no sign-in.
- Claude Code, as the team
-
claude mcp add --transport http slate https://api.slatevideo.com/mcp \ --header "Authorization: Bearer slk_..." - Anything else
-
Send
Authorization: Bearer slk_…tohttps://api.slatevideo.com/mcp.
What a key may do
| Scope | Allows |
|---|---|
videos:read | Every read tool. Always included: a key that may tag has to be able to find what it is tagging. |
tags:write | add_tag and remove_tag, with the team’s existing tags. |
comments:write | add_comment, posted under the key’s name as “<name> (API key)”. |
- A key reads what a team admin reads in the team’s library: recordings shared with the team or wider. Never one kept private or shared only with named people, never another team’s.
- It manages nothing: no uploads, renames, resolving comments or viewer lists.
- Up to 10 live keys a team. A key lasts until revoked unless you set an expiry.
- Revoking one in Settings cuts it off on its next call. Each call is logged against the key.
- It works on the MCP server only, and only while the team’s plan is live.
Tools
17 tools, and what each one needs.
Signed in, Claude sees exactly what your Slate account sees and can change only what you could change yourself. With a team key, it gets the tools its scopes allow.
| Tool | What it does | Changes | API key |
|---|---|---|---|
get_me Who am I | The signed-in person (or the key’s team), their teams and plan. | Reads | Any key |
find_videos Find recordings | Search your library and your team’s by words in the title, summary or transcript, by tag or by date. | Reads | videos:read |
get_video Get a recording | Title, summary, tags, the pages that were on screen and when each came up, and counts. | Reads | videos:read |
get_transcript Get the transcript | What was said, as timestamped lines. Narrow it to a stretch, or to the lines that mention something. | Reads | videos:read |
get_activity What was on screen | Which app, window and web page had focus at each moment (Mac app recordings). | Reads | videos:read |
get_screenshot Screenshot at a moment | A still frame as an image, a run of them, or a spread across a stretch. Up to 8 a call. | Reads | videos:read |
get_comments Get comments | The thread, the moment each comment is pinned to, and whether it is resolved. | Reads | videos:read |
get_reactions Get reactions | Emoji reactions and their moments. | Reads | videos:read |
get_viewers Who watched | Who watched and how far they got. Owners and team admins only. | Reads | People only |
list_tags List tags | The tags you can use, personal and team. | Reads | videos:read |
add_comment Add a comment | Comment as you, optionally pinned to a moment. The owner is notified as usual. | Writes | comments:write |
resolve_comment Resolve a comment | Resolve or reopen a comment. Owner, team admin or the comment’s author. | Writes | People only |
add_tag Tag a recording | Add a tag by name or id, creating it if your team allows. | Writes | tags:write |
remove_tag Untag a recording | Take a tag off. The tag itself stays. | Writes | tags:write |
update_video Rename or summarize | Change a title or summary. Owner or team admin only. | Writes | People only |
upload_video Upload a video | Start a new recording from a video or audio file (up to 5 GB), with an optional title, summary and .vtt transcript. Returns the upload URL and the curl command that sends the file. | Writes | People only |
finish_upload Finish an upload | Close the upload so the recording processes: transcript, title and summary, like anything recorded. | Writes | People only |
Pointing at a recording
Paste whatever link you have.
- Any link works A share link on any domain (…/v/abc123), the share id out of one, the library id, or an /edit/ link. Custom domains included.
- One clock Every moment is seconds on the finished recording, after cuts and stitched clips, and can be written as 83, "1:23" or "1m23s". The transcript, activity, comments, reactions and screenshots all share it.
- Not found means not yours A recording the account could not open on the web is “not found” here too. The same rules decide both.
Your data
How it signs in, and how to disconnect.
- Claude signs in with OAuth 2.1 and PKCE on Slate’s own consent page. Slate never sees your Claude password, and Claude never sees your Slate one.
- We keep a hash of each token, never the token, and a record of which tool was called and whether it worked. Not your questions, and not what the tools returned.
- Nothing Claude reads through Slate is used for advertising or to train AI models.
To disconnect, choose Disconnect next to Claude under Claude and other AI tools in Slate’s Settings, or remove the connector in Claude. Either one stops it on the next call. A team key stops when an admin revokes it under API keys.
Questions about connecting Claude get an answer within two business days.