MCP server
Connect ChatGPT, Claude, Claude Code, Codex, Cursor and any MCP client to Gutlog.
The MCP server is at https://getgutlog.com/api/mcp over streamable HTTP. It exposes one tool per op, with the op's description and input schema, and marks read-only and destructive tools so clients can auto-approve reads and confirm the rest. It is the main way to use Gutlog: your assistant looks at a meal photo, sends log_meal a draft, and reads your diary back. The setup page has every client's clicks with copy buttons; this page is the reference.
Authentication
- OAuth (recommended): ChatGPT, Claude and most MCP clients sign you in through the browser; no key. The server answers 401 with a pointer to its protected resource metadata and the client does the rest.
- API key: send
Authorization: Bearer gutlog_…, for clients without OAuth. Create keys in the web app, withnpx @meterapp/gutlog login, or with thecreate_api_keyop; narrow them with scopes.
No account yet? The catalog server at https://getgutlog.com/api/mcp/catalog needs no credential and serves get_pricing and create_checkout_link.
Setup
ChatGPT
Until the app is listed in ChatGPT's app directory: on chatgpt.com, Settings → Apps & Connectors → Advanced settings, turn on Developer mode, then Create a connector with the URL https://getgutlog.com/api/mcp and OAuth authentication. Choose it from the + menu in a new chat.
Claude.ai and Claude Desktop
Settings → Connectors → Add custom connector, URL https://getgutlog.com/api/mcp, then Connect and sign in. The desktop and mobile apps use the connectors of your account.
Claude Code
claude mcp add --transport http gutlog https://getgutlog.com/api/mcpThen type /mcp, pick the server and authenticate in your browser. The plugin adds the same server with skills and signs in the same way, with your browser:
/plugin marketplace add MeterApp/gutlog-plugins
/plugin install gutlog@gutlogOn a machine without a browser, add the server with your own key instead (the plugin never uses one):
claude mcp add --transport http gutlog https://getgutlog.com/api/mcp \ --header "Authorization: Bearer gutlog_…"Codex
codex mcp add gutlog --url https://getgutlog.com/api/mcpcodex mcp login gutlogOr with an API key:
# ~/.codex/config.toml
[mcp_servers.gutlog]
url = "https://getgutlog.com/api/mcp"
bearer_token_env_var = "GUTLOG_API_KEY"Cursor
Add to Cursor in one click, or:
{ "mcpServers": { "gutlog": { "url": "https://getgutlog.com/api/mcp" } }}VS Code
Install in VS Code in one click, or:
code --add-mcp '{"name":"gutlog","type":"http","url":"https://getgutlog.com/api/mcp"}'Gemini CLI
gemini mcp add --transport http gutlog https://getgutlog.com/api/mcpOther clients
Any client that speaks streamable HTTP works with the URL, signing in with OAuth or sending an API key:
{ "mcpServers": { "gutlog": { "type": "http", "url": "https://getgutlog.com/api/mcp", "headers": { "Authorization": "Bearer gutlog_…" } } }}For hosts that only speak stdio, the CLI bridges to the hosted server:
{ "mcpServers": { "gutlog": { "command": "npx", "args": [ "-y", "@meterapp/gutlog", "mcp" ], "env": { "GUTLOG_API_KEY": "gutlog_…" } } }}Things to ask
- [a photo] “Log this.” (the assistant drafts and calls
log_meal) - “Log a banana and a black coffee for a snack.”
- “What did I eat today, and how much protein was it?” (
get_day) - “What is left to set up?” (
get_onboarding)
Editing, clean verdicts, symptoms, triggers and programs arrive as their ops ship; the API reference lists what is live, and the server's tool list always matches it.
Troubleshooting
- No tools after adding the server: start a new chat or session; most clients load tools when it starts.
- 401 or “needs login”: sign-in did not finish or expired. Reconnect from the client's MCP or connector settings.
- No developer mode in ChatGPT: your plan or workspace may not offer it yet. Use Claude, a coding agent or the web app meanwhile.
Agents should read agents.md for the rules, such as never buying a plan without a person's approval.