Integration

Nexudus integration

Nexudus is a coworking and flexible workspace management platform. This integration covers part of its admin REST API: list and read the locations an account manages, bookable resources (meeting rooms, desks, offices) and resource types, create or delete resources, list, read, create and delete bookings, read products, membership plans (tariffs) and booking rates, and list, read, create and delete community events. Customer (coworker) records, invoices and payments, contracts, check-ins, help desk, teams, access control and system settings are not exposed, and reads withhold customer names and phone numbers, event host and attendee names, location postal addresses, contact details and payment data. Updates are left out because Nexudus replaces the whole record on update, which would erase the withheld fields. Authentication is HTTP Basic with the email and password of a Nexudus admin user; every route also needs the matching role (for example Booking-Create) or a full unrestricted administrator. The docs state no rate limit.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Nexudus.Built from the 22 Nexudus tools below, on the connection you add once.

What you can do with Nexudus

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Booking, 4 operations

  • create_bookingCreate bookingPOSTCreates a real booking of a resource for a time range, optionally for a customer, recurring, with products, or charged and invoiced now. Returns its Id in Value; check WasSuccessful.
  • delete_bookingDelete bookingDELETEPermanently deletes a booking; this cannot be undone. Requires the Booking-Delete role or a full administrator.
  • get_bookingGet bookingGETGets one booking by id: resource, customer id, UTC times, rate, notes, recurrence, check-in and invoice state. Customer names and phone numbers are withheld.
  • list_bookingsList bookingsGETLists bookings with resource, customer id, times, rate, tentative and invoicing state. Filter by resource, customer id, time range (from_/to_ filters) or booking number; paged.

Calendarevent, 4 operations

  • create_eventCreate eventPOSTCreates a real community event at a location (name, start and end dates required); it is published to members per PublishDate. Some flags send emails. Returns its Id in Value.
  • delete_eventDelete eventDELETEPermanently deletes a community event; this cannot be undone. Requires the CalendarEvent-Delete role or a full administrator.
  • get_eventGet eventGETGets one community event by id: descriptions, location, linked resource, dates, capacity, categories, publication and recurrence settings. Host and attendee names are withheld.
  • list_eventsList eventsGETLists community events with name, descriptions, location, linked resource, start and end dates, capacity, publish date and recurrence. Filter by location, name, resource or dates.

Resource, 4 operations

  • create_resourceCreate resourcePOSTCreates a bookable resource in a location (name, built-in category, resource type, display order and cancellation fee type are required). Creates it for real; returns its Id in Value.
  • delete_resourceDelete resourceDELETEPermanently deletes a resource; this cannot be undone. Requires the Resource-Delete role or a full administrator.
  • get_resourceGet resourceGETGets one bookable resource by id: location, type, capacity, booking rules, cancellation fee settings and amenity flags. Requires the Resource-Read role or a full administrator.
  • list_resourcesList resourcesGETLists bookable resources (meeting rooms, desks, offices, booths) with type, capacity, booking rules and amenities. Filter by location, type, name or visibility; paged with page and size.

Business, 2 operations

  • get_locationGet locationGETGets one location (business) by id: web address, country, currency, time zone, venue type, floors and opening hours. Postal address, contacts and payment data are withheld.
  • list_locationsList locationsGETLists the locations (businesses) the account can manage, with web address, country, currency, time zone, venue details and opening hours. Use their Id as BusinessId elsewhere.

Extraservice, 2 operations

  • get_booking_rateGet booking rateGETGets one booking rate (extra service) by id: price, charge period, the resource types and plans it applies to, its time window and length limits.
  • list_booking_ratesList booking ratesGETLists booking rates (extra services): the prices applied to bookings of resource types, with charge period, credit price, time window and length limits. Paged.

Product, 2 operations

  • get_productGet productGETGets one product by id: price, currency, tax rate, SKU, stock levels, visibility and the plans it is limited to.
  • list_productsList productsGETLists products (items sold one-off, with bookings or on contracts) with price, currency, tax rate, SKU, stock and visibility. Filter by location, name, SKU or type; paged.

Resourcetype, 2 operations

  • get_resource_typeGet resource typeGETGets one resource type by id: its name and location.
  • list_resource_typesList resource typesGETLists resource types (the custom categories resources belong to, which booking rates attach to). Filter by location or name; paged with page and size.

Tariff, 2 operations

  • get_tariffGet tariffGETGets one membership plan (tariff) by id: price, sign-up fee, invoicing cycle, contract and cancellation terms, and check-in, hours, booking and visitor limits.
  • list_tariffsList tariffsGETLists membership plans (tariffs) with price, sign-up fee, invoicing cycle, contract and cancellation terms and usage limits. Filter by location, name or visibility; paged.

Use Nexudus from Claude Code, Cursor or Codex

Connect Nexudus in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Nexudus operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Nexudus

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Nexudus once

    Add your Nexudus connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Nexudus integration FAQ

What can you do with the Nexudus integration?

LiveContext exposes 22 operations on Nexudus, covering booking, calendarevent, resource and business.

Popular integrations

Browse the whole catalog