OfficeRnD MCP Server

A production-ready Model Context Protocol (MCP) server that exposes the complete OfficeRnD REST API as AI-friendly tools. Enables AI clients (Claude Desktop, ChatGPT, Cursor, VS Code, and others) to interact with your coworking space management platform using natural language.

⚡ Full CRUD — not read-only. This server supports create, update, and delete operations across all OfficeRnD resources in addition to reads. Ask your AI assistant to create bookings, update members, delete invoices, or perform any other write operation. Write tools are prefixed with [WRITE] in their descriptions. Call health_check to get a full list of available read and write tools at any time.

Table of Contents

• Overview

• Architecture

• Capabilities at a Glance

• Installation

• Authentication

• Configuration

• MCP Tools

• Client Setup

  • VS Code (Copilot)

  • Claude Desktop

  • Cursor

  • ChatGPT

• VS Code Extension

• Development

• Troubleshooting

• Deferred Endpoints

• Contributing

• License

Related MCP server: Finizi B4B MCP Server

Overview

This monorepo provides everything needed to connect any MCP-compatible AI client to OfficeRnD:

Architecture

AI Client
(Claude Desktop / ChatGPT / Cursor / VS Code)

           │
           │  MCP (stdio)
           ▼

┌─────────────────────────────────────────┐
│           @officernd/mcp                │
│  Tool Registry (160+ CRUD + business)   │
├─────────────────────────────────────────┤
│           @officernd/core               │
│  Business helpers (rooms, members, …)  │
├─────────────────────────────────────────┤
│           @officernd/sdk                │
│  OAuth2 · HTTP Client · Pagination      │
│  Retries · Rate Limiting · Logging      │
└─────────────────────────────────────────┘

           │
           ▼

    OfficeRnD REST API

The SDK has no MCP dependency, making it reusable in non-MCP contexts.

Capabilities at a Glance

This server is fully mutation-capable — it is not limited to read operations.

Write tools are prefixed with [WRITE] in their MCP tool descriptions so that AI agents can identify them at a glance.

Call health_check at any time to receive a live JSON summary of every available tool, separated into readTools and writeTools lists.

Installation

Prerequisites

• Node.js 22 or later

• An OfficeRnD account with API access

• OAuth2 Client ID and Client Secret (see Authentication)

Install the MCP Server

npm install -g @officernd/mcp

This installs the officernd-mcp command globally.

Verify Installation

officernd-mcp --version

Authentication

OfficeRnD uses OAuth2 Client Credentials for API access.

Obtain Credentials

1. Log in to your OfficeRnD dashboard

2. Go to Settings → Integrations → API

3. Create a new OAuth2 application

4. Copy your Client ID and Client Secret

5. Note your Organization Slug (the subdomain in your OfficeRnD URL, e.g. my-space from my-space.officernd.com)

Required Scopes

For the Flex API v2 (recommended), grant your OAuth2 application the specific scopes it needs. Examples:

flex.community.members.read
flex.community.members.create
flex.space.bookings.read
flex.space.bookings.create
flex.billing.charges.read

Your OfficeRnD OAuth2 application must be configured with the scopes you want the MCP server to use. You must specify at least one scope — OfficeRnD will reject token requests that do not include a scope. Configure the OFFICERND_SCOPES environment variable (space-separated list) for the MCP server, or set officernd.scopes in VS Code settings for the extension.

The token endpoint is rate-limited to 5 requests per minute. The SDK automatically caches tokens and reuses them until 60 seconds before expiry.

Configuration

Configure the server using environment variables:

Example

export OFFICERND_CLIENT_ID="your_client_id"
export OFFICERND_CLIENT_SECRET="your_client_secret"
export OFFICERND_ORG="my-coworking-space"
export OFFICERND_SCOPES="flex.community.members.read flex.space.bookings.read"
officernd-mcp

Security note: Never hardcode credentials in configuration files. Use environment variables or a secrets manager. The VS Code extension generates MCP config with ${env:...} placeholders so secrets are never written to disk.

MCP Tools

The server automatically generates tools from the resource registry. Every resource supports a consistent set of operations:

CRUD Tools (per resource)

Supported Resources

Business / AI Convenience Tools

Setup Tool

Example AI Interactions

"Show me all members who joined in the last 30 days"
→ list_members with date filters

"Find available meeting rooms tomorrow at 2pm for 8 people"
→ find_available_rooms

"Which memberships are expiring this month?"
→ find_memberships_expiring_soon with daysUntilExpiry: 30

"Show today's visitors"
→ get_todays_visitors

"How many unpaid invoices do we have?"
→ get_unpaid_invoices

"Show me all resources, their types, and pricing rates for our downtown location"
→ get_inventory with locationId

"What's the cancellation policy for this resource rate?"
→ get_resource_rate_cancellation_policy with resourceRateId

"Preview the checkout cost for this member on this plan before charging them"
→ preview_checkout with filters (memberId, planId)

"Is the OfficeRnD connection working?"
→ health_check

"Book the downtown conference room for tomorrow at 2pm for 2 hours"
→ create_booking with resourceId, start, end

"Cancel John's booking"
→ delete_booking with id

"Update the member's email address"
→ update_member with id and data

"Add a new member named Jane Smith"
→ create_member with data

"Create a visitor pass for next Monday"
→ create_visitor with data

"Finalize the checkout for this member's plan"
→ execute_checkout with data

"What write operations can this server perform?"
→ health_check — returns writeTools list with all available mutation tools

Client Setup

VS Code (Copilot)

Option A: Using the VS Code Extension (Recommended)

1. Install the OfficeRnD MCP extension from the VS Code Marketplace

2. Run command: OfficeRnD: Configure Connection

