Skip to main content
Glama

Kitchen.co MCP

Kitchen.co MCP by Dimy Osman — project code KTCH-MCP.

Cursor / VS Code extension that connects AI agents to the Kitchen.co API via the Model Context Protocol.

  • Multiple workspace profiles (URL + API token pairs)

  • API tokens in OS keychain (SecretStorage) plus a local envFile under extension globalStorage

  • Durable entries merged into ~/.cursor/mcp.json (survives window reload) — keys never written plaintext into that file

  • Optional session registration via Cursor’s vscode.cursor.mcp.registerServer API

Security

Stored

Where

Profile name + base URL

Extension globalState

API tokens

SecretStorage (OS keychain) + globalStorage/env/kitchen-*.env (envFile for Cursor)

~/.cursor/mcp.json

Command/args/base URL only — no API key plaintext

Git

Never.env, *.env, *.vsix, build outputs gitignored

Do not commit real API keys. Create tokens in Kitchen → Settings → Developer → API Token; enter them only via Add Profile (password input).

Related MCP server: ClickUp Multi-Workspace MCP Server

Install (VSIX)

  1. Build: npm install && npm run package

  2. Cursor: Extensions → … → Install from VSIX…kitchen-co-mcp-0.1.1.vsix

  3. Command Palette → Kitchen.co MCP: Add Profile

  4. Enter name, workspace URL/slug, and API token

  5. Confirm under Cursor Settings → MCP and via List Profiles (durable mcp.json: yes)

Reload behavior (fixed in 0.1.1)

v0.1.0 unregistered MCP servers in deactivate(), so Developer: Reload Window removed Kitchen from MCP.
v0.1.1+ does not unregister on deactivate, syncs durable mcp.json on activate, retries the Cursor MCP API, and logs to Kitchen.co MCP: Show Output Log.

Commands

  • Add / Edit / Remove Profile

  • List Profiles — key status, durable mcp.json yes/no, dynamic register yes/no

  • Re-register MCP Servers — sync durable + dynamic

  • Test Connection

  • Show Output Log

Settings

  • kitchenMcp.autoRegister (default true) — sync on startup

  • kitchenMcp.persistToUserMcpJson (default true) — merge into ~/.cursor/mcp.json

Standalone MCP (manual)

{
  "mcpServers": {
    "kitchen-acme": {
      "command": "node",
      "args": ["/absolute/path/to/kitchen-co-mcp/mcp/dist/index.js"],
      "env": {
        "KITCHEN_BASE_URL": "https://acme.kitchen.co",
        "KITCHEN_API_KEY": "${env:KITCHEN_ACME_KEY}"
      }
    }
  }
}

Or use envFile pointing at a local file that defines KITCHEN_API_KEY (what the extension writes under globalStorage).

MCP tools (selected)

Tool

Purpose

kitchen_whoami

Auth probe (no key in response)

kitchen_list_tasks / kitchen_get_task

Tasks

kitchen_create_task / kitchen_update_task

Task writes

kitchen_list_boards / kitchen_get_board

Boards

kitchen_list_conversations / messages

Conversations

kitchen_list_files / folders / invoices / clients / members / docs

Other resources

kitchen_request

Low-level GET/POST/… under /api

API reference: https://developer.kitchen.co/

Develop

npm install
npm run compile
npm run package

Requirements: Node 20+, Cursor (recommended).

License

MIT © Dimy Osman

A
license - permissive license
-
quality - not tested
C
maintenance

Maintenance

Maintainers
<1hResponse time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

  • The personal context layer for AI: your profile and files, read by any MCP client over OAuth.

  • Shared, permission-aware company context for AI agents, with provenance, approvals and audit.

View all MCP Connectors

Latest Blog Posts

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