Setting up the MCP server
Endpoint, auth and tools of the footage.one Model Context Protocol server.
Endpoint
https://mcp.footage.one/mcp
Transport: Streamable HTTP (compatible with MCP clients from spec version 2025-03-26).
Auth
The MCP server uses OAuth as its only supported auth mechanism. On the first tool call, the client opens the footage.one login in the browser; the user signs in with their regular account; the client manages the token lifecycle automatically thereafter.
For Claude Desktop, adding the server URL is all that is needed — see Connecting Claude Desktop.
API token at the MCP endpoint
Currently not yet available (work in progress). API tokens (from your account) work exclusively against the REST API directly — see REST API Quickstart and API tokens. If you need headless integrations without a browser login and the MCP endpoint is required, contact support.
Tool domains
| Domain | Example tools |
|---|---|
| Assets | search_assets, get_asset, update_asset, add_keywords_to_asset, generate_description |
| Albums | list_albums, create_album, add_assets_to_album, share_album |
| Episodes | list_episodes, add_assets_to_episode |
| Storage | list_storages, browse_storage, import_storage_items |
| Keywords | search_keywords, get_keyword_suggestions, disambiguate_freewords |
| Account / Teams | get_account_info, list_teams |
The complete tool list with schemas is provided by the MCP server itself on a tools/list call.
Server card
Machine-readable description at https://www.footage.one/.well-known/mcp/server-card.json.