3. Enter your Client ID, Client Secret, and Organization Slug

4. Run command: OfficeRnD: Generate MCP Configuration

5. The extension writes .vscode/mcp.json with secure environment variable references

Note: The generated config uses ${env:OFFICERND_CLIENT_ID} references. You must also export those variables in your shell profile (.bashrc, .zshrc, etc.) so the MCP server process can read them. See Option B below for details.

Option B: Manual Configuration with Environment Variables

Create or edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "officernd": {
      "command": "officernd-mcp",
      "env": {
        "OFFICERND_CLIENT_ID": "${env:OFFICERND_CLIENT_ID}",
        "OFFICERND_CLIENT_SECRET": "${env:OFFICERND_CLIENT_SECRET}",
        "OFFICERND_ORG": "your-org-slug"
      }
    }
  }
}

Set environment variables in your shell profile (.bashrc, .zshrc, etc.):

export OFFICERND_CLIENT_ID="your_client_id"
export OFFICERND_CLIENT_SECRET="your_client_secret"

Option C: Runtime Configuration via configure_officernd (Simplest)

The server can start without any credentials and be configured later through its configure_officernd tool. This is the easiest option when you do not want to set environment variables.

Create .vscode/mcp.json with just the command — no env block required:

{
  "servers": {
    "officernd": {
      "command": "officernd-mcp"
    }
  }
}

Then ask your AI assistant to configure the connection:

"Configure OfficeRnD with clientId my-client-id, clientSecret my-secret, orgSlug my-org"
→ configure_officernd

The AI will call the configure_officernd tool and all other tools will become available for the lifetime of that server process.

Claude Desktop

Edit your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "officernd": {
      "command": "officernd-mcp",
      "env": {
        "OFFICERND_CLIENT_ID": "your_client_id",
        "OFFICERND_CLIENT_SECRET": "your_client_secret",
        "OFFICERND_ORG": "your-org-slug"
      }
    }
  }
}

Restart Claude Desktop. You should see "officernd" in the MCP servers list.

Cursor

Create or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "officernd": {
      "command": "officernd-mcp",
      "env": {
        "OFFICERND_CLIENT_ID": "your_client_id",
        "OFFICERND_CLIENT_SECRET": "your_client_secret",
        "OFFICERND_ORG": "your-org-slug"
      }
    }
  }
}

ChatGPT

ChatGPT supports MCP via the OpenAI desktop app. Configure in the app's MCP settings using the same officernd-mcp command with the required environment variables.

VS Code Extension

The officernd-mcp-vscode extension provides a first-class developer experience:

Commands

Status Bar

The status bar shows the current connection state:

• $(check) OfficeRnD Connected — credentials configured

• $(warning) OfficeRnD Disconnected — no credentials

Security

Credentials are stored in VS Code's SecretStorage (OS keychain). Secrets are never written to:

• settings.json

• Workspace settings

• mcp.json — env var references (${env:...}) are used instead

Development

Prerequisites

node --version  # Must be >= 22
npm --version

Clone and Install

git clone https://github.com/EmpathDesign/OfficeRnD_MCP.git
cd OfficeRnD_MCP
npm install

Build

npm run build

Test

npm test

Lint and Format

npm run lint          # ESLint
npm run format:check  # Prettier check
npm run format        # Prettier fix

Monorepo Structure

packages/
├── sdk/          @officernd/sdk     — REST API SDK
├── core/         @officernd/core    — Business helpers
├── mcp/          @officernd/mcp     — MCP server + CLI
└── vscode/       officernd-mcp-vscode — VS Code extension

Adding a New Resource

The resource registry in packages/sdk/src/resources/registry.ts is the single source of truth. Add a new entry:

{
  name: 'my_resource',
  path: '/my-resources',
  description: 'Description of the resource',
  operations: ['list', 'get', 'create', 'update', 'delete', 'count'],
}

The MCP server automatically generates all tools from this registry. No additional code changes are needed.

Troubleshooting

Tools return "OfficeRnD is not configured"

The server starts without credentials when no environment variables are set. To authenticate, ask your AI assistant to call the configure_officernd tool:

"Configure OfficeRnD with my credentials"

Or set the OFFICERND_CLIENT_ID and OFFICERND_CLIENT_SECRET environment variables before starting the server (see Configuration).

Authentication errors

OAuth2 token request failed: 401

• Verify your Client ID and Client Secret are correct

• Ensure the OAuth2 application has the Flex API scopes your workflows need (for example flex.community.members.read)

• Check that your organization slug matches your OfficeRnD URL

Rate limiting

The token endpoint is limited to 5 requests/minute. The SDK caches tokens automatically — this should only occur if the server is restarted very frequently.

404 errors on API calls

• Verify your OFFICERND_ORG is set to the correct organization slug

• Check that the API version (OFFICERND_API_VERSION) matches what your account supports

Enabling debug logging

OFFICERND_LOG_LEVEL=debug officernd-mcp

Logs are written to stderr to keep MCP's stdout protocol clean.

Deferred Endpoints

The following OfficeRnD API resources are not yet implemented. They are documented here for follow-up:

Checkout flows (preview_checkout / execute_checkout) and resource-rate cancellation policy lookups (get_resource_rate_cancellation_policy) are now supported — see MCP Tools.

The RESOURCES registry in packages/sdk/src/resources/registry.ts is designed for declarative extension — adding a new resource requires a single entry.

Contributing

1. Fork the repository

2. Create a feature branch: git checkout -b feature/my-feature

3. Make changes and add tests

4. Verify: npm run build && npm test && npm run lint

5. Submit a pull request

All PRs run the CI workflow (lint → format check → build → test) automatically.

License

MIT © EmpathDesign