LABSCO SUMMARY

It holds no session, so one install can address several Chef organisations.

Authentication travels with each call rather than sitting in the config, which is what makes it multi-tenant. The same connection can address one organisation on this call and a different one on the next, with nothing cached in between.

What it is

A server over the Chef Infra Server API with one tool per endpoint rather than a generic wrapper. It holds no session: every tenant-facing call carries its own authentication.

What you get

Nodes, roles and environments: chef_create_node, chef_delete_node, chef_create_role, chef_delete_role, chef_create_environment and chef_delete_environment
Clients and their keys: chef_create_client, chef_get_client, chef_delete_client, chef_create_client_key, chef_get_client_key and chef_delete_client_key
Cookbooks: chef_get_cookbook, chef_get_cookbook_version, chef_delete_cookbook_version, chef_get_cookbook_artifact, chef_get_cookbook_artifact_version and chef_delete_cookbook_artifact_version
Data bags: chef_create_data_bag, chef_create_data_bag_item, chef_delete_data_bag and chef_delete_data_bag_item
Uploads: chef_create_sandbox and chef_commit_sandbox
Organisations and membership: chef_create_organization_global, chef_delete_organization_global, chef_create_association_request, chef_delete_association_request, chef_associate_org_user and chef_disassociate_org_user
Users, groups and containers: chef_create_user_global, chef_delete_user_global, chef_create_user_key_global, chef_delete_user_key_global, chef_authenticate_user, chef_create_group, chef_delete_group, chef_create_container and chef_delete_container

Requirements

A Chef Infra Server you can reach, and credentials passed on each call: a user id and RSA private key for Chef signature authentication, or a username and password for the endpoints that take basic auth. Connecting through the hosted MewCP gateway also takes a MewCP account and its API key (dashboard → Developer); running it from source does not.

Setup effort

Add the hosted endpoint plus a key — paste it into your client, then supply credentials

See installation options

USE CASES

01

Taking stock of an organisation you inherited

Read the clients, containers and cookbooks that exist before changing anything, using credentials scoped to that organisation alone.

chef_get_clientchef_get_containerchef_get_cookbook

02

Onboarding somebody onto an organisation

Create the user, raise the association request and complete the membership in one pass.

chef_create_user_globalchef_create_association_requestchef_associate_org_user

03

Standing up a new environment

Create the environment, the roles that belong to it, and the nodes underneath.

chef_create_environmentchef_create_rolechef_create_node

04

Rotating a client's key

Issue the new key, confirm it is registered, then remove the old one — in that order, so nothing loses access mid-way.

chef_create_client_keychef_get_client_keychef_delete_client_key

05

Pulling back a cookbook version that should not have shipped

Read the version to confirm what it contains, then delete it.

chef_get_cookbook_versionchef_delete_cookbook_version

102 tools

Listed in project docs. Your client may show a different list.

health_check

chef_authenticate_user

chef_get_license

chef_list_organizations_global

chef_create_organization_global

chef_get_organization_global

chef_update_organization_global

chef_delete_organization_global

chef_get_stats

chef_get_status

chef_list_users_global

chef_create_user_global

chef_get_user_global

chef_update_user_global

chef_delete_user_global

BEFORE YOU INSTALL

What to know first

Tools you get

102 tools named in the project's documentation.

Requires

A MewCP account and API key (MEWCP_KEY, dashboard → Developer); the Hobby plan is free for 20K actions a month

INSTALLATION

Connect your client

Server setup

ENDPOINT URL

https://gateway.mewcp.com/personal/mcp

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

VS Code

VS CODE · JSON

{
  "servers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MEWCP_KEY>"
      }
    }
  }
}

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "mewcp": {
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MEWCP_KEY>"
      }
    }
  }
}

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization: Bearer <YOUR_MEWCP_KEY>"
      ]
    }
  }
}

Any MCP client — From Source

Clone the repository and install its dependencies

ANY MCP CLIENT — FROM SOURCE · TERMINAL

git clone https://github.com/AStheTECH/mewcp-chef-server
cd mewcp-chef-server
pip install -r requirements.txt

Add this to your client

<YOUR_PATH_TO_MEWCP_CHEF_SERVER> is the path of your clone. No MewCP key is needed this way; Chef credentials are passed on each tool call.

ANY MCP CLIENT — FROM SOURCE · JSON

{
  "mcpServers": {
    "chef-server": {
      "command": "python",
      "args": [
        "<YOUR_PATH_TO_MEWCP_CHEF_SERVER>/server.py"
      ]
    }
  }
}

MewCP Chef Server MCP