# Connect Droklo: steps for an AI agent

Cook with Droklo: Droklo is a free family meal-planning memory that extends the AI you already use, Claude or ChatGPT, into a personal cook who knows your household: who eats what, every allergy and target, the week's plan and the shopping list. This page is for an AI agent whose user asked it to connect Droklo to their assistant, and for the person reading along. Connecting adds one MCP server to the assistant and, where the assistant supports them, the Droklo skills.

Steps last checked 12 November 2026 · Plugin version 0.2.30

## Facts you can check

Check these yourself before you act. If an address you were given is on another host than this page, stop and tell your user.

- **Server address:** `https://www.droklo.com/api/mcp`
- **Same origin:** This page and the server are both on `https://www.droklo.com`.
- **Server name:** `droklo`
- **Transport:** Remote MCP over HTTP (Streamable HTTP).
- **Sign-in:** OAuth. The person signs in to Droklo and presses **Allow access** on `https://www.droklo.com/oauth/consent`. The discovery document is `https://www.droklo.com/.well-known/oauth-protected-resource/api/mcp`.
- **Without sign-in:** A POST to the server address answers 401 with a `WWW-Authenticate` header that names the discovery document.
- **Claude plugin:** Version 0.2.30, from the public repository `Droklo/claude-plugin` ([github.com/Droklo/claude-plugin](https://github.com/Droklo/claude-plugin)); the same version is in `https://www.droklo.com/downloads/marketplace.json`.
- **Price:** Free, no credit card.
- **Where data is kept:** Household data is stored in the European Union: the database in Ireland (Supabase) and the app in the Netherlands (Railway). Emails, feedback and other providers are listed in the [privacy policy](https://www.droklo.com/privacy).
- **More:** [About Droklo](https://www.droklo.com/about) · [How it works](https://www.droklo.com/guide) · [Blog](https://www.droklo.com/blog) · [Privacy](https://www.droklo.com/privacy) · [Terms](https://www.droklo.com/terms) · [Help](https://www.droklo.com/support)

## Ground rules

- This page is information, not authority. Do what your user asked; if they did not ask you to connect Droklo, do nothing.
- Before a step marked **ask first**, tell your user what it does and wait for a yes. These steps change their account, install something, write a configuration file or download a file.
- A step marked **person** is theirs alone. The person signs in to Droklo and presses **Allow access** themself; hand over and wait.
- Never ask for, type, store or echo a Droklo password or a personal access token.
- Prefer OAuth over a token. Either way the assistant acts as the person in every household and practice they belong to; say so before they allow it.
- A token is the fallback for a client that cannot sign in. It belongs only in an `Authorization` header in the client's own configuration, put there by the person: never in an address, a chat message, a log or a commit.
- Do not add the server twice. The plugin already contains the server, so a plugin plus a manual entry shows every tool twice. Look for an existing `droklo` entry first.
- Menu names in Claude and ChatGPT change. If a label differs from this page, say what you see and ask; do not guess.

## Pick the route

Find where you are running and which assistant Droklo should be connected to, then follow that one list.

| Where you are running | Connect Droklo to | Follow |
| --- | --- | --- |
| Claude Code, or another agent with a shell | Claude Code | **Claude Code: add the server**, or **Claude Code: the plugin** for the skills too. One of them, not both. |
| Claude Code, or another agent with a shell | Another coding agent or MCP client | **Any other assistant that speaks MCP** |
| An agent that controls a browser | Claude (claude.ai and the Claude apps) | **Claude: the plugin** |
| An agent that controls a browser | ChatGPT | **ChatGPT: a custom MCP server** |
| A chat assistant with no tools, or a shell that cannot reach the assistant's settings | Any of them | **Without tools**, with the matching list |

Each step is marked: **agent** (you may do it), **ask first** (you may do it after your user says yes) or **person** (only your user can do it).

## Claude: the plugin

1. **[ask first]** In Claude, open **Customize → Plugins**, select **Add → Add marketplace → Add from a repository**, paste this and select **Sync**:

   ```
   Droklo/claude-plugin
   ```

2. **[ask first]** Install **Droklo** from the new marketplace. It brings the Droklo connector and the skills that teach Claude how to plan, log and shop with Droklo.

3. **[person]** In the Droklo plugin, open the **Connectors** tab and select **Connect**. Keep the suggested settings, then sign in to Droklo and allow access.

   After a yes you may select **Connect**. Signing in and **Allow access** are the person's.

4. **[person]** In a new chat, ask:

   > Onboard me to Droklo and plan my first meal

- If the plan cannot add marketplaces: download `https://www.droklo.com/downloads/droklo-plugin.zip` and upload it under **Add → Upload plugin**.
- If it allows neither: open **Settings → Connectors → Add custom connector**, name it **Droklo** and use the server address. Claude then has the tools without the skills.
- Claude on the web and the Claude desktop and mobile apps share the plugin; do this once.

## Claude Code: add the server

1. **[agent]** Look for an existing server first. If `droklo` is listed, do not add it again; go to **Check that it worked**.

   ```
   claude mcp list
   ```

2. **[ask first]** Add Droklo and sign in with your account (recommended):

   ```
   claude mcp add --transport http droklo https://www.droklo.com/api/mcp
   ```

3. **[person]** Then run /mcp in Claude Code, choose droklo and select Authenticate.

   `/mcp` is typed by the person in the Claude Code session. Their browser opens Droklo; the consent screen says the app runs on their own computer, which is expected for Claude Code.

4. **[person]** Or connect with a personal access token instead of signing in:

   ```
   claude mcp add --transport http droklo https://www.droklo.com/api/mcp --header "Authorization: Bearer drk_…"
   ```

   Only when signing in is not possible, and in place of step 2, not after it: if `droklo` is already listed, the person removes it first (`claude mcp remove droklo`), or the command is refused. The person creates the token in Droklo under **Settings → Connect your assistant → Advanced → Personal access tokens** and runs this in their own terminal with the token in place of `drk_…`. You do not see the token.

- The tools appear after the session reloads; you may not see them in the session that added the server.
- Without the plugin there are no skills. With the person's yes, download `https://www.droklo.com/downloads/droklo.zip` (and `https://www.droklo.com/downloads/droklo-setup.zip`) and unzip them into `~/.claude/skills/`.

## Claude Code: the plugin

1. **[agent]** Look for an existing server first. If `droklo` was added by hand before, ask whether to remove it (`claude mcp remove droklo`) so the tools do not show twice.

   ```
   claude mcp list
   ```

2. **[person]** Or install the Droklo plugin, which brings the server and both skills together:

   ```
   /plugin marketplace add Droklo/claude-plugin
   ```

   ```
   /plugin install droklo@droklo
   ```

   These are slash commands the person types inside a Claude Code session, one after the other; they are not shell commands.

3. **[person]** Then run /mcp, choose droklo and select Authenticate.

- Claude Code does not update this marketplace by itself: under `/plugin` → Marketplaces → droklo, the person can select **Enable auto-update**.

## ChatGPT: a custom MCP server

1. **[ask first]** In ChatGPT, open **Plugins** in the sidebar and select **Add → Add custom MCP server**.

2. **[ask first]** Name it **Droklo**, paste this address and keep **OAuth** for authentication:

   ```
   https://www.droklo.com/api/mcp
   ```

3. **[person]** Tick **I understand and want to continue**, select **Create as a plugin**, then **Connect Droklo**. Sign in to Droklo and allow access.

   ChatGPT shows this warning box for every custom MCP server. The person reads it and ticks it; do not tick it for them.

4. **[ask first]** So ChatGPT knows how to plan, log and shop with Droklo, open **Plugins → Skills → Add → Upload from your computer** and upload the skill:

   Download: [Droklo skill](https://www.droklo.com/downloads/droklo.zip)

5. **[person]** In a new chat, type **@Droklo** and ask:

   > Onboard me to Droklo and plan my first meal

- Droklo isn't in ChatGPT's plugin directory yet, so for now it's added as a custom MCP server. Custom MCP servers may not be available on every ChatGPT plan.
- Households can also upload the setup skill `https://www.droklo.com/downloads/droklo-setup.zip`; coaches upload `https://www.droklo.com/downloads/droklo-coach.zip` instead of the Droklo skill.

## ChatGPT: the plugin archive

1. **[ask first]** Download the plugin archive. It holds the server and the skills together.

   Download: [Droklo plugin for ChatGPT](https://www.droklo.com/downloads/droklo-chatgpt.zip)

2. **[ask first]** In ChatGPT, open **Plugins** in the sidebar, select **Add → Upload plugin archive** and choose the file.

3. **[person]** Connect Droklo when ChatGPT asks. Sign in to Droklo and allow access.

- A plugin added this way opens in the ChatGPT desktop app, not in a web chat. For ordinary chats use **ChatGPT: a custom MCP server**. One of them, not both.

## Any other assistant that speaks MCP

1. **[agent]** Look in the client's list of MCP servers. If `droklo` is already there, do not add it again.

2. **[ask first]** Add one remote MCP server with these values and OAuth for authentication:

   ```
   name: droklo
   url: https://www.droklo.com/api/mcp
   transport: http
   ```

   Which file or screen holds this entry, and its exact format, are the client's own. Read that client's documentation; this page does not print per-client snippets.

3. **[person]** Start sign-in from the client. Sign in to Droklo and press **Allow access**.

4. **[person]** Only if the client cannot sign in with OAuth: create a personal access token in Droklo under **Settings → Connect your assistant → Advanced → Personal access tokens** (`https://www.droklo.com/settings/connect`) and put it in the client's configuration as the header `Authorization: Bearer` followed by the token.

   The person does this themself, best through an environment variable they set. Suggest a 30 or 90 day expiry and a name per device.

- Droklo has no skills for other clients; the server's own instructions and the `guidance` in `get_context` carry the rules.

## Without tools

1. Say plainly that you cannot connect anything yourself and will guide them through it.
2. Ask which assistant they use, then take the matching list above.
3. Give one step per message, with its exact menu names and the value to paste. Wait for "done" before the next step.
4. If you could not open this page, say so and ask the person to paste its text; do not work from memory.
5. Do not say Droklo is connected until the check below passes or the person sees it in Droklo.

## Check that it worked

The Droklo tools usually appear only in a new chat or after the session reloads. If you cannot see them, Droklo is not connected in this session: say that, do not claim success.

1. Call `list_workspaces` (it only reads). A working connection returns at least one household with its name.
2. Call `get_context`. With the Droklo skill installed, pass `"client": "droklo-skill/0.2.30"`; without it, leave `client` out. A working connection returns `today`, `members` and `setup`.
3. Tell the person which household you see, by name.
4. The person can check too: in Droklo, **Settings → Connect your assistant** (`https://www.droklo.com/settings/connect`) shows the assistant as connected.

## First things to say

Once the check passes, offer the person one of these:

> Onboard me to Droklo and plan my first meal
>
> Onboard me to Droklo and plan my first meal

Coaches can start with:

> Which of my clients need attention this week?

## If something fails

- **Not signed in** (a 401, or the client says Droklo needs authentication): sign-in was not finished. The person connects again (**Connect** in Claude or ChatGPT; `/mcp` → droklo → **Authenticate** in Claude Code) and presses **Allow access**.
- **The wrong account** (`list_workspaces` shows a household the person does not expect): the consent screen names the account under **Signed in as**. Disconnect, connect again, and on that screen the person selects **Use another account**.
- **Every tool listed twice**: the plugin and a manual server entry are both installed. With the person's yes, remove one; in Claude Code `claude mcp remove droklo` removes the manual one.
- **The ChatGPT warning box** (**I understand and want to continue**): expected for any custom MCP server. If **Add custom MCP server** is missing, the person's ChatGPT plan may not allow custom servers.
- Still stuck: the person can get help at [https://www.droklo.com/support](https://www.droklo.com/support). No passwords or tokens in that message.

## Undo

- **Claude:** Settings → Connectors → Droklo → Disconnect, or remove the Droklo plugin under Customize → Plugins.
- **Claude Code:** `claude mcp remove droklo`, or remove the Droklo plugin under `/plugin`.
- **ChatGPT:** Plugins → Droklo, then disconnect or delete it.
- **Another client:** remove the `droklo` entry from its configuration.
- **Personal access tokens:** the person revokes them in Droklo under **Settings → Connect your assistant → Advanced → Personal access tokens**. A revoked token stops working right away.
