DiSH MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DiSH MCP Server Find a room for a 1-hour meeting tomorrow at 2 PM."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DiSH MCP Server
A Model Context Protocol (MCP) server for the DiSH room booking site. It exposes tools to check availability, book rooms, and cancel bookings so assistants like Cursor or Claude can manage your reservations.
What it can do
Search room availability across your DiSH locations
Create bookings on your behalf
Cancel or reschedule existing bookings
Pair with calendar tools (e.g., Google Calendar MCP) to coordinate bookings with your calendar availability.
Example prompts:
"Book meeting rooms for all my standups this week."
"Reschedule my 1-1 with John to tomorrow afternoon when we’re both free and a room is open."
"Book a meeting room for all my customer demos for the next 2 months."
Related MCP server: nexudus-mcp
Requirements
Python 3.10+
uvfor dependency management
Setup
uv syncConfiguration
Required:
TEAM_ID— your DiSH team IDMEMBER_ID— your DiSH member ID
Authentication:
DISH_COOKIE— your DiSHconnect.sidsession cookieDISH_EMAIL— optional, enables non-interactive login when the cookie is missing or expiredDISH_PASSWORD— optional, enables non-interactive login when the cookie is missing or expired
Optional transport configuration (for HTTP mode):
MCP_TRANSPORT—stdio(default) orhttpMCP_PORT— port for HTTP transport (default:8000)MCP_HOST— host for HTTP transport (default:127.0.0.1)
Non-interactive cookie refresh
If you want Claude to keep working when connect.sid expires, put these values in .env:
TEAM_ID=<YOUR_TEAM_ID>
MEMBER_ID=<YOUR_MEMBER_ID>
DISH_EMAIL=you@example.com
DISH_PASSWORD=<YOUR_PASSWORD>With that setup:
The MCP will create
DISH_COOKIEautomatically if it is missing.If the API returns
401or403, the MCP will log in again headlessly, updateDISH_COOKIEin.env, and retry the request once.TEAM_IDandMEMBER_IDstay stable in.env; only the session cookie rotates.
This only works if your DiSH account supports direct email/password login. If your login goes through Google, Microsoft, or another SSO flow, there is no silent refresh path in this repo and you will need the browser-based flow below.
Automatic credential retrieval (manual browser flow)
The easiest way to get your credentials is to use the included script:
# Install Playwright browser (first time only)
uv run playwright install chromium
# Run the credential retrieval script
uv run src/get_credentials.pyThis will:
Open a browser window for you to log in to DiSH
Automatically detect when you've reached the dashboard
Capture your cookie, team ID, and member ID
Save them to your
.envfile
Manual credential retrieval
If the automatic method doesn't work, you can retrieve credentials manually:
Getting your connect.sid cookie
Log in to DiSH in your browser.
Open Developer Tools (F12 / Cmd+Option+I).
In Application/Storage > Cookies, select the DiSH domain.
Copy the
connect.sidvalue (looks likes%3A...).In your
.envfile, setDISH_COOKIEtoconnect.sid=<value>.
Getting your team and member IDs
Log in to DiSH in your browser.
Open Developer Tools (F12 / Cmd+Option+I).
In the Network tab, find a request to
occurrences(orbooking-policy).In the request URL or payload, look for the
teamandmembervalues.In your
.envfile, setTEAM_IDandMEMBER_IDto the respective values.
Keep this secret. Do not commit cookies, team IDs, member IDs, or .env files to source control. Regenerate the cookie if it stops working or was ever exposed.
Run the MCP server
stdio transport (default)
For use with Cursor or Claude Desktop:
uv run fastmcp run src/mcp_server.pyHTTP transport
For remote access or web-based clients:
# Default: http://127.0.0.1:8000
uv run python src/mcp_server.py --transport http
# Custom port and host
uv run python src/mcp_server.py --transport http --port 3000 --host 0.0.0.0Or using environment variables:
MCP_TRANSPORT=http MCP_PORT=8000 uv run python src/mcp_server.pyThe HTTP server exposes an SSE endpoint at http://<host>:<port>/sse.
Configure your client
Cursor
"Dish MCP": {
"command": "<PATH_TO_VENV>/bin/fastmcp",
"args": ["run", "<PATH_TO_REPO>/src/mcp_server.py"],
"cwd": "<PATH_TO_REPO>",
"transport": "stdio"
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"Dish MCP": {
"command": "<PATH_TO_VENV>/bin/fastmcp",
"args": ["run", "<PATH_TO_REPO>/src/mcp_server.py"],
"cwd": "<PATH_TO_REPO>"
}
}
}The server loads auth values from .env automatically. Keep .env as the source of truth for DISH_COOKIE, TEAM_ID, MEMBER_ID, DISH_EMAIL, and DISH_PASSWORD instead of hardcoding those values in your Claude config.
Available Tools
3 toolsbook_roomB
Book a room using the Dish Manchester API.
Args: datetime_range: Datetime range for the booking meeting_room_name: Name of the meeting room user_info: User information. If not provided, looks for TEAM_ID and MEMBER_ID env vars. cookie: Authentication cookie. If not provided, looks for DISH_COOKIE env var. summary: Title of the booking: default to "meeting"
Inputs: datetime_range (required), meeting_room_name (required), user_info, cookie, +1 more. Returns: result
cancel_bookingA
Cancel a room booking using the DiSH API.
To cancel a booking, you need to know the booking ID. You can get the booking ID by using the
check_availability tool to get the bookings for a room and date range.
Args: booking_id: The ID of the booking to cancel (e.g., "692192791c60f69c20311db3") cookie: Authentication cookie. If not provided, looks for DISH_COOKIE env var. skip_cancellation_policy: Whether to skip cancellation policy (default: False)
Inputs: booking_id (required), cookie, skip_cancellation_policy. Returns: result
check_availability_and_list_bookingsC
Check room availability for the DiSH API and list bookings for a room and date range.
Args: datetime_range: Datetime range for the query resource_ids: Optional list of room resource IDs to query. cookie: Authentication cookie. If not provided, looks for DISH_COOKIE env var. ctx: Context object.
Returns: str: The availability summary.
Inputs: datetime_range (required), resource_ids, cookie. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: book_room creates bookings, cancel_booking removes them, and check_availability_and_list_bookings queries availability and existing bookings. The descriptions explicitly differentiate their functions, and the cancel_booking tool even references check_availability_and_list_bookings as a way to find booking IDs, showing complementary rather than overlapping roles.
The tool names follow a consistent verb_noun pattern (book_room, cancel_booking, check_availability_and_list_bookings), all using snake_case. However, check_availability_and_list_bookings is longer and combines two actions, which slightly deviates from the simpler verb_noun style of the others, but the overall pattern remains clear and readable.
With 3 tools, this server is well-scoped for its purpose of managing room bookings via the DiSH API. Each tool earns its place by covering essential operations: booking, canceling, and checking availability/listings. This count is appropriate for a focused domain without being too thin or bloated.
The tool set provides complete CRUD/lifecycle coverage for room bookings: create (book_room), read (check_availability_and_list_bookings), and delete (cancel_booking). A minor gap is the lack of an update tool for modifying existing bookings, but agents can work around this by canceling and rebooking. The domain is clearly covered for core workflows.
Maintenance
Related MCP Connectors
Find free rooms and book, change or cancel them. Sign in from Claude, ChatGPT or Grok Bot.
AI-native scheduling and booking: check availability, book meetings, share links.
Booking engine for rooms, desks, sessions and courses: listings, rates, availability and bookings.
Manage Bookla bookings, availability, services, resources and clients with AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to search for available meeting rooms, check reservation status, and create room bookings through an integrated SSO-authenticated meeting room system. Supports natural language queries for room availability by date, time, floor, and duration requirements.-
- FlicenseBqualityDmaintenanceEnables natural language booking and management of rooms in Nexudus coworking spaces, including listing rooms, checking availability, booking, viewing/cancelling bookings, and schedules.6-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse, search, and book meeting rooms across multiple buildings with realistic seed data and conflict detection.-
- AlicenseAqualityDmaintenanceEnables AI agents to query office locations and meeting rooms from the Shangang Capital Digital Office Platform via natural language.4MIT