![]()
Troubleshooting
Test browser login
If your agent reports a connection or OAuth metadata failure, use the shared test from this computer. It works without the source repository or saved credentials. You need PowerShell 7 and network access to this server.
Download the OAuth test helper. From the folder where you saved it, run:
pwsh -File ./Test-McpOAuth.ps1 -BaseUrl https://mcp.uniconta.com -CheckOnly pwsh -File ./Test-McpOAuth.ps1 -BaseUrl https://mcp.uniconta.com -CompanyId 133515
The first command checks metadata without login. If it succeeds, the second opens the login page. Enter your credentials there; the callback completes the test and shows its result. Keep the test process running until it finishes.
The example read is limited to three customer account/name rows in test company
133515. Use that example only if your login has access; otherwise supply an authorised
-CompanyId. If you do not know the id, stop after -CheckOnly and ask your operator.
This is a company id, not a customer account, and may differ from the company number.
The test revokes its own token afterwards and makes no ERP changes. It creates one
diagnostic OAuth registration, retained after successful login. It does not log
your configured MCP connection in.
The agent should show the precise failed step, rather than treating every failure as a bad password or an unavailable server. A local hosts-file entry applies to local requests; identify where the failing connection actually runs.
If something is wrong
- Claude Code finds an old or different connection
- Compare the name, exact endpoint and scope using
claude mcp listandclaude mcp get NAME. Local scope takes precedence over project, then user, only for the same name. The effective entry may hide other scope definitions; do not guess. Remove only a verified incorrect entry for this host or a same-host shadow preventing the intended connection, withclaude mcp remove NAME -s SCOPE. Keep other hosts, desktop extensions, plugins and managed settings. A working entry with another name should be reused. - OAuth metadata request fails
- Run the metadata check under Test browser login. Record the exact URI, failed step, HTTP status and test time. The unauthenticated MCP endpoint should return 401 with a Bearer metadata URL. A successful Basic read or health response does not prove that OAuth works.
- You only see this page
- Expected. It is informational, and it is what any browser gets. Your client
needs the
/mcpendpoint shown in the connection guide. - 401 Unauthorized
- Sign-in may be missing, or its token may have expired, been revoked or disappeared
after a server restart. A stale
Authorizationheader is another possibility. Check the endpoint/header and sign in from the client. For a stale Claude Code login, runclaude mcp logout NAMEandclaude mcp login NAMEonce, using the existing connection name; older versions use/mcpinteractively. - The browser ends on a
127.0.0.1address showing nothing - That is your client's own loopback callback. Check the client or test process for its completion result; a blank page alone does not prove success or failure. If the page cannot load, confirm that the listener is still running on the same computer where you opened the login link.
- Nothing connects at all
- This server is internal: it cannot be reached from outside the
company network, so a VPN connection is required from elsewhere, and a
cloud-hosted AI connector cannot reach it however good its OAuth support. Your
client has to run somewhere that resolves
mcp.uniconta.com. Test from that execution environment. Do not change hosts files or network settings automatically. DNS/timeout, TLS errors and an HTTP 4xx/5xx response are different failures; report the actual stage and status, or say no HTTP response was received.