communityLABSCO SUMMARY
Read-only, and only GET requests, by construction.
No tool here creates, modifies or deletes anything — which makes it a safe thing to hand an assistant that answers questions about a live workspace. Two details will bite otherwise: name filters need an exact full name, not a first name, and date and time output is converted to Eastern Time, so a booking window will not match a local clock unless you account for that. The read ceiling is OfficeRnD's own, 400 requests per minute.
What it is
A read-only server over the OfficeRnD coworking and flex-space platform. Rather than one tool per entity, it groups the data into five domains and takes an action, an entity and filters — so "list active members" and "show bookings for today" go through the same shape.
What you get
- People data: members, companies, memberships, check-ins, contracts, visits, visitors, opportunities and opportunity statuses, filterable by status, email, name, company, location and date bounds —
community - Space data: resources with a status action, bookings and booking occurrences, floors, assignments, amenities, passes and credits, with resource types
meeting_room,team_room,desk,hotdesk,desk_tranddesk_na—space - Financial data: payments filtered by status, member, company, document type and date range, plus fees, plans, and a coin and credit balance for a member or company in a given month —
billing - Collaboration data: events, tickets and posts —
collaboration - Configuration: locations, resource types, business hours and custom properties —
settings - Cursor-based pagination on every tool through
cursorNext, capped at 50 results per page
Requirements
OfficeRnD API credentials — a client ID, a client secret and your organisation slug — supplied as OFFICERND_CLIENT_ID, OFFICERND_CLIENT_SECRET and OFFICERND_ORG_SLUG. They come from the OfficeRnD admin dashboard under Integrations > API, and the slug is the identifier in your OfficeRnD URL. Node.js 18+; install from a clone with npm install and npm run build, then point your client at build/index.js. Authentication is OAuth 2.0 client credentials with tokens cached in memory.
Setup effort
Build from source — git clone https://github.com/MrBoor/officernd-mcp.git
USE CASES
Answering member questions without opening the admin console
Look up a member by email or exact name and read their memberships, contracts and recent check-ins in one pass.
Checking what is booked today
List bookings within a date window or ask for the status of meeting rooms, filtered by location.
Chasing outstanding payments
Filter payments by status and date range, and pull a member's credit balance for the month in question.
Reviewing open tickets and upcoming events
Read tickets by status and location alongside the event calendar, so community operations and facilities issues come from the same query.
5 tools
Listed in project docs. Your client may show a different list.
spacebillingcollaborationsettingsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 18+
- OFFICERND_CLIENT_ID in your environment
- OFFICERND_CLIENT_SECRET in your environment
- OFFICERND_ORG_SLUG in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/MrBoor/officernd-mcp.git
cd officernd-mcp
npm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"officernd": {
"command": "node",
"args": [
"<YOUR_PATH_TO_OFFICERND_MCP>/build/index.js"
],
"env": {
"OFFICERND_CLIENT_ID": "<YOUR_OFFICERND_CLIENT_ID>",
"OFFICERND_CLIENT_SECRET": "<YOUR_OFFICERND_CLIENT_SECRET>",
"OFFICERND_ORG_SLUG": "<YOUR_OFFICERND_ORG_SLUG>"
}
}
}
}<YOUR_PATH_TO_OFFICERND_MCP> is the full path of the officernd-mcp folder you cloned.
Claude Code
claude mcp add officernd \
-e OFFICERND_CLIENT_ID=<YOUR_OFFICERND_CLIENT_ID> \
-e OFFICERND_CLIENT_SECRET=<YOUR_OFFICERND_CLIENT_SECRET> \
-e OFFICERND_ORG_SLUG=<YOUR_OFFICERND_ORG_SLUG> \
-s user \
-- node <YOUR_PATH_TO_OFFICERND_MCP>/build/index.js<YOUR_PATH_TO_OFFICERND_MCP> is the full path of the officernd-mcp folder you cloned. Use -s project instead of -s user to scope it to the current project.