One-liner

Run this inside any git repository to configure it for Ticket House and start the local workstation:

curl https://your-ticket-house-server.com/bin/setup.js | node

What happens step by step

  1. curl fetches a setup script from the server’s /bin/setup.js endpoint. The server bakes its own URL, the ticket-house package repo, and the list of available projects directly into the script at serve-time. No config files are needed on your side.

  2. Finds the git repo root using git rev-parse --show-toplevel. If you’re not inside a git repository the script exits with an error.

  3. Project selection — if the server has only one project, it’s auto-selected. If there are multiple projects:
    • It first tries to match the git repo’s directory name to a project slug (e.g. if you’re in ~/code/my-app and there’s a project with slug my-app, it picks that).
    • If no match is found, an interactive prompt lists the available projects and asks you to pick one by number.
    • The script also tries to fetch the project list from the server’s API (GET /api/projects) using a saved session cookie at ~/.ticket-house/session, so authenticated users see only the projects they have access to. If not authenticated it falls back to the list baked into the script.

  4. Creates .ticket-house.json in the repo root (if it doesn’t already exist) with a remote field pointing to the server and project:

    {
  "remote": "https://your-server.com/projects/my-app"
}

  5. Installs ticket-house globally if it isn’t already (ticket-house --version). If not found it runs npm install -g from the git repo URL configured on the server (requires SSH access to the package repo).

  6. Starts the workstation by running ticket-house in the repo, which launches local workstation mode and connects to the remote server.

Pre-selecting a project

If you already know the project slug you can skip the interactive prompt by passing it as a query parameter:

curl 'https://your-server.com/bin/setup.js?project=my-app' | node

What you end up with

After running the one-liner you’ll have:

  • .ticket-house.json in the repo root, connecting it to the remote server.
  • ticket-house installed globally (if it wasn’t already).
  • A running local workstation with the MCP server, ready for AI agents to connect to.

Requirements

  • Node.js installed
  • Inside a git repository
  • SSH access to the ticket-house package repo (for first-time install)