Based on a GetMCP customer's own setup

Run every client project in Kitchen.co from Claude

Connect the Kitchen.co API to your own MCP server once. Then ask Claude what's overdue across every client board, who you're waiting on, and have it post the update in the right conversation.

Who it's for
Agencies and freelancers
Apps
Kitchen.co
Works in
Claude, ChatGPT, Manus
Built with
Ready-made server from the Kitchen.co API

A ready-made GetMCP server: import the file, add your own key and ask. How to import it

Claudeyour-site.com/mcp

Which client projects have overdue tasks this week, and who is waiting on us?

Tool call: list_boards state=active

Tool call: list_board_tasks status=open due_at=<=1762473600

Three boards have overdue tasks:

  • Northwind rebrand: 2 tasks, waiting on your copy review
  • Bluebird Bakery site: waiting on the client's photos
  • Harbor Dental ads: 1 task, assigned to Sam

Want me to post a reminder in the Bluebird conversation?

Yes, keep it friendly.

Tool call: post_conversation_message conversation_id=bluebird

What changes

The work is the same. Where you do it moves from a row of tabs to one conversation.

Before

  • Open each client's workspace to see where it stands
  • Copy tasks into a status note by hand
  • Chase people one message at a time
  • Find out a deadline slipped when the client asks
  • Rebuild the same Monday summary every week

After

  • One question covers every active project
  • Claude writes the status note from the real tasks
  • Reminders go out in the right conversation when you say so
  • Ask what's slipping before the client notices
  • The Monday summary is one question, written from live data

Things you can ask

Copy one into Claude once the server is connected.

  • What's overdue across all my client projects this week?
  • Which projects are waiting on the client, and since when?
  • Write a status note for Northwind from its open tasks.
  • Post a friendly reminder about the photos in the Bluebird conversation.
  • Add a task for Sam: send the Harbor Dental ad proofs by Friday.
  • Which client have we not updated in two weeks?
  • Move the Northwind review to next Tuesday and let the team know.
  • Sum up everything that happened on Harbor Dental this week.

Set it up

Import the ready-made server, or describe it and let Claude build it from the Kitchen.co API docs. Either way, no code. You need GetMCP and a Kitchen.co API token from a plan that includes the API.

Skip the setup: import the ready-made server

  1. Download the file.
  2. In GetMCP, open Servers, click Import and choose the file.
  3. Add your Kitchen.co API token and workspace name: keys go in the server's Authentication tab, anything else in its connection variables.
  4. Switch on the Gateway and connect Claude to it. To connect to the server's own address instead, create an access key for it first.

Or build it yourself:

  1. Connect Claude to GetMCP

    Add GetMCP's own address to Claude once and sign in. Claude can now build servers for you.

  2. Ask Claude to build the Kitchen.co server

    Share the Kitchen.co API docs and say what you want to do. Claude creates the server and its tools.

  3. Add your API key and test each tool

    New tools start as drafts. Test one, see a real response, then switch it on.

  4. Turn on the Gateway and add it to Claude

    One address for every server you have. Claude signs in with your own login.

What you ask Claude

Using GetMCP, create a server called Client work for Kitchen.co. I want to list boards, their lists and tasks, add and update tasks, comment on tasks, and read and post conversation messages. Here are the API docs: https://developer.kitchen.co/

Created Client work with 9 tools. They're saved as drafts. Add your Kitchen.co API token and your workspace name in GetMCP, then test them.

Claude creating a server and its tools in GetMCP from a chat

More on GetMCP: how Claude builds a server from an app's API and GetMCP for agencies.

The tools on this server

Nine tools from the Kitchen.co API cover the daily questions. Clients can see conversation messages, so Claude shows you the text before it posts.

ToolWhat it doesChanges data
list_boards Lists boards, usually one per client project No
list_board_lists Lists the columns on a board, which a new task needs No
list_board_tasks Lists a board's tasks, filtered by status, title or due date No
create_task Adds a task to a list on a board Yes
update_task Changes a task's title, assignee, dates or list Yes
add_task_comment Comments on a task Yes
list_conversations Lists conversations with clients and the team No
list_conversation_messages Reads the messages in a conversation No
post_conversation_message Posts a message in a conversation, now or scheduled Yes

Questions about this setup

Do I need to write code?

No. You tell Claude what you want and share the Kitchen.co API docs, and Claude builds the tools in GetMCP. You only add your Kitchen.co API key.

Which Kitchen.co plan includes the API?

The API comes with Kitchen.co's Lifetime and Agency White Label plans. The workspace owner or an admin creates the token in Kitchen.co's settings.

Does Claude see my API key?

No. The key stays in GetMCP on your own server. Claude only sees the tools and what they return.

Can I add more Kitchen.co actions later?

Yes. Ask Claude for a tool for any other request in the Kitchen.co API docs, and it goes on the same server.

What is my workspace name?

The first part of your Kitchen.co address. If you sign in at northwind.kitchen.co, it's northwind. Enter it as the server's workspace connection variable.

Build this server tonight. Ask your first question tomorrow morning.