OfficeRnD MCP Server
A read-only MCP server that connects AI assistants to the OfficeRnD coworking and flex-space management platform. It enables natural language queries for community members, space bookings, billing records, and office resources.
README
OfficeRnD MCP Server
A read-only Model Context Protocol (MCP) server that connects AI assistants to the OfficeRnD coworking and flex-space management platform. Query members, companies, bookings, billing, and more through natural language.
What it does
This server exposes OfficeRnD data through 5 domain-grouped tools, covering 25+ entity types:
| Tool | Entities | Example queries |
|---|---|---|
| community | Members, companies, memberships, check-ins, contracts, visits, visitors, opportunities | "List all active members" / "Show me visits from last week" |
| space | Resources, bookings, booking occurrences, floors, assignments, amenities, passes, credits | "What meeting rooms are available?" / "List bookings for today" |
| billing | Payments, fees, plans, coin/credit stats | "Show pending payments" / "Get credit balance for March" |
| collaboration | Events, tickets, posts | "List open tickets" / "What events are coming up?" |
| settings | Locations, resource types, business hours, custom properties | "List all office locations" |
All tools are read-only — no data can be created, modified, or deleted.
Prerequisites
- Node.js 18+
- OfficeRnD API credentials — client ID, client secret, and organization slug (from your OfficeRnD admin dashboard under Integrations > API)
Quick start
git clone https://github.com/MrBoor/officernd-mcp.git
cd officernd-mcp
npm install
npm run build
Configuration
Set three environment variables (via .env file or directly):
OFFICERND_CLIENT_ID=your_client_id
OFFICERND_CLIENT_SECRET=your_client_secret
OFFICERND_ORG_SLUG=your_organization_slug
The org slug is the identifier in your OfficeRnD URL: app.officernd.com/.../{your_org_slug}.
Usage with Claude Desktop
- Open Claude Desktop > Settings > Developer > Edit Config.
- Add the server to
claude_desktop_config.json:
{
"mcpServers": {
"officernd": {
"command": "node",
"args": ["/absolute/path/to/officernd-mcp/build/index.js"],
"env": {
"OFFICERND_CLIENT_ID": "your_client_id",
"OFFICERND_CLIENT_SECRET": "your_client_secret",
"OFFICERND_ORG_SLUG": "your_organization_slug"
}
}
}
}
- Restart Claude Desktop. A hammer icon in the chat input confirms the connection.
Usage with ChatGPT Desktop
- Open the ChatGPT desktop app and go to Settings (
Cmd+,on macOS /Ctrl+,on Windows). - Navigate to Tools (or MCP Servers) and add a new server, or edit the config file directly at
~/.chatgpt/mcp.json:
{
"mcpServers": {
"officernd": {
"command": "node",
"args": ["/absolute/path/to/officernd-mcp/build/index.js"],
"env": {
"OFFICERND_CLIENT_ID": "your_client_id",
"OFFICERND_CLIENT_SECRET": "your_client_secret",
"OFFICERND_ORG_SLUG": "your_organization_slug"
}
}
}
}
- Restart ChatGPT. The server should appear in your tools list.
Note: MCP support requires the ChatGPT desktop app (macOS or Windows) — it is not available in the web version. Requires a Plus, Team, or Enterprise subscription.
Usage with Claude Code (CLI)
Option A — CLI command (recommended):
claude mcp add officernd \
-e OFFICERND_CLIENT_ID=your_client_id \
-e OFFICERND_CLIENT_SECRET=your_client_secret \
-e OFFICERND_ORG_SLUG=your_org_slug \
-s user \
-- node /absolute/path/to/officernd-mcp/build/index.js
Use -s project instead of -s user to scope to the current project only.
Option B — Project config file:
A .mcp.json is included in the repo. Fill in your credentials:
{
"mcpServers": {
"officernd": {
"type": "stdio",
"command": "node",
"args": ["build/index.js"],
"env": {
"OFFICERND_CLIENT_ID": "your_client_id",
"OFFICERND_CLIENT_SECRET": "your_client_secret",
"OFFICERND_ORG_SLUG": "your_organization_slug"
}
}
}
}
Verify: Run /mcp inside Claude Code to check the server status.
Tool reference
Each tool accepts an action (list, get, or a special action), an entity type, and optional filters. All support cursor-based pagination via cursorNext (max 50 results per page).
community
Query community/people data.
| Entity | Actions | Filters |
|---|---|---|
members |
list, get | status, email, name, company, location |
companies |
list, get | name, status, location |
memberships |
list, get | member, company, status |
checkins |
list, get | member, location, startAfter, startBefore |
contracts |
list, get | member, company, status |
visits |
list, get | location, startAfter, startBefore |
visitors |
list | (pagination only) |
opportunities |
list, get | status, member, company |
opportunity_statuses |
list | (pagination only) |
space
Query space/resource data.
| Entity | Actions | Filters |
|---|---|---|
resources |
list, get, status | type, name, location |
bookings |
list, get | resourceId, member, company, location, startAfter, startBefore |
booking_occurrences |
list | seriesStart (required), seriesEnd (required), resourceId, member, location |
floors |
list, get | location, name |
assignments |
list | resourceId, membershipId |
amenities |
list, get | title |
passes |
list, get | member, company |
credits |
list, get | member, company |
Resource types for the type filter: meeting_room, team_room, desk, hotdesk, desk_tr, desk_na.
billing
Query billing/financial data.
| Entity | Actions | Filters |
|---|---|---|
payments |
list, get | status, member, company, documentType, dateFrom, dateTo, sort |
fees |
list | (pagination only) |
plans |
list, get | sort |
Special action — coin_stats: Get coin/credit balance for a member or company in a given month. Parameters: member, company, month (e.g., 2026-03).
collaboration
Query collaboration data.
| Entity | Actions | Filters |
|---|---|---|
events |
list, get | location, startAfter, startBefore |
tickets |
list, get | status, member, location |
posts |
list, get | (pagination only) |
settings
Query organization configuration.
| Entity | Actions | Filters |
|---|---|---|
locations |
list, get | name |
resource_types |
list | (pagination only) |
business_hours |
list | location |
custom_properties |
list | (pagination only) |
Development
npm run dev # Watch mode — recompiles on changes
npm run inspect # Launch with MCP Inspector for debugging
Architecture
src/
index.ts # Entry point — env validation, tool registration, stdio transport
auth.ts # OAuth 2.0 client-credentials flow with token caching
client.ts # API client — GET helper, pagination, base URL
tools/
community.ts # Members, companies, memberships, check-ins, contracts, visits
space.ts # Resources, bookings, floors, assignments, amenities
billing.ts # Payments, fees, plans, coin stats
collaboration.ts # Events, tickets, posts
settings.ts # Locations, resource types, business hours, custom properties
Request flow: AI assistant → MCP stdio → tool handler → OAuth token (cached) → HTTP GET → OfficeRnD API → formatted response.
API rate limits
OfficeRnD API v2 enforces rate limits per integration per organization:
| Operation | Per Minute | Per Day |
|---|---|---|
| Read (GET) | 400 | 20,000 |
| Token generation | 5 | — |
This server only performs read operations. OAuth tokens are cached in memory and reused until expiry (with a 60-second buffer), keeping token requests well under the 5/min limit.
If you receive HTTP 429 Too Many Requests, implement exponential backoff and spread requests out rather than bursting. Contact OfficeRnD support for rate limit exceptions if needed.
Security
- Read-only — Only GET requests; no data modification possible
- OAuth 2.0 client credentials — Tokens cached in memory, auto-refreshed before expiry
- No secrets in code — Credentials are passed via environment variables
- Scoped access — Only requests the minimum read permissions needed
Notes
- Date/time output is converted to Eastern Time (ET)
- Name filters (where noted) require exact full name match (e.g., "Jane Smith" not "Jane")
- Pagination is capped at 50 items per page (both default and maximum)
- The
$infilter operator is capped at 50 values
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.