積載

Connect your agent to Actualog

Connect your agent application to Actualog so it can read permitted information and help you work with it. You set up the connection in your agent application's settings, then sign in to Actualog and approve the requested access.

Before you start

You need an Actualog account, a supported agent application and the MCP server address for the Actualog environment you want to use. Use the address and client connection settings supplied for that environment. The website address alone does not establish that MCP is available there.

Current availability: the pilot supports the prepared local Codex client and Application Admin accounts. Access for other roles is planned. Company membership alone does not currently enable access. Support for Work, hosted clients and other agent applications has not been established by this pilot.

The current pilot needs prepared Codex connection settings as well as the MCP server address. Use the settings supplied for your client; adding a URL alone does not replace them. If those settings have not been supplied, request the supported client setup from the team providing your Actualog integration.

Add Actualog in your agent application

  1. Open your agent application's Settings and find MCP servers or its equivalent connection list.
  2. If Actualog is already listed, select that entry and check that it points to the environment you intend to use. Otherwise, select Add server.
  3. Enter a recognizable name, such as Actualog. Choose Streamable HTTP and paste the supplied MCP server address. Keep the supplied pilot client settings.
  4. Save the entry and restart or reconnect the client if it asks you to do so.
  5. Select Authenticate or the client's sign-in action for Actualog.

In the Codex IDE extension, open the gear menu and select MCP servers. In a Codex terminal with an already configured entry named actualog, codex mcp login actualog starts the same sign-in step. Menu names can vary by client version. The official OpenAI MCP instructions describe the supported client controls.

Sign in and allow access

  1. In the browser window opened by your agent, sign in to the intended Actualog account.
  2. Complete any required multi-factor authentication.
  3. Read the consent screen. Check the Actualog server, the agent application and the requested access. Approve read access for a read-only task; additional change permissions need their own authorization.
  4. Choose Allow to continue, or Decline to cancel.
  5. Return to your agent application and wait for authentication to finish.

Keep the client running while the browser returns the sign-in result to it. In the current local pilot, that return happens on the computer running the agent application.

Check that reading works

Start or reconnect a conversation that can use the Actualog connection. Ask:

Confirm which Actualog user and MCP server this connection uses. Find one existing category and show its name and description. Do not change any data.

The agent should confirm the current connection context and read the category through Actualog. A successful login message or a visible server entry alone is not enough. If the client shows tool activity, confirm that the answer used Actualog tools rather than a remembered answer.

If connection fails

  • Server cannot be reached: check the supplied MCP address, your network and the selected environment. Report the error to the team providing the integration if it persists.
  • Sign-in is denied: check that you used the intended account and completed any required MFA. The current pilot only admits Application Admin; changing client settings cannot add eligibility for another role.
  • Callback or client error: keep the agent application open and use its supplied pilot settings. Ask the integration team to check the client setup rather than inventing a callback address or port.
  • No Actualog tools or an older tool list: enable the connection in your agent and reconnect it. If reading still fails, provide the error and the server address to the integration team.
  • Read succeeds but a change is refused: the connection does not grant every operation. The requested action still needs the appropriate permission and Actualog's normal checks.

You can now ask the agent to inspect and discuss information it can read. Discussing a change does not authorize applying it. For the supported capabilities and limits, see Actualog MCP.