LabscoMCP early access ↗
MrBoorMCP SERVER

OfficeRnD MCP Server

Query members, bookings, billing, tickets and locations in OfficeRnD from a conversation — read-only, with five domain tools covering 25+ entity types.

by MrBoor ↗ERP & Vertical Business SystemsCommunity

LABSCO 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_tr and desk_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