Skip to main content
A hosted assistant runs on its vendor’s servers, so there is nothing to install on your computer. It connects to Little Spaces’ remote MCP server, and you approve it once with OAuth. This page covers the connection, the permissions to grant, and what you see afterwards, with steps for Grok Bot.

​
Connect it

1

Copy the MCP URL

On the Agents page, under Connect a hosted assistant, copy the MCP URL:
2

Add it to the assistant

In the assistant, add a remote MCP server with that URL. When it asks how to authenticate, choose your own sign-in (OAuth), not a key or token.
3

Approve it

Finish the sign-in in your browser. On Little Spaces’ approval page, name the agent, turn off Work on tasks you’ve approved, and choose Allow.
4

Tell it the project

Tell the assistant which project its reports are for, and ask it to check Little Spaces for your answers whenever it starts.

​
Permissions

The approval page lists what the agent may do: With work turned off, a hosted assistant can still read your projects and activity, ask questions about them, report milestones and asks, send liveness signals and fetch your answers. Connecting never approves new work, merges, deployments or spending. Little Spaces ignores any other permission an app asks for, such as openid or offline_access, and they never add access. Only approve a connection you just asked an agent to make. The app supplies its own name, so the name isn’t verified.

​
What you see afterwards

  • On the Agents page, the assistant is an agent of its own, marked “MCP OAuth”. Its card says “Connected over MCP. Its reports appear under Activity, not Runs.”
  • Its reports appear in Activity under the agent’s name, and its questions in your inbox.
  • It shows under Runs only if it sends liveness signals itself (signal_run). Its reports alone appear in Activity.
  • Your answers wait in Little Spaces until it next runs and fetches them. Little Spaces can’t wake it.
The assistant’s access lasts an hour at a time and renews by itself. If it goes 30 days without renewing, it has to sign in again. To revoke its access to Little Spaces, choose Disconnect agent on its card. That revokes all its credentials at once, and reconnecting needs a new approval. It doesn’t stop a session already running in the assistant’s app.

​
Grok Bot

Grok Bot is xAI’s persistent agent. These steps come from xAI’s and Cursor’s Grok Bot pages, and haven’t been seen working with a real connection yet.
Grok Bot isn’t on the Free or Plus plans: it needs a paid Cursor plan, The X Subscription’s Premium or higher, a linked SuperGrok subscription or a Grok Business seat. Custom MCP servers are documented for Team Bots, which are for members of a Cursor team.
  1. In the Grok Bot desktop app, open the Team Bot that should report to you, and click its name at the top of its chat to open its details.
  2. Under Setup, choose the Plugins card, or ask the Bot in its chat to add a custom MCP server.
  3. Add a custom MCP server of the Remote HTTPS kind, name it Little Spaces, and paste Little Spaces’ MCP URL.
  4. If it asks how to authenticate, choose each person’s own sign-in (OAuth), not a key or token for the Bot, so that the approval is yours.
  5. When Grok Bot asks you to Authenticate, finish the sign-in in your browser. On Little Spaces’ approval page, name the agent (for example “Grok Bot (Ops)”), turn off Work on tasks you’ve approved, and choose Allow.
  6. Back in Grok Bot, check that the plugin no longer shows Needs auth. Then tell the Bot in its chat which project its reports are for, and ask it to remember to check Little Spaces for your answers whenever it starts.
Answers: Grok Bot fetches them when you next message it, or when one of its routines runs. Little Spaces can’t wake it yet.