New · the agent door · MCP

Your kitchen.
Your AI.

Connect the assistant you already use, Claude, ChatGPT or any tool that speaks the open MCP standard, to your ChefAdmin data. It reads your recipes, inventory, brands, costs and reports and answers from your numbers. Read-only. Under your own sign-in. One click to disconnect.

Connection guide → Open ChefAdmin →

Read-only by design Open standard Your account, your revoke A few minutes to connect

Connection guide

Three steps. Then ask.

Included with the Kitchen plan at no extra charge. You need your ChefAdmin sign-in and an assistant that supports MCP connections: Claude, ChatGPT or any MCP client.

01 · IN YOUR ASSISTANT

Add ChefAdmin as a connector.

Open your assistant's connector settings, choose to add a custom connector, name it ChefAdmin and paste the address below. No key, no code.

02 · SIGN IN

Approve it under your account.

Your assistant opens a ChefAdmin sign-in screen. Enter your ChefAdmin email and password and continue. The connection is tied to your own sign-in, not to a shared login, and it can only read.

03 · ASK

Ask about your kitchen.

"What did my top five dishes cost this week?" The assistant reads your ChefAdmin data and answers from your numbers, live, not from an export.

The address to paste

https://admin.chefadmin.com/mcp

Open standard (MCP over HTTPS), sign-in by OAuth. Your password is never given to the assistant; it goes to ChefAdmin, which hands the assistant a read-only token you can withdraw at any time.

Claude

Settings, then Connectors, then Add custom connector. Name: ChefAdmin. URL: the address above. Add, then Connect and sign in. In a chat, make sure ChefAdmin is switched on under the tools menu, then ask.

ChatGPT

Settings, then Connectors, then create or add a custom connector with the address above and sign in when asked. Custom connectors depend on your ChatGPT plan and settings; if the option is not there, your plan does not include it yet.

Any other MCP client

Add a remote MCP server with the address above. The client discovers the sign-in itself (OAuth with dynamic registration) and opens the ChefAdmin screen. Nothing to configure by hand.

To disconnect, remove ChefAdmin from your assistant's connectors. Access ends there and then. To connect a second assistant, repeat the three steps; each connection is its own, under your sign-in.

What it can read

Read what is yours. Touch nothing.

The door is read-only by design. Your assistant can look at everything below. It cannot change any of it.

Recipes and sub-recipes costed, versionedread

Inventory on hand, par, below parread

Brands and locationsread

Costs and margins food cost, theoretical against actualread

Reportsread

Change a recipe, move stock, raise or touch a purchase ordernever

It cannot write. Nothing your assistant does through the door changes a number in ChefAdmin. The token it holds is read-only, issued under your sign-in, and it dies the moment you remove the connector.

In practice

Questions it answers.

Worked examples of the kind of question the door is built for. The answers come from your data, not a guess and not last month's export.

"What did my top five dishes cost this week?"Reads your live recipe costs and answers per dish.

"Which brand had the biggest variance between theoretical and actual?"Reads the variance report, brand by brand.

"What's below par across the group right now?"Reads inventory at every location.

"Which ingredients went up in price this month?"Reads supplier prices against the recipe costs that depend on them.

"Draft me a Monday note on where food cost moved and why."Reads the week's reports and writes the note in your assistant; nothing is written back.

The standard

No lock-in. By design.

MCP is the open protocol the major assistants use to reach outside tools. ChefAdmin speaks it as a standard, not through a private integration. The assistant you use next year connects the same way as the one you use today, and a connection never dies because a partnership did.

Every platform has a copilot now, and every copilot reads your data inside its own walls. If the data is yours, any tool you choose should be able to read it. That is the whole point of the door.

Questions

Before you connect.

If yours is not here, write to info@godark.ai.

Can my assistant change anything in ChefAdmin?

No. The door is read-only. It cannot create or edit a recipe, move stock, raise a purchase order or change a setting. Writing stays with people, in ChefAdmin.

Who can see my data through the door?

Only an assistant you have signed in and approved yourself. The connection is yours; it does not belong to ChefAdmin or to the assistant's maker, and it ends the moment you remove the connector from your assistant.

Which assistants work?

Any that supports MCP connections: Claude, ChatGPT and other MCP clients. If yours supports adding a connector or tool by URL, it should work. If you are not sure, ask us.

Is it included in my plan?

Yes, with the Kitchen plan, at no extra charge. If you are on Build and want the door, write to info@godark.ai.

Does the assistant get my password?

No. Sign-in happens on a ChefAdmin screen, not inside the assistant. ChefAdmin then gives the assistant a read-only token for your account. That is the standard OAuth pattern, the same one your calendar and email connectors use.

Is the data live?

Yes. The assistant reads what ChefAdmin holds at the moment you ask, the same data your team sees on screen.

Can my own software use this instead of an assistant?

Yes. The same engine is addressable through an open API as well as MCP. Partners and integrations are handled by Godark; write to info@godark.ai.

Your kitchen.Your AI.