Install and connect

Use the CLI to register Meetily as an MCP server in your client's config, then restart the client to pick up the new server.

meetily-pro mcp install [--config <path>] [--name <name>] [--write]

By default this targets Claude Desktop's config and registers the server under the name meetily. It merges into the config's mcpServers map without touching any servers you already have there, and writes the file atomically so a crash mid-write can't corrupt your existing config.

What gets written

Running the command with no flags:

meetily-pro mcp install

mints a scoped, least-privilege token for this client, stores it in a file with 0600 permissions, and adds an entry like this to your client's config:

{
  "mcpServers": {
    "meetily": {
      "command": "meetily-pro",
      "args": ["mcp", "--token-file", "/path/to/token"]
    }
  }
}

The token is scoped to Read and Record by default. Pass --write to also grant Write:

meetily-pro mcp install --write

Install never grants Delete or Admin scope. If you need Delete, enable the assistant from the in-app Integrations panel instead, which can grant it.

How the token is minted

Install calls a loopback-only endpoint, POST /v1/mcp/client-token, which is Admin-scoped and authorized transiently by your local loopback token. That endpoint mints a scoped, per-client token and returns it once. Install writes it to disk with 0600 permissions and never falls back to an unscoped token: if the mint fails, the install fails.

Registering a second entry

Use --name to register another server entry under a different key, for example a write-enabled one alongside the default read-and-record one:

meetily-pro mcp install --name meetily-write --write

This leaves the existing meetily entry untouched and adds a second meetily-write entry next to it.

Verify the connection

meetily-pro mcp doctor

doctor probes the gateway with GET /v1/whoami and reports:

• whether the gateway is reachable
• your Pro license tier
• the scopes your token carries

This tells apart a gateway that is reachable but denies you, which is a token or license problem, from a gateway that isn't running at all. Run it any time a tool call is failing and you're not sure why.