Getting started

Claude Code

1. Open your terminal and add the server.

   claude mcp add --transport http cloudfactory https://mcp.cloudfactorygroup.com/mcp

2. Start claude, type /mcp, pick cloudfactory and choose Authenticate. Your browser opens the Cloud Factory login; sign in with your Partner Portal account and accept the consent screen.

3. Ask for one of your customers by name to confirm the connection.

4. Optional: to lock the connection to read-only, put the server in your settings with the scopes pinned. The connection then cannot be widened without changing the file.

   {
     "mcpServers": {
       "cloudfactory": {
         "type": "http",
         "url": "https://mcp.cloudfactorygroup.com/mcp",
         "oauth": {
           "scopes": "read:cloudfactory"
         }
       }
     }
   }

For more details, see the Claude Code MCP documentation.

Claude

1. In Claude (web or desktop) open Settings, Connectors, then Add custom connector. Team and Enterprise owners add it under Organization settings first; members then connect it individually.

2. Name it Cloud Factory and paste the server URL. Leave the Advanced OAuth fields empty.

   https://mcp.cloudfactorygroup.com/mcp

3. Click Add, then Connect. Sign in with your Cloud Factory Partner Portal account and accept the consent screen.

4. Enable the connector in a chat and ask for one of your customers by name.

For more details, see Get started with custom connectors using remote MCP.

ChatGPT

1. Open Settings, Plugins (called Connectors or Apps & Connectors in some workspaces), then Create or Add MCP server. Developer mode must be on for custom servers.

2. Paste the server URL. Keep the /mcp path; the host root alone does not work.

   https://mcp.cloudfactorygroup.com/mcp

3. Authentication: OAuth.

4. Switch OIDC enabled off before you connect.

5. Connect, sign in with your Cloud Factory Partner Portal account and accept the consent screen.

Why OIDC must be off: our identity provider does not issue OpenID scopes to third-party connectors yet. With OIDC on, ChatGPT asks for the user's e-mail after login, the request is refused, and ChatGPT reports that the account could not be connected. OIDC in ChatGPT only serves workspace domain restrictions and is not needed to use the server.

Codex

1. Add the server from the terminal. Codex shares the configuration with the desktop app and the IDE extension.

   codex mcp add cloudfactory --url https://mcp.cloudfactorygroup.com/mcp

2. Sign in. Codex reads its scopes from the login command, so pass them.

   codex mcp login cloudfactory --scopes "read:cloudfactory offline_access"

3. Your browser opens the Cloud Factory login; sign in and accept the consent screen. Then ask for one of your customers by name.

For more details, see the Codex MCP documentation.

VS Code

1. Open the Command Palette and run MCP: Add Server. Choose HTTP, paste the server URL, name it cloudfactory, and pick Global to keep it in your user profile or Workspace to keep it in the project.

   https://mcp.cloudfactorygroup.com/mcp

2. Or write it yourself. Run MCP: Open User Configuration for your profile, or create .vscode/mcp.json in the project, and add the server:

   {
     "servers": {
       "cloudfactory": {
         "type": "http",
         "url": "https://mcp.cloudfactorygroup.com/mcp"
       }
     }
   }

3. Start the server from the Start link above its entry in mcp.json, or from MCP: List Servers. VS Code asks to allow the server to authenticate and opens your browser. Sign in with your Cloud Factory Partner Portal account and accept the consent screen.

4. Open Copilot Chat in agent mode. The Cloud Factory tools appear in the tools picker. Ask for one of your customers by name to confirm the connection.

5. To disconnect, open the Accounts menu in the Activity Bar and sign out of the Cloud Factory entry, or run MCP: Reset Trust.

For more details, see the VS Code MCP servers documentation.

Hermes Agent

