Connect your agent

Rubikc works with Claude, Cursor and Codex, and there are two ways to connect them.

	Use when
The shared URL	You want to connect quickly, or your assistant has a built-in Rubikc connector
A named connection	You want to tell your connections apart in Admin

Both give the assistant the same access. The difference is how it shows up afterwards.

The shared URL

One URL, the same for everyone. Assistants with a connector directory — Claude, among others — use this one, and handle the login themselves.

1. In Admin, open Settings › MCP and copy the MCP URL.

2. Add it to your assistant as an MCP server.

3. Log in with your Rubikc account when prompted.

That is the whole setup.

A named connection

Instead of sharing one URL, you can create a connection with a name and get a URL of its own.

1. In Admin, open Settings › MCP and create a connection.

2. Give it a name — “Cursor agent”, “Content drafting”, whatever tells you what it is.

3. Copy the URL you get back and add it to your assistant.

4. Log in when prompted.

Reconnecting to that same URL reuses the same connection rather than making a new one.

Why bother naming them

A named connection has an identity in Admin. You see it in your connection list by name, how it connected, and when it was last used — so you can tell which assistant is which, spot one that has gone quiet, and revoke a single connection without disturbing the others.

With one shared URL, every assistant looks the same.

Some assistants ask for a connection name themselves while logging in, so you may be offered one either way.

Keep your URL private

Caution

An MCP URL identifies your connection. Treat it like a password — do not paste it into a shared document or a public channel.

Confirm it worked

Admin shows the connection as active. The better test is to ask the assistant something harmless:

Tell me what you can see in my Space. Do not change anything.

If it comes back with your real cubes, you are connected.

Start read-only

Make the first thing you ask a question, not an instruction. It confirms the connection and shows you how the assistant reads your Space before it has changed anything.

If it will not connect

• Login fails. Confirm you are signing in with the account that has access to the Space you expect.
• Connected but sees nothing. You may be on a different Space. Ask it which one it is looking at.
• It stopped working. Connections can expire or be revoked. Check the status in Settings › MCP and reconnect.

Next

Working safely with an agentWhat to let an agent change, and what to keep for yourself.