Lastaaminen

Manage your MCP connection

Use your agent application's settings to manage a connection that has already been added. You can choose when the client uses Actualog, sign in again and remove its saved connection settings. These client actions have different effects from withdrawing the access permission recorded by Actualog.

Find your Actualog connection

Open your agent application's Settings and find MCP servers or its equivalent connection list. Select the Actualog entry. Check its server address, whether the entry is enabled and whether it requires sign-in.

Codex shares MCP configuration between its desktop, CLI and IDE clients on the same host. Changes to that shared configuration can affect those clients. In a Codex terminal, codex mcp list lists saved entries; the conversation's /mcp control shows its active servers. A saved entry alone does not prove that requests are currently being made. See the official OpenAI MCP instructions for client controls.

Pause, sign out or remove the entry

What you want Client action and effect
Pause Actualog use in this client Turn off the MCP entry. Reconnect the conversation if needed. The entry remains saved and you can enable it later. This does not withdraw your Actualog access permission.
Sign out in this client Use its MCP sign-out action. In the Codex CLI, codex mcp logout actualog removes stored OAuth credentials for an entry named actualog. This clears the client's saved sign-in; it does not establish that Actualog has revoked the server-side permission.
Remove the saved connection Delete the MCP entry in the client. You will need its connection settings to add it again. Removing configuration does not by itself prove that the Actualog permission was revoked.
Withdraw the permission held by Actualog This requires a separate Actualog permission-revocation action. A personal or company permission-management page is planned and is not available in the current pilot. Ask the team providing your integration how to withdraw your own permission under the current pilot procedure.

In Codex advanced configuration, enabled = false turns off the server entry without deleting it. The CLI's sign-out and removal controls are described in the official command reference.

Turning off one client does not establish that another client or computer has stopped using the same application permission. Request activity also does not imply a permanent online connection.

Reconnect or change account

  1. Enable the intended Actualog entry in your client.
  2. If the wrong account is signed in, sign out of that MCP entry first.
  3. Select Authenticate, or use the client's normal MCP sign-in command.
  4. Sign in to the intended Actualog account, complete required MFA and review the consent screen.
  5. Reconnect the conversation so it receives current Actualog tools and guidance.
  6. Ask the agent to confirm the current Actualog user and server and read one existing category without making changes.

The current pilot admits Application Admin using the supported local Codex setup. Access for other roles and broader client support are planned. Reconnecting cannot grant a role or operation you do not have.

Common problems after connection

  • You changed the server address: use the approved settings for the new environment and sign in there. Permission for one environment is not permission for another.
  • The client asks for sign-in again: its credentials may have been removed or its Actualog permission may no longer be valid. Use normal sign-in only if access is still authorized.
  • The tools or descriptions look old: reconnect the client and start a conversation using the refreshed connection.
  • Reading fails after successful sign-in: check that the entry is enabled, the network is reachable and the intended account was used. Report the exact error if it continues.
  • A change is refused while reads work: ask the agent to show the relevant refusal and current permission or data-state limits. Successful reads do not authorize every change.

For setup from the beginning, see Connect your agent to Actualog. For supported capabilities, see Actualog MCP.