Troubleshooting

New tools do not appear

Some Claude and Codex versions or sessions keep an older tool list after the server changes. In testing, signing in again or opening a new chat alone did not always reload that list.

1. Use your application's MCP Refresh or reconnect action if it provides one.
2. Fully quit and reopen the application, then start a new conversation with LogDrop enabled. Closing only the chat or window may leave the application running.
3. For CLI sessions, exit and start a new session.
4. If the tool requires a new permission, complete authorization again. Restarting cannot grant a permission you did not select.

Refresh behavior depends on the application and version. In Antigravity, refresh the MCP server list after configuration changes. A tool list that looks stale does not by itself mean your LogDrop connection was revoked.

A tool says a permission is missing

Read the tool's error message for the missing permission and suggested next step. Start LogDrop authentication again, select that permission and the needed project, and complete browser authorization. If the client still uses an old connection or tool list, fully quit and reopen it.

If you intentionally do not want to grant that permission, leave it off and ask the assistant to stay within its current access. Reconnecting does not override your panel role.

Sign-in completed but tools still fail

Confirm that you authorized the intended project and used the intended LogDrop account. Refresh or restart the AI application. If needed, remove its old LogDrop server configuration, add it again from Connect MCP, and authorize a replacement connection. Revoke unused old grants in the panel after identifying them.

For Codex CLI, run:

codex mcp login logdrop

If you already have a server entry at the correct URL, adding it again is not a substitute for signing in.

Claude opens customization but does not add LogDrop

The Connect in Claude link opens a web setup page; it does not approve or install the connector silently. Check the selected Claude account and organization, then open the panel link again after signing in.

If custom connectors are disabled for your organization, an authorized owner or administrator must make the connector available first. Your personal LogDrop sign-in cannot remove Claude's organization restrictions. See Claude setup.

VS Code and Copilot setup issues

Some VS Code Copilot/AgentHost setups may show Migrations after adding a server. The migration can move a server entry from VS Code's MCP configuration into a Copilot-owned configuration. These are different clients and configuration locations; a successful migration message does not prove that the new client authenticated successfully.

If LogDrop disappears from the MCP list or sign-in does nothing:

1. Check whether you are using standard Copilot Chat in VS Code, a Copilot CLI/AgentHost session, or the standalone CLI.
2. Open that client's MCP server list and check that LogDrop is configured there.
3. Use the matching setup method in Connect your AI application, then authenticate.
4. Restart the affected client if it reports that a login is already in progress but no browser appears.
5. If that client still cannot connect, use another supported client such as Cursor, Codex, or Claude while investigating its error logs.

An upstream Copilot issue describes AgentHost authentication discovery failures for servers whose OAuth issuer has a path component. LogDrop uses a root issuer, so that report is related context, not a confirmed explanation for every LogDrop/VS Code connection problem. Compatibility can vary by version.

The browser does not open Cursor or VS Code

The install buttons ask the browser to open a locally installed application. Check that the application is installed and review the browser's open-application prompt. If the handoff does not work, use Manual setup in the LogDrop connection dialog with the public server URL:

https://mcp.logdrop.io/mcp

A panel review link does not complete an action

Sign in to the LogDrop panel and check access to the linked project. Review the prepared form and finish the action there. A prepared push is not sent simply by generating or opening its link, and a journey draft is not published by creating it.

If a prepared link has expired or the underlying draft no longer exists, ask the assistant to prepare it again and review the new values.

The SDK has not sent data yet

SDK onboarding tools can report that no SDK data has arrived. Run the app with the integration in place and generate an event or request. Ask the assistant to check again after data has had time to arrive. A waiting status is not a reason to make an unlimited stream of polling calls.

Sharing an issue with support

Include the AI application and version, the affected tool or action, the time, and the error code or message. You can include a screenshot after removing tokens, credentials, private user data, and unrelated browser content. Do not share access tokens or passwords.