What is MCP?
The Model Context Protocol is an open protocol that lets AI assistants securely interact with external systems. Gumnut’s MCP server implements this protocol, giving your assistant authenticated, rate-limited access to your Gumnut library.Server URL
Supported Features
The MCP server exposes Gumnut’s main photo operations, including:- Assets: Upload, list, update, and delete photos and videos
- Albums: Create and manage photo collections
- Faces: Review face detections, add manual face boxes for misses, and associate faces with people
- Libraries: Organize content across multiple libraries
- People: Access facial recognition and people management
- Search: Perform semantic and metadata-based searches
- Image understanding: Let compatible MCP hosts inspect image assets directly for tasks like reading text, describing a scene, or answering questions about visible details
MCP Apps
Gumnut supports the MCP Apps standard, enabling rich interactive UI experiences within MCP-compatible clients. When you use a client that supports MCP Apps, you’ll get visual photo grids, album cards, and other interactive elements alongside the standard tool-based interactions.Let your assistant inspect photos
Gumnut’s MCP server includes a nativeview_asset tool for image-aware workflows. When your MCP client supports image results from tools, the assistant can look at an image asset itself rather than only its metadata or a signed asset_url meant for client rendering.
This is useful when you want your assistant to:
- Read text from signs, receipts, slides, documents, or screenshots in your library
- Describe what is visible in a specific photo or image asset
- Answer questions about details such as objects, colors, or layout
MCP tool calls follow the same weighted rate-limit model as the REST API. Each tool call is charged once using the comparable REST operation, so
view_asset counts like a metadata read rather than a full file download. See Rate Limiting for the cost classes and retry guidance.Authentication
The MCP server supports multiple authentication methods:- API Keys: For CLI tools and server applications —
Bearer apikey_... - OAuth 2.1: For browser-based tools and web applications —
Bearer oat_... - Session Tokens: Automatic session management through cookies