1. Add the server to ~/.hermes/config.yaml (or the profile's mcp_servers file) with OAuth enabled and the scopes pinned.

   mcp_servers:
     cloudfactory:
       url: "https://mcp.cloudfactorygroup.com/mcp"
       auth: oauth
       oauth:
         scope: "read:cloudfactory offline_access"

2. Start Hermes and use a Cloud Factory tool once. Hermes prints an authorization URL, opens your browser and waits for the callback on a local port. Sign in and accept the consent screen.

3. On a remote host, in a container or as a messaging bot the browser cannot reach that port. Use the device-code flow instead, or paste the final callback URL back at the prompt.

   hermes mcp login cloudfactory --flow device

Tokens are stored in ~/.hermes/mcp-tokens/cloudfactory.json and refreshed automatically. For more details, see the Hermes Agent MCP documentation.

Grok

1. Open grok.com/connectors, click New Connector, then Custom.

2. Paste the server URL.

   https://mcp.cloudfactorygroup.com/mcp

3. If Grok shows OAuth Credentials Required, put this in Scopes and leave the other fields as Grok fills them.

   read:cloudfactory offline_access

4. Sign in with your Cloud Factory Partner Portal account and accept the consent screen. Ask for one of your customers by name.

On Grok Business and Enterprise a team admin adds the connector first in the xAI console under Grok Business, Connectors.

For more details, see the Grok connectors documentation.

Grok Build

1. Add the server from the terminal.

   grok mcp add --transport http cloudfactory https://mcp.cloudfactorygroup.com/mcp

2. Pin the scopes in ~/.grok/config.toml. Grok Build uses this list exactly, so include offline_access.

   [mcp_servers.cloudfactory]
   url = "https://mcp.cloudfactorygroup.com/mcp"
   oauth_scopes = ["read:cloudfactory", "offline_access"]

3. Start grok, type /mcps, select cloudfactory and press i to authenticate. Sign in and accept the consent screen.

Tokens are stored in ~/.grok/mcp_credentials.json. For more details, see the Grok Build MCP documentation.

OpenClaw

1. Add the server with OAuth and the scopes pinned.

   openclaw mcp add cloudfactory --url https://mcp.cloudfactorygroup.com/mcp --transport streamable-http --auth oauth --oauth-scope "read:cloudfactory offline_access"

2. Sign in. OpenClaw prints the authorization URL, opens your browser and waits for the callback on port 8989.

   openclaw mcp login cloudfactory

3. On a remote host the browser cannot reach that port. Copy the code value from the redirect URL in the browser and pass it.

   openclaw mcp login cloudfactory --code <code>

4. Check the connection.

   openclaw mcp status --verbose

For more details, see the OpenClaw MCP documentation.

Gemini CLI

1. Add the server to ~/.gemini/settings.json (or .gemini/settings.json in the project) with the scopes pinned. Use httpUrl; url is for the older SSE transport.

   {
     "mcpServers": {
       "cloudfactory": {
         "httpUrl": "https://mcp.cloudfactorygroup.com/mcp",
         "oauth": {
           "scopes": ["read:cloudfactory", "offline_access"]
         }
       }
     }
   }

2. Start gemini and run this command. Sign in and accept the consent screen.

   /mcp auth cloudfactory

3. Ask for one of your customers by name.

For more details, see the Gemini CLI MCP documentation.

Zed

1. Add the server to your Zed settings.

   {
     "context_servers": {
       "cloudfactory": {
         "url": "https://mcp.cloudfactorygroup.com/mcp"
       }
     }
   }

2. Zed asks you to sign in the first time the agent uses the server. Sign in and accept the consent screen. Zed reads the scopes from the server; there is nothing to set.

For more details, see the Zed MCP documentation.

GitHub Copilot CLI

1. Add the server.

   copilot mcp add --transport http cloudfactory https://mcp.cloudfactorygroup.com/mcp

2. Start copilot and run /mcp auth if it does not ask you to sign in by itself. On a machine without a browser it offers a device code. Sign in and accept the consent screen.

For more details, see Add MCP servers to GitHub Copilot CLI.

Microsoft Copilot Studio

Coming soon. A certified Cloud Factory listing for Copilot Studio and Microsoft 365 Copilot is in preparation. Until it is available, contact [email protected] if you want to connect from Copilot Studio.

For how MCP servers work in Copilot Studio, see Extend your agent with Model Context Protocol.