Connecting to MCP

Check availability before connecting a client.

Hosted connections

Cloud MCP uses https://mcp.altifigence.com/cloud-mcp with Streamable HTTP and OAuth. See availability and client qualification before configuring a client.

  1. Add the exact endpoint in your client’s remote MCP connection settings.

  2. Complete Account sign-in and review the organization and requested Cloud permissions on the consent page. The client manages the OAuth credentials.

  3. Initialize the connection and refresh the client’s tool list. Only currently permitted Cloud tools appear.

  4. With read permission, read your identity and project list first. Use a returned project ID for project and file reads; file reads require a ready workspace.

  5. For project, file, settings or Git changes, request https://mcp.altifigence.com/cloud.write and complete fresh consent. Your organization must explicitly allow each tool. Read the current project and file revisions before changing saved files; inspect state after an uncertain mutation response before deciding whether to retry.

  6. For runtime lifecycle, terminal actions or jobs, request https://mcp.altifigence.com/cloud.execute permission and complete fresh consent. For a job, estimate the saved project’s RTL first. Review the returned offer and usage policy before authorizing submission, then follow the tool workflows. Availability depends on the service release and your organization’s runtime and tool policy.

  7. For personal AI connections, request only the needed AI scopes listed in account security, obtain organization tool approval and complete fresh consent. Use the returned secure setup URL so the user can enter a provider key directly in Cloud. Review the selected provider, model, context and possible charges before requesting an AI response.

New tool names require fresh consent, including new tools within an existing permission. Refreshing an old token does not add them. The console’s selected project is not an authorization grant. Changing the authorized organization requires a new consent. A stopped project is not started by a read request. Do not add account tokens, browser cookies, or AI-provider keys to the connection configuration.

If initialization or authorization fails, use troubleshooting. Do not fall back to posting protocol requests to a site root or another profile.

Installed software

If you are using a local MCP process, follow the instructions for your installed CLI version. See MCP overview for the difference between local and hosted connections.

Verify your first read

  1. Ask the client to read the connected Altifigence account and organization.

  2. List accessible projects and select a returned project ID.

  3. Read the selected project state. If a file read is unavailable, check the selected project, access and current storage/service status in Cloud. Starting a runtime is a separate execution action; ordinary saved-file access does not require a personal runtime startup.

  4. List files and choose one returned path. Read its complete content, following continuation offsets when necessary.

  5. Ask for a summary that includes the project, path and saved revision. Check it against Cloud before using the connection for larger work.

Example request: “List my Altifigence Cloud projects. Read the README in the project I select, then summarize its setup steps and identify the saved file you used.” This works within the published read scope and makes the target explicit.