Configuration, consent and a Cloud MCP read

Distinguish client connection details, Account consent and a saved-file read.

A customer Cloud MCP connection brings together client configuration, Account consent and a read request. Each serves a different purpose.

Configuration, consent and a read request

  1. Client configuration

  2. Account consent

  3. Read request and access checks

Client configuration

Configure the remote endpoint https://mcp.altifigence.com/cloud-mcp with Streamable HTTP. These settings tell the client where to connect.

Account consent

During Account sign-in and OAuth consent, review the organization and requested Cloud read access. The connection uses the organization approved in that consent.

Verify a read

Use the tools listed for the current connection. Begin with the account identity and accessible projects, then choose a project for a saved-file read. A read request is checked against current authorization and project access.

For the full connection and first-read procedure, follow the guide below.

MCP connection and first read