Claude Code and Cloud MCP

Distinguish client configuration, Cloud authorization and a successful saved-file read.

Cloud MCP uses the remote HTTP endpoint https://mcp.altifigence.com/cloud-mcp. A configured server, an authorized account and a successful tool read are separate checks. Availability depends on the client and your Cloud organization’s tool policy.

Check the client and endpoint

When the installed Claude Code CLI supports a remote HTTP MCP server, its configuration command has this form. Confirm the installed CLI’s help and intended configuration scope before using it.

claude mcp add --transport http altifigence https://mcp.altifigence.com/cloud-mcp

When the configured server is available in Claude Code’s /mcp interface, the client can offer account authorization. The account, organization and requested scopes belong to that authorization. The DDS settings page does not prove that this client completed it. A callback alone does not establish successful Cloud tool access.

Check connection availability in DDS

  1. Use QUOTA to open DDS settings and choose Developer access.

  2. Read the project selected in Overview and the requirement for account sign-in, organization consent and permission.

  3. Choose Open setup to open Developer tools. Read the offered setup information and Documentation link.

  4. Expand Details. Read MCP endpoint, Transport, Authentication and the permission labels. The displayed transport is Streamable HTTP.

The Details table is a reference to tool names and permission categories. The connection’s actual discovered tools and current grant determine access; the reference alone does not enable a tool.

Context, search & connections is a separate settings page for context, Web search and AI connections. These controls are not the Cloud MCP consent screen. Developer tools may show setup information without offering an external authorization session in this host.

When the connection exposes read tools

A connected Cloud account can expose identity, accessible projects and saved-file reads under cloud.read. A successful small read of a non-sensitive file from a project returned by that connection establishes more than server configuration alone. Project/file identity, pagination, chunk completion and versions define what was read. A denied tool remains unavailable without the required current organization policy and consent.

Keep staff DX separate

The staff DX endpoint ends in /dx-mcp. Its organization plugin and employee device-login flow do not configure customer Cloud access. The DX device-code flow must not be substituted for Cloud authorization, and staff scopes must not be mixed with cloud.* scopes.

If connection fails

If the client rejects a command option, use its installed help. A rejected callback, missing tool or denied read has a different cause from an unavailable DDS workspace. Keep the sanitized error and use MCP troubleshooting. Tokens, browser cookies and authorization codes do not belong in shared project configuration.

Related guides

Connection guide · Authentication · Tool reference · Troubleshooting