Skip to main content

Documentation Index

Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt

Use this file to discover all available pages before exploring further.

Available Tools

The Nexudus MCP server gives your AI assistant a small set of generic tools that work across every entity in Nexudus, plus a few specialist tools that wrap common queries with friendlier parameters. You do not call these tools yourself — the assistant decides which to use based on your question.

Generic tools

These tools cover any of the 208 entity types supported by Nexudus — bookings, products, resources, members, invoices, and so on. The assistant picks the right entity based on your question.
ToolWhat it does
nexudus_list_entitiesLists every available entity type. Used at the start of a conversation to discover what is available.
nexudus_describe_entityReturns the field schema, filter options, and enum values for a chosen entity.
nexudus_listSearches and filters records of a chosen entity, with pagination.
nexudus_getFetches a single record by ID, including collection fields omitted from list responses.
nexudus_createCreates a new record.
nexudus_updateUpdates an existing record by ID.
nexudus_deleteDeletes a record by ID. The assistant should confirm with you before calling this.
nexudus_list_commandsLists special operations (like archive or activate) available on an entity.
nexudus_run_commandRuns a named command (such as Archive or CheckIn) on one or more records.
nexudus_get_skill_guideFetches the cross-cutting guide that teaches the assistant how to use the Nexudus tools.
nexudus_get_entity_guideFetches the per-entity guide for a specific entity type.

Specialist tools

Specialist tools wrap a common query against a single entity, with friendly parameter names that map to the right Nexudus filter keys. The assistant uses them when the request matches one of these flows — no schema lookup needed first, so the response is faster.

nexudus_fetch_bookings

Fetches bookings with friendly parameters: fromTime, toTime, coworkerId, resourceId, businessId (the location), tentative, invoiced, archived. Example prompt: “List bookings at my London location between 9am and 5pm tomorrow that are still tentative.”

nexudus_fetch_visitors

Fetches visitors with friendly parameters: fullName, email, businessId (the location), coworkerId (the host), expectedFrom, expectedTo, hostApprovalStatus (pending, approved, or declined). Example prompt: “Show me the pending visitor requests expected at my main location this week.”

How the assistant chooses tools

A typical conversation looks like this:
1

The assistant identifies the entity

For an open-ended question, the assistant calls nexudus_list_entities once to discover what is available.
2

It learns the entity's shape

Before listing or creating, it calls nexudus_describe_entity to learn the filter keys, required fields, and enum values.
3

It runs the operation

Depending on your question, it calls nexudus_list, nexudus_get, nexudus_create, nexudus_update, nexudus_delete, or nexudus_run_command.
4

It summarises the result

The raw response is shaped into a human-readable answer for you.
For booking and visitor queries, the assistant often skips straight to the specialist tools above.

Coverage

The Nexudus MCP server is metadata-driven: entity definitions, supported operations, fields, and filter keys are loaded from the Nexudus-Ltd/nexudus-coworking-cli repository at server startup. That repository is the single source of truth for the Nexudus CLI, the public skills/reference docs, and this MCP server, so all three stay in sync. When new entities are added upstream, they appear in the MCP server automatically. For a complete list of entities and their supported operations (list, get, create, update, delete, run-command), see the CLI entity reference — the same entities are available through the MCP server.

Safety

The MCP server cannot do anything your Nexudus account cannot do. But within your permissions, create, update, and delete operations are real: they affect live data immediately and there is no undo button. Always read the proposed tool call before approving it.
Vague instructions like “clean up old bookings” can lead the assistant to delete more than you expected. Be specific about what to keep and what to remove, and consider asking for a list first to confirm the scope before any deletions.

Next steps

Sessions and re-auth

Why sessions expire after 8 hours.

Troubleshooting

Common issues and how to fix them.