garmonia-crm-mcp

MCP server for testing the «Гармония отеля» CRM through its internal API. It logs in with a password (session cookie) and provides tools for orders, clients, brands, calendar, and universal access to all the rest of CRUD.

Quick installation (one command, no cloning)

You only need Node 18+. There's no need to install or clone the repository — npx will run the server directly from GitHub.

1. Create a local credentials file, for example ~/garmonia-crm.json:

   {
     "baseUrl": "https://адрес-crm",
     "login": "твой-логин",
     "password": "твой-пароль"
   }

2. Add the MCP with one command (substitute your path to the file):

   claude mcp add garmonia-crm \
     -e CRM_CONFIG="$HOME/garmonia-crm.json" \
     -- npx -y github:AlekseiKastsiuk/garmonia-crm-mcp

3. Restart Claude Code.

The credentials live only in your local file and are sent nowhere — npx only pulls the server code from GitHub.

Related MCP server: MCP CRUD Tools

Installing from source (alternative)

git clone https://github.com/AlekseiKastsiuk/garmonia-crm-mcp
cd garmonia-crm-mcp
npm install
cp crm-config.example.json crm-config.json
# открой crm-config.json и впиши baseUrl, логин и пароль своей CRM

crm-config.json contains the CRM address and login/password; don't commit it to git (it's already in .gitignore).

Connecting to Claude Code

Add the server in ~/.claude.json (or via claude mcp add):

{
  "mcpServers": {
    "garmonia-crm": {
      "command": "node",
      "args": ["/полный/путь/к/garmonia-crm-mcp/server.mjs"]
    }
  }
}

If the config is not next to the server, specify the path in env:

"env": { "CRM_CONFIG": "/полный/путь/к/crm-config.json" }

After editing, restart Claude Code.

Tools

Security

• The password and CRM address are kept in crm-config.json, which is in .gitignore — it never gets into the repository.

• crm-config.example.json contains only placeholders, no real data.

• Before the first push, check: git ls-files should not contain crm-config.json, and git grep -i password should only show the field name in the code.

Notes

• Orders are created via the public endpoint POST /api/form-lead — no authorization needed.

• Deleting an order is not REST but a Next.js server action (the same “Delete” button on the closed tab). crm_order_delete invokes it itself. The action id is tied to the frontend build; if deletion breaks after a CRM deploy, update bulkDeleteActionId in crm-config.json (search the JS bundle for bulkDelete).

• Products/categories provide listings via server-side rendering rather than a GET API — use crm_request (POST/PATCH/DELETE) to create/edit/delete them.