CloudShare MCP Server

Setting Up the CloudShare MCP Server Integration

The CloudShare MCP Server connects the AI client of your choice — Claude Code, Codex, Gemini, or any other MCP-compatible client — directly to your CloudShare account. Once connected, you can retrieve information and perform platform actions inside CloudShare directly from your AI client, using natural language instead of the CloudShare UI.

All actions performed through the MCP Server respect the permissions of the authenticated user — your connected AI client can only access and modify the resources you yourself have permission to access.

Available tools include:

• List Entities — environments, projects, blueprints, policies, regions, teams, instructors
• Create Environments — provision new environments from an existing blueprint, or from scratch
• Create & Manage Experiences — provision new training or sales experiences with full scheduling and access configuration, along with add/removing instructors/participants and sending invitations. 

The CloudShare MCP card appears By CloudShare in the Integration Hub, under the AI & Agent Integrations category.

Enabling MCP Server Access for Your Subscription (Account Managers)

Before anyone in your subscription can connect to the MCP Server, an Account Manager needs to turn it on at the subscription level.

1. Go to Subscription Details.
2. Locate the AI Integrations section.
3. Turn the MCP Server toggle ON.

Once enabled, every user in the subscription is allowed to generate their own MCP token by default (see Managing individual user access below to change this for specific users).

If the toggle is turned OFF, MCP access is blocked for the entire subscription — no user can generate or use a token, and existing tokens stop working, regardless of their individual permissions.

Note: If you open the CloudShare MCP card in the Integration Hub before enabling this toggle, you'll see a note explaining that the MCP Server needs to be turned on for your subscription, with a link to this setting. Other team members won't see this note, but their Setup tab will be unavailable until an Account Manager turns it on.

Connecting Your AI Client

Once MCP access is enabled for your subscription, any user can connect their own AI client.

1. Open the Integration Hub and scroll to the CloudShare MCP card.
2. Click More Details, then select the Setup tab in the card header.
3. Click Generate MCP Token.
   • This creates a personal token tied to your CloudShare user.
   • If you already have a token, this button becomes Regenerate MCP Token — regenerating invalidates your previous token, so any client already using it will need to be reconnected. You'll be asked to confirm before this happens.
4. In the Connector list below, find the AI client you use — Claude Desktop, Claude Code, Codex, Copilot, or Gemini —  click on it to expand and follow the connection instructions.
5. Using a different AI client? Click the copy icon next to the token above and follow your AI client’s instructions for connecting to a custom MCP server.

Keep your MCP token private — treat it like a password. If you believe it's been exposed, regenerate it immediately.

Out-of-the-Box Skills

In addition to the MCP tools, CloudShare provides ready-made skills that guide your AI client through common multi-step workflows. Instead of figuring out which tools to call and in what order, you describe what you want in plain language. The skill collects the required details, fills in sensible defaults, asks you to confirm, and then completes the action in your account.

Skills run through the MCP Server, so they follow the same rules as everything else: they can only access and change what your own CloudShare user is permitted to.

Available skills to download:

Using a skill:

1. Download the skill and add it to your AI client.
2. Make sure your AI client is connected to the CloudShare MCP Server (see Connecting Your AI Client).
3. Describe your goal in natural language. You don't need to name the skill. Your AI client selects the relevant one based on your request.
4. Review the summary of the details the skill proposes (project, blueprint, region, schedule, participants, and so on) and adjust anything you want to change.
5. Confirm. The skill creates the environment or experience and returns the link and the details you need to share.ֿ

Note: Skills create real environments and experiences in your account, so they may consume resources according to your subscription. Nothing is created until you confirm.

Managing Individual User Access

By default, once MCP Server access is enabled for a subscription, every user is allowed to generate a token. An Account Manager can control this individually for any user from the User Details page:

• Viewing another user's details, select Edit User Details under Actions, then use the Allow MCP Connection checkbox to enable/disable the MCP server.

Note: Unchecking this field immediately blocks the user from generating or using an MCP token — their MCP Token field and Setup tab are hidden, and any existing token stops working.

Managing Connected Users (Account Managers)

Account Managers can see and manage everyone in their subscription who has successfully connected an AI client to the MCP Server.

1. Open the CloudShare MCP card in the Integration Hub.
2. Select the Manage Users tab (visible to Account Managers only).

The grid lists every user who has completed setup and established a real connection — generating a token alone doesn't add a user to this list. 

For each user, you'll see:

Revoking a User's MCP Access

1. In the Manage Users grid, click Manage next to the user you want to revoke.
2. You'll be taken to that user's User Details page.
3. Uncheck Allow MCP Connection.

Note: The user's access is revoked immediately: their existing token stops working, and they can no longer generate a new one until an Account Manager re-enables their access. The user will see a message in the MCP card instructing them to contact their Account Manager to regain access.