Connect Altifigence to ChatGPT

Install the published connection, review consent and verify a saved-file read with the five published read tools.

The read-only Altifigence connection exposes five operations: account identity, project listing, project details, file listing and file reading. Check the tools discovered for your connection and begin with a small saved file you may read.

Connect and review consent

  1. Open ChatGPT Plugins, find the available Altifigence listing and install/connect it. Workspace policy can restrict availability.

  2. Sign in to Altifigence through the authorization page opened by the client.

  3. Check the account, organization and exact requested tools before accepting consent.

  4. Return to a new ChatGPT Work conversation, type @ and select Altifigence if offered. Installation or a callback alone does not verify a file read.

Verify the first read

  1. Ask the connection for your identity and accessible projects.

  2. Select the intended project from the returned list, then request its details.

  3. List the saved files and choose a small non-sensitive source file.

  4. Ask to read that file and explain a specific part, such as its ports. Check the project and saved-file identity in the response.

  5. If the response is paginated or chunked, let the discovered tool schema guide the next request. Do not assume a partial result is the whole file.

Example request: “List my accessible projects. After I choose one, read its saved top.sv and explain the ports.” The tools read saved files, so save a current edit in DDS before asking about it.

Understand the permission boundary

The published five-tool profile does not edit files or run jobs. Server version and a client's published tool set are separate. Use the tools actually discovered for the connection; broader tools require separate availability, explicit organization approval and fresh consent. Reconnecting does not enable a disabled tool.

Troubleshooting

Problem

Action

Altifigence is not offered

Check installation and whether it is selected for the conversation.

Sign-in expired/revoked

Reconnect to the intended account and organization.

A project is missing

Check current membership; do not guess project IDs.

A tool is denied

Review current organization policy and consent for that exact tool.

The saved content is old

Save in DDS, list/read again and verify the current file identity.

Send support only the client/version, time and sanitized error. Do not include authorization codes, cookies, keys or proprietary project content.

Related guides

First MCP read · Authentication · Tools and availability · MCP troubleshooting