nexudus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUDUS_EMAIL | Yes | Your Nexudus login email | |
| NEXUDUS_PORTAL | Yes | Your space's portal hostname (e.g., yourspace.spaces.nexudus.com) | |
| NEXUDUS_PASSWORD | Yes | Your Nexudus login password | |
| NEXUDUS_COWORKER_ID | No | Optional Nexudus member ID. If omitted, extracted from bookings. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_roomsB | List all bookable rooms with capacity and amenities. Can filter by type (Conference Room, Lab Equipment, Wellness Room). |
| search_available_roomsC | Find which rooms are free during a specific time window |
| get_room_scheduleB | View all bookings for a specific room on a given date |
| book_roomC | Book a room for a specific time slot |
| my_bookingsB | List your upcoming (or recent past) bookings |
| cancel_bookingC | Cancel a booking by its ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of room booking: inventory (list_rooms), availability search (search_available_rooms), schedule viewing (get_room_schedule), booking action (book_room), personal bookings (my_bookings), and cancellation (cancel_booking). No two tools overlap in purpose, and descriptions clearly delineate their scope.
Five of six tools follow a consistent verb_noun snake_case pattern (list_rooms, search_available_rooms, get_room_schedule, book_room, cancel_booking). 'my_bookings' deviates as a possessive noun phrase, but the overall convention remains readable and predictable.
Six tools provide a well-scoped set for a room booking domain, covering discovery, availability, scheduling, booking, and cancellation without redundancy. The count is typical for a focused MCP server.
Core lifecycle operations are present: list rooms, check availability, view schedules, book, list personal bookings, and cancel. The only notable gap is a dedicated update/reschedule operation, but this can be worked around by canceling and rebooking.