Skip to main content
Lists every space the current user belongs to and marks which ones this MCP connection may use and which one is the default. Useful for agency / multi-client workflows where the user juggles many workspaces.

When to use

  • “What spaces / teams / clients do I have access to?”
  • “Am I in the right space?”

Session scope

A connection covers one space, the spaces you chose, or all your spaces. You decide on the Cometly consent screen when you connect, and you also pick a default space. Tools run in the default space unless you pass space_id.
  • granted spaces can be used in this session. With an All my spaces connection, every space you belong to is granted, including spaces you’re added to later. Your membership, your role in that space, and the team’s plan are re-checked on every call.
  • A space that isn’t granted can’t be read. Pass its id as space_id and the call returns an authorization error; reconnect Cometly in your MCP client and include that space.
  • On the legacy /mcp/{space_id}/public-api URL, the path names the space and a different space_id is refused.

Using space_id

Every tool accepts an optional space_id argument. Pass the id from this tool’s output to run a call in a granted space other than the default:
Custom field and event labels shown in tool descriptions describe the default space. Call list_custom_events with space_id to see another space’s labels.

Parameters

Output

The current column from earlier versions is gone; use default.