DiSH

You can run a DiSH MCP Server to manage room availability, bookings, and cancellations for your DiSH locations. This MCP Server exposes tools that assistants can use to check availability, create bookings, cancel or reschedule, and coordinate with your calendar, making it easy to automate and streamline meeting planning.

How to use

To use the Dish MCP Server, run it locally and connect a compatible MCP client such as Cursor or Claude Desktop. You will be able to search for available rooms, create bookings on your behalf, cancel or reschedule existing reservations, and pair with calendar tools to keep your availability in sync. Use natural language prompts like asking to book meeting rooms for a set of meetings, rescheduling a session when both you and a coworker are free, or reserving spaces for customer demos over a period. Your client will send requests to the server, and the server will perform the actions against your DiSH account.

How to install

Prerequisites you need to prepare before starting the server are Python 3.10 or newer and the uv dependency management tool.

Step 1: Install the uv tool (if you don’t already have it) and synchronize dependencies.

Step 2: Start the MCP server using the provided runtime command.

Step 3: Configure a client with the credentials you provide (cookie, team ID, and member ID) to enable authenticated access to DiSH.

Step 4: Connect a client (Cursor or Claude Desktop) to the running MCP server and begin issuing requests to search availability, create bookings, or cancel/reschedule bookings.

Additional setup and usage notes

Automatic credential retrieval is recommended for ease of setup. You can run a credential script, which will open a browser window, log you in to DiSH, and save the connect.sid cookie, team ID, and member ID to an .env file for use by the MCP server.

# Install Playwright browser (first time only)
uv run playwright install chromium

# Run the credential retrieval script
uv run src/get_credentials.py

# The script saves credentials to your .env file for use by the server.

Configuration and runtime

The MCP server requires three environment variables to connect to your DiSH account.

Environment variables to set in your environment or your client configuration include:

• DISH_COOKIE — your DiSH connect.sid session cookie
• TEAM_ID — your DiSH team ID
• MEMBER_ID — your DiSH member ID

Run the MCP server

uv run fastmcp run src/mcp_server.py

Configure your MCP client

Configure Cursor or Claude Desktop to connect to the running MCP server using the environment variables you set. The examples below show how to wire the server into each client.

"Dish MCP": {
  "command": "<PATH_TO_VENV>/bin/fastmcp",
  "args": ["run", "<PATH_TO_REPO>/src/mcp_server.py"],
  "cwd": "<PATH_TO_REPO>",
  "env": {
    "DISH_COOKIE": "<connect.sid=...>",
    "TEAM_ID": "<YOUR_TEAM_ID>",
    "MEMBER_ID": "<YOUR_MEMBER_ID>"
  },
  "transport": "stdio"
}

Security and credentials safety

Keep credentials secret. Do not commit cookies, team IDs, member IDs, or .env files to source control. If authentication stops working or credentials are exposed, regenerate the cookie.

Troubleshooting

If authentication fails, re-run the credentials retrieval process to obtain fresh values, and restart the MCP server with the updated env variables.

Available tools

search_availability

Search room availability across your DiSH locations.

create_booking

Create bookings on your behalf with the MCP server.

cancel_booking

Cancel or reschedule existing bookings via MCP client requests.

calendar_pairing

Pair with calendar tools to coordinate bookings with calendar availability.