OfficeRnD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OFFICERND_ORG_SLUG | Yes | The organization slug is the identifier in your OfficeRnD URL: app.officernd.com/.../{your_org_slug} | |
| OFFICERND_CLIENT_ID | Yes | Your OfficeRnD client ID from your OfficeRnD admin dashboard under Integrations > API | |
| OFFICERND_CLIENT_SECRET | Yes | Your OfficeRnD client secret from your OfficeRnD admin dashboard under Integrations > API |
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 |
|---|---|
| communityA | Query community/people data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID. Entity-specific filters when listing:
|
| spaceA | Query space/resource data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID. action=status: Check current availability of a resource (requires id). Entity-specific filters when listing:
|
| billingA | Query billing/financial data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID (payments, plans). action=coin_stats: Get coin/credit balance for a member or company in a given month. Entity-specific filters when listing:
|
| collaborationB | Query collaboration data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID. Entity-specific filters when listing:
|
| settingsA | Query organization settings and configuration in OfficeRnD. action=list: List configuration entities. action=get: Get a single location by ID (locations only). Entity-specific filters when listing:
|
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 5 tools
While the five tools map to distinct business domains (billing, collaboration, community, settings, space), there is conceptual overlap—e.g., 'credits' appear in both billing and space tools, and member-related data is scattered across community, billing, and space. The broad 'mega-tool' approach requires agents to infer which domain bucket contains specific entities.
All tool names follow a consistent pattern of single lowercase nouns representing functional domains (billing, collaboration, community, settings, space). Although they lack action verbs (e.g., 'get_billing'), the naming convention is uniform and predictable.
Five tools is a reasonable count for the OfficeRnD domain, falling within the ideal 3-15 range. However, each tool is a heavy aggregate covering multiple entities (e.g., community covers 9+ entity types), suggesting the surface could benefit from finer granularity despite the appropriate total count.
The tool set is strictly read-only (limited to list, get, status, and coin_stats actions) for a management platform that fundamentally requires write operations. Critical gaps include inability to create/update bookings, members, or invoices, which will prevent agents from completing core coworking management workflows like checking in visitors or reserving rooms.