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.

​

Troubleshooting

​

Connection issues

​

My client cannot reach https://mcp.nexudus.com

• Check that you typed the URL exactly: https://mcp.nexudus.com — no trailing slash, no extra path.
• Check your internet connection.
• Check that a firewall or proxy is not blocking outbound HTTPS connections to mcp.nexudus.com.

​

The login window does not open

• Most MCP clients use your default browser to show the Nexudus login page. Make sure you have a default browser set.
• Pop-up blockers can prevent the window from opening. Disable them and retry.
• In Claude Code and VS Code, check the log output for the manual login URL — you can open it in any browser to complete sign-in.

​

”Authentication required” or “Unauthorized” mid-conversation

Your 8-hour session has expired. Reconnect from your client’s MCP settings — see Sessions and re-authentication for the exact steps per client.

​

Login redirects back to a Nexudus error page

• Your Nexudus credentials may have changed. Try signing in directly at spaces.nexudus.com first.
• Your account may have been deactivated — contact your Nexudus administrator.

​

Tool issues

​

The AI assistant says no Nexudus tools are available

• Confirm the connector shows as Connected in your client’s settings.
• In ChatGPT, confirm the Nexudus connector is toggled on in the current chat’s tools menu — it must be enabled per chat.
• Restart your MCP client. Some clients only load tools at app startup.
• Disconnect and reconnect the connector.

​

The assistant picks the wrong field name or filter

The assistant should call nexudus_describe_entity before creating or filtering, but sometimes it skips that step. Ask it to describe the entity explicitly:

“Before updating that, describe the ‘products’ entity and list its filter keys.”

This pulls in the correct field names so the next call works.

​

List queries return wrong results

The Nexudus API uses specific filter keys (for example, Booking_FromTime rather than FromTime). The MCP server validates filter keys and returns an error listing the valid ones — the assistant should self-correct on the next attempt. If results still look wrong, ask the assistant to describe the entity and rerun the query using the listed filter keys.

​

A create or update fails with a validation error

• Ask the assistant to call nexudus_describe_entity and check which fields are required for the entity.
• Some entities have additional rules (price minimums, contract overlaps, location-specific defaults) that the API enforces. The error message usually says which field caused the problem.

​

Delete is too aggressive

If the assistant has deleted more than you intended, there is no automatic undo. Recovery options depend on the entity:

• For most entities, you would need to recreate them from a backup or from another source.
• For destructive bulk actions, always ask the assistant to list first so you can confirm the scope before deletion.

​

Performance issues

​

Calls feel slow

• The first call after connecting can take a moment as the session initialises and entity definitions are loaded.
• Long list calls take more time on large datasets. Ask the assistant to use pagination — “show the first 25 records” — and continue from there.

​

”Session not found” errors after a long break

• The server may have restarted while your session was idle. Reconnect from your client’s MCP settings — re-authenticating creates a fresh session.

​

Where to get more help

• Nexudus help centre: help.nexudus.com
• MCP server repository: github.com/Nexudus-Ltd/nexudus-coworking-mcp-stateful
• Entity reference: CLI entity reference — same entities are available through the MCP server.

​

Next steps