Setting Up the Gumnut MCP Server
This guide walks you through configuring the Gumnut MCP server in popular AI tools.Prerequisites
- A Gumnut account
- An MCP-compatible tool
Any MCP client
Gumnut runs a standard remote MCP server over HTTP, so a client that supports remote MCP servers can connect to it — provided it can also authenticate. Every request to the server carries your Gumnut credentials, so remote transport on its own isn’t enough: your client needs to support either the MCP OAuth flow or configurable request headers. The tools below have step-by-step instructions because they’re the ones people ask about most, not because they’re the only ones that work. To connect a client that isn’t listed, you need two things. The server URL:- OAuth — if your client can sign in to remote MCP servers, point it at the URL and it will open a browser window to authorize your Gumnut account. Nothing else to configure.
- An API key — if your client can’t do OAuth, or the sign-in flow gives you trouble, send the key as an
Authorizationheader instead.
headers block if you’re using OAuth. The exact keys vary between clients — some want an explicit transport field such as "type": "http" or "transport": "http" alongside the URL — so check your client’s documentation for its spelling.
Claude Code
Claude Code supports MCP servers natively through CLI commands or configuration files. When you connect, you’ll be prompted to authenticate with your Gumnut account via OAuth.Using the CLI (Recommended)
Add the Gumnut MCP server with a single command:--scope user flag:
Using JSON Configuration
Alternatively, add the configuration directly to your~/.claude.json file:
.mcp.json file in your project root with the same structure.
You can also authenticate with an API key instead of OAuth by adding an Or in JSON configuration:
Authorization header:Verify Installation
Check that the server is configured:/mcp command within Claude Code to see available servers and their tools.
Cursor
Cursor supports MCP servers through JSON configuration files. When you connect, you’ll be prompted to authenticate with your Gumnut account via OAuth.Configuration File Location
- Global (all projects):
~/.cursor/mcp.json - Project-specific:
.cursor/mcp.jsonin your project root
Configuration
Create or edit the configuration file:Using Cursor Settings UI
- Open Cursor and go to File > Preferences > Cursor Settings
- Select the MCP tab
- Click Add Server
- Enter the server details:
- Name:
gumnut - URL:
https://api.gumnut.ai/mcp - Transport:
http
- Name:
You can also authenticate with an API key instead of OAuth by adding an
Authorization header to the configuration:Verify Installation
After configuration, go to Cursor Settings > MCP to seegumnut listed as a registered server. Click refresh if needed.
Claude Web (claude.ai)
Claude on the web supports remote MCP servers through the Integrations feature.MCP integrations on Claude.ai require a paid plan (Pro, Max, Team, or Enterprise). Free accounts cannot connect to MCP servers—use Claude Code or Claude Desktop instead.
Setup Steps
- Go to claude.ai and sign in
- Click Customize then Connectors (or go directly to claude.ai/customize/connectors)
- Click + to add a new connector
- Enter the Gumnut MCP server URL:
- You’ll be prompted to authenticate with your Gumnut account via OAuth
- Save the connector
Using the Integration
Once configured, you can ask Claude to interact with your Gumnut library directly in chat:ChatGPT
ChatGPT supports MCP servers through custom apps.Gumnut will be added to the ChatGPT app store in the near future. In the meantime, you can connect manually using developer mode.
Setup Steps
- Open ChatGPT and go to Settings > Apps (or go directly to chatgpt.com/#settings/Connectors)
- Enable Developer mode
- Click Create app
-
Configure the app:
- Name:
Gumnut - Server URL:
https://api.gumnut.ai/mcp
- Name:
-
Expand Advanced settings. Under OpenID support, leave OIDC enabled unchecked, and under Default scopes, make sure
openidis not selected (profile,email, andoffline_accesscan stay selected).
Advanced settings → OpenID support: leave OIDC enabled unchecked

Advanced settings → Default scopes: openid unchecked, with profile, email, and offline_access selected
- You’ll be prompted to authenticate with your Gumnut account via OAuth
- Save the app
Using Gumnut in ChatGPT
Once configured, you can ask ChatGPT to interact with your Gumnut photo library directly in chat.Local and self-hosted models
You can use Gumnut with a model running on your own hardware:- The model generates the responses. It can run locally or in the cloud.
- The MCP client is the app that connects to Gumnut and calls its tools on the model’s behalf.
https://api.gumnut.ai/mcp over the network, and still authenticates as your Gumnut account.
How you connect depends on which layers your local setup covers:
- Apps that run models and act as an MCP client, such as LM Studio, need nothing extra from Gumnut. Add the server using the Any MCP client instructions and your local model can call Gumnut’s tools.
- Runners that only serve models, such as Ollama, have no MCP client of their own. Pair one with a separate MCP client and point that client at Gumnut. Ollama, for instance, documents running Claude Code against a local Ollama instance — from there, follow the Claude Code section above.
What to expect
Gumnut exposes a broad set of tools, and choosing between them is the hard part for a model:- Use a tool-calling model with a generous context window. Smaller models tend to pick the wrong tool, or ignore the tools entirely, as the list grows.
- Image understanding needs more than a vision model. For
view_assetto work, the model has to be vision-capable and the client has to pass image results from tools back to the model. Clients that only forward text will leave the assistant working from metadata alone. - Interactive MCP Apps widgets are client-side. Clients that don’t implement MCP Apps still get every tool — they render the results as text rather than as photo grids and album cards.