kitchen-co-mcp
Provides tools for interacting with the Kitchen.co API, including managing tasks, boards, conversations, files, invoices, clients, members, and documents, plus a low-level request tool.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kitchen-co-mcpshow tasks on the client onboarding board"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kitchen.co MCP (Unofficial)
Unofficial community extension by Dimy Osman.
Not affiliated with Kitchen.co. This is not an official Kitchen.co product. It is not endorsed, sponsored, or approved by Kitchen.co, 2create.io, or their affiliates. “Kitchen” / “Kitchen.co” identify the third-party API only — no partnership or rights are implied.
Connects IDE to your Kitchen.co workspace so the agent can read and update that work from the editor.
Uses the public Kitchen API and MCP. You supply your own workspace URL and API token. This extension does not provide Kitchen accounts or Kitchen.co support.
Install
Recommended — Extensions marketplace
Open Extensions in Cursor (or another Open VSX–compatible editor).
Search for
Kitchen.co MCP (Unofficial)ordimy-osman.kitchen-co-mcp.Click Install.
Listings:
After install
Acknowledge the one-time unofficial notice (first run only).
Command Palette → Kitchen.co MCP: Add Profile.
Enter a profile name, your workspace URL (or slug), and API token from Kitchen → Settings → Developer → API Token.
Optional: List Profiles to confirm the profile is ready (
durable mcp.json: yes).
Tokens stay on your machine (OS keychain + encrypted vault). They are never written into mcp.json as plaintext.
Alternative — Install from VSIX
If you prefer a local package: download a release VSIX from GitHub, or build one (see Development), then Extensions → ⋯ → Install from VSIX….
Related MCP server: ClickUp Multi-Workspace MCP Server
What you can do
Once a profile is connected, agents can use the public Kitchen API for that workspace.
Cursor only loads hot-path named tools (schemas). Read MCP resource kitchen://api-index for the compact public-path map, then kitchen_request. Resource kitchen://capabilities (or tool kitchen_capabilities) is the full catalog — only if the index is missing or a path fails. Both resources are shipped in this extension, not fetched live from Kitchen.
Hot-path named tools (Bearer /api only):
Folders — list, get, children, create (including clone from a template)
Boards / lists / labels — list boards, list columns, list labels, add a label to a task
Tasks — list, get, create, update, move
Members / clients — list members, list/get clients
Invoices — list, get, create
Conversations / messages — list/get conversation, list/get/create message
Meta —
kitchen_whoami,kitchen_request,kitchen_capabilities
Other documented public paths (archive, memberships, companies, webhooks, files, docs, embeds, milestones, …) stay available via kitchen_request using kitchen://api-index. Query arrays serialize as key[]=value.
Not on the public API (so not in MCP): client billing-profile CRUD, company user attach, invoice finalize/send, quotes, proposals. Do not scrape cookies. Deprecated Cards / legacy Attachments are skipped on purpose.
Permissions: visibility is private, internal, or shared. Internal can take a default team role. Shared includes clients.
See SECURITY.md for how credentials are stored and what protections apply.
Commands
Command | Purpose |
About / Disclaimer | Unofficial status and legal notice |
Add / Edit / Remove Profile | Manage workspace URL + API token pairs |
List Profiles | Status (key stored, durable MCP, etc.) |
Re-register MCP Servers | Re-sync workspaces into |
Test Connection | Quick API check |
Show Output Log | Diagnostics (success is silent on startup) |
Startup success is silent; you only get a toast if something fails. Setup help appears once on first install.
Disclaimer & legal
Unofficial / third-party — independent use of Kitchen’s public API.
No rights from Kitchen.co — no trademark license, partnership, or official support.
Support — use GitHub Issues only; do not contact Kitchen.co about this extension.
Your credentials — you are responsible for tokens and for actions agents take with them.
AS IS — MIT License; no warranties. Kitchen may change their API at any time.
See NOTICE.
Development
For contributors building from source:
npm install
npm run compile
npm run lint
npm run audit
npm run package # writes vsix/kitchen-co-mcp-*.vsixPublishing notes for maintainers: docs/PUBLISH.md.
Buy me coffee and AI tokens
If this extension helps, you can buy me coffee and AI tokens.
License
MIT © Dimy Osman — see LICENSE.
Kitchen.co and related marks remain the property of their respective owners.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Shared project context for AI agents and teams: docs, tasks, and messages that stay current.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
One profile — skills, credentials, and memory — synced to every agent tool via one MCP URL.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEmpowers AI assistants with real-world capabilities including note management, Gmail integration, Google Calendar and Tasks management, and Git repository operations through the Model Context Protocol.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with tasks, spaces, lists, and folders across multiple ClickUp workspaces via the Model Context Protocol.601MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage and interact with Kasm Workspaces containerized desktop infrastructure, providing tools for session management, command execution, file operations, and user management via the Model Context Protocol.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, update, list, and delete tasks on a Kanban board via the Model Context Protocol, supporting multi-project management and real-time collaboration.98MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dimy-osman/kitchen-co-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server