Uniconta MCP

Connect with your client

Choose the connection route for your AI client. Claude Code guidance was checked against the official documentation and local CLI 2.1.294 on 27 October 2026. Client availability and organisation policies may vary.

Start here

The MCP endpoint is https://mcp.uniconta.com/mcp. Add it in your client's MCP settings, then sign in with your own Uniconta account in the browser. Entering the URL in a conversation does not configure a connection.

The important question is where the MCP request actually runs. A desktop app may use a cloud connector; a local development client may make the request directly from your computer. A local hosts-file entry or VPN helps only a process using that computer's network.

Your Uniconta permissions and the server's allowed-company configuration both apply. Separate OAuth logins have independent company selections and temporary approvals. Always state the intended company when asking for accounting data. Read-only use and ERP writes must be tested separately.

Client overview
Client and connectionPrivate network or VPNPublic HTTPSSetup route
Codex with a local MCP connectionPossible when its execution host can reach the serverPossibleAdd the HTTP server and complete browser sign-in
Claude Code with direct HTTP MCPPossible when its execution host can reach the serverPossibleAdd an HTTP server, then authenticate using the client's MCP controls
Claude web or a remote connector in desktop/CoworkThe user's local network alone is insufficientRequires reachability from the connector serviceAdd a custom connector, subject to organisation policy
ChatGPT custom remote MCP connectionA browser hosts-file entry alone is insufficientRequires reachability from the serviceAdd a custom MCP server using OAuth, subject to workspace policy
GitHub Copilot in VS CodePossible when the configured execution environment can reach itPossibleConfigure an HTTP MCP server and authenticate
Microsoft 365 Copilot through Copilot StudioRequires a supported network route from the Microsoft environmentPossible, subject to authentication compatibilityConnect an agent to the MCP server
Teams through the same agentSame network requirements as the Copilot Studio agentPossible after agent setupPublish the agent to the organisation's chosen channel

These are setup routes, not a claim that every client has passed our complete compatibility test. The earlier Danish assessment records reported success with local Codex and Claude Code; other clients still require verification in the intended environment. Local MCP execution also does not mean the language model or its processing of tool results runs locally.

Codex

If the connection is already configured, use its existing name and sign in:

codex mcp login uniconta --oauth-client-registration dcr

Only if it does not exist, add it first:

codex mcp add uniconta --url https://mcp.uniconta.com/mcp

The name uniconta is an example: keep the existing name if yours differs. Older CLI versions may only support codex mcp login uniconta; check the installed command's help if the DCR option is unknown. Finish sign-in on the Uniconta browser page and return to the client. Reload the connection if its tools are not yet available. Do not replace working settings or paste credentials into the conversation.

Source: Codex MCP configuration and OAuth.

Claude Code

For a direct local HTTP connection, first check claude --version and claude mcp --help. The CLI on the tester's machine decides which commands are available. The current CLI supports login and logout; older versions can authenticate through /mcp inside Claude Code.

  1. Check this server's /health from the environment where Claude Code actually runs. On DNS/network failure, stop and ask the tester to connect to the company network/VPN. Do not edit hosts or network settings. If the server responds with an HTTP or TLS error, report the actual error; do not automatically call it a VPN problem.
  2. Run claude mcp list and inspect relevant entries using claude mcp get NAME. Inspect names, exact URLs and scopes without printing Authorization headers or other secrets. Reuse a correct HTTP user-scope entry, including its existing name. uniconta-mcp below is only the default name for a new entry.
  3. Only if no correct user-scope entry exists, add the connection below, without a configured Authorization/Basic header. If that name is used for another host, leave that entry alone and choose an unused name.
claude mcp add --transport http --scope user uniconta-mcp https://mcp.uniconta.com/mcp
claude mcp login uniconta-mcp

Use the chosen existing/new name consistently in login, logout and status commands. The tester enters their own Uniconta username/password in the browser. Never ask an agent to enter, obtain or save that password. Never paste tokens or callback URLs into chat. If an SSH/headless login requires a callback paste, the tester does it directly in their own terminal, not through the conversation.

Confirm Connected with claude mcp get NAME. Start a new Claude Code session, check that its tools are available, and first select the intended company, for example switch to company COMPANY_NUMBER. Connected status alone does not prove company rights.

Existing entries and scope conflicts

For the same server name, local scope overrides project scope, then user scope. Different names do not shadow each other. list/get can show the effective definition without revealing every lower-precedence definition. Inspect the relevant scopes safely or stop if uncertain; do not guess a scope or try an unsupported get --scope flag.

Remove only a verified incorrect definition pointing to this exact server host, or a verified same-host shadow that prevents the intended user connection from working:

claude mcp remove NAME -s SCOPE

An incorrect entry may have the wrong URL (the exact endpoint must end in /mcp) or a configured Authorization/Basic header. Preserve entries pointing to other hosts, desktop extensions, plugins and managed settings. A working entry under another name should be reused, not duplicated or renamed. User scope works across project directories; local scope is private to the project where it was added.

For a stale OAuth login, use claude mcp logout NAME, then retry claude mcp login NAME once. If these commands are unavailable, use /mcp interactively. A server restart or expired/revoked token can also require fresh login. Do not delete a correct connection just because a token has expired.

The front page's Connecting with Claude Code section includes a copyable setup request for an agent. Its Test browser login helper is a separate diagnostic: it does not authenticate the configured Claude Code connection. Before any diagnostic data read, obtain an authorised company id; 133515 is only a dummy-company example, not a company every tester can access. Company ids may differ from company numbers. For a different deployment, preserve the exact origin/endpoint shown on its front page.

Source: Claude Code HTTP MCP and authentication.

Claude web, desktop and Cowork remote connectors

A remote connector must reach the server from the service running it. Installing the desktop application or changing your computer's hosts file does not by itself give that remote service access to the private network. Ask your organisation administrator to enable the appropriate custom connector and check its OAuth flow.

Source: Claude custom remote connectors.

ChatGPT

Add a custom MCP server with OAuth through the controls available in your workspace. Organisation approval may be required. Verify the connection's execution path: a cloud connection needs a supported route to the server; your browser's local hosts entry is not such a route. A separately configured local Codex connection is a different connection.

OpenAI also documents a Secure MCP Tunnel route for private servers. It requires its own configuration and authentication compatibility assessment; it is not an automatic fallback enabled by this server. A public directory listing is separate from configuring a custom connection.

Sources: Custom MCP server setup and Secure MCP Tunnel.

GitHub Copilot in VS Code

Use VS Code's MCP server setup to add an HTTP server with the endpoint above, authenticate and enable the required tools in the agent. The organisation's policy must permit it. Remote development and containers may have a different network route from your desktop.

Verify the actual OAuth callback before marking this client as supported. The server permits loopback HTTP callbacks by default; another callback origin must match the server's redirect policy. Do not broaden that policy simply to bypass an unexplained login failure.

Sources: VS Code MCP setup and OAuth callback guidance.

Microsoft 365 Copilot and Teams

Create a Copilot Studio agent and connect it to the existing MCP server. Test the network route, OAuth registration and callbacks in that Microsoft environment. Successful login alone does not prove that the client supports our write-approval protocol.

The same agent can be published to Teams and Microsoft 365 where the organisation permits it. An internal organisational release is separate from public marketplace distribution. Microsoft 365 Copilot, GitHub Copilot and other products named Copilot are separate clients with separate setup and capabilities.

Sources: Connect a Copilot Studio agent to MCP and Publish an agent to Teams and Microsoft 365.

Diagnose a connection

Use the front page's Test browser login instructions and diagnostic helper. The helper checks OAuth discovery, lets you enter your credentials in your own browser, reads at most three customer account/name rows in an authorised company and revokes its own test token. Company 133515 is only an example for users with access; supply the authorised -CompanyId explicitly. If the id is unknown, stop after -CheckOnly and ask the tester/operator before reading data. Keep the helper running until it finishes. This is a separate diagnostic: it does not sign the configured client in for continued use.

Report where the failure occurred: network, discovery, client registration, browser sign-in, callback, token exchange or MCP read. Include the safe error and HTTP status if there was an HTTP response; say no HTTP response for DNS/TLS/network failure. Omit query strings from reported URIs. Do not paste passwords, tokens or callback codes into chat. A failed data read is not automatically an OAuth metadata failure.

A connection test must not change server configuration, ERP data or company access. Test with your own user; do not share another tester's login or token. The number 133515 is a company id, not a customer account.

Reads, approvals and writes

The server supports reads with MCP revision 2025-11-25. ERP writes require 2026-07-28 or later, Multi-Round Trip Requests (MRTR) and advertised form elicitation. Older elicitation or URL-only approval support does not establish compatibility with this write workflow. Record the exact client version and negotiated capabilities when testing.

Broader historical reads may request approval. Chat approval through confirm_read is available only when the server enables it; otherwise a compatible approval form is required. The front page shows the active setting. Approval belongs to the current login: after signing in again, request a new preview and approval. Never bypass an approval by claiming that the user already agreed elsewhere.

HTTP Basic authentication is disabled by default; use browser OAuth. If an operator explicitly enables Basic for compatibility diagnostics, it creates a fresh login for each request and cannot carry temporary approvals between separate requests. Use OAuth or the stdio host for workflows that need those approvals. Durable write status can still be checked by the same authorised user after signing in again.

Start testing with an explicitly selected permitted company and a small read. Confirm reconnect behaviour and company isolation before testing broader history. Test ERP writes only with explicit authorisation and a client capable of displaying the required human approval.

See 20 questions to try, version history and the front page.

The endpoint

https://mcp.uniconta.com/mcp

Point your client at that, not at mcp.uniconta.com on its own. A client aimed at the host lands on this page and reports that it found no server.

Connect with Codex

In your client's MCP settings, use the endpoint above and choose sign-in for the existing Uniconta connection. Enter your own Uniconta username and password in the browser page it opens.

If you use the Codex CLI, log in to the server name already configured in your client. This example uses uniconta:

codex mcp login uniconta --oauth-client-registration dcr

If your CLI does not recognise --oauth-client-registration, use codex mcp login uniconta. After login, check that the tools appear in the chat where you want to test; reconnect or reload the client if needed.

Adding a new Codex connection

Only add this if the server is not already configured under another name:

codex mcp add uniconta --url https://mcp.uniconta.com/mcp

Then run the login command above. Keep existing client settings and credential sources.

Connecting with Claude Code

You do not sign in from this page. Sign-in starts in your client, which opens a browser for you.

First run claude mcp list and inspect the relevant entry with claude mcp get NAME. Reuse an existing correct user-scope connection, including its name. Do not display Authorization headers or other stored secrets.

Only if it is missing, add an HTTP connection in user scope. The example name is uniconta-mcp; substitute your existing name in login and status commands. If that name already belongs to another host, leave it alone and choose an unused name:

claude mcp add --transport http --scope user uniconta-mcp https://mcp.uniconta.com/mcp
claude mcp login uniconta-mcp

Without --scope user, the connection is only available in the directory where it was added. Use --scope user for access from other directories; sign in with the command above or via /mcp in Claude Code.

Check claude mcp --help: if your version does not offer login/logout, open /mcp inside Claude Code and authenticate there. Enter your password only in your own browser; never paste a password, token or callback link into chat.

Add the endpoint with no authorization header, then sign in once with your normal Uniconta username and password. Your client receives an access token, never your password. The token reaches only this server, and only as the Uniconta user who signed in.

Check claude mcp get NAME for Connected. Start a new Claude Code session, confirm that its tools are available and first select your intended company, for example switch to company COMPANY_NUMBER.

Copy a setup request for your Claude Code agent

Just trying it out?

You can test this server without keeping it. Nothing here needs to stay in your setup:

claude mcp add --transport http --scope local uniconta-trial https://mcp.uniconta.com/mcp
claude mcp login uniconta-trial
# ... try it ...
claude mcp logout uniconta-trial
claude mcp remove uniconta-trial --scope local

This example uses a separate uniconta-trial name and --scope local: the connection is only available in the directory where it was added. If your client can scope a server to one session or one project rather than to your account, prefer that. Removing the connection does not guarantee that its server-side token is revoked. Use the client's logout/revocation feature if available; otherwise the token may remain valid until expiry or server restart. Revocation applies only to that login and does not undo ERP changes.

If your client cannot do the browser sign-in

HTTP Basic is disabled on this server. Clients using Basic headers must reconnect with OAuth. Clients configured before this server had a sign-in page send an HTTP Basic header instead, which works when enabled by the server. Prefer the sign-in flow where you can: with Basic, your password travels on every request rather than once.

Technical details: available tools

The 33 tools you should see

Read from this build's own tool surface, so it cannot fall out of date. If your client lists these, you are connected.

  • confirm_read
  • create_customer
  • create_quick_invoice
  • describe_entity
  • get_account_activity
  • get_accounting_context
  • get_bank_reconciliation
  • get_budget_vs_actual
  • get_cash_forecast
  • get_current_company
  • get_customer_statement
  • get_financial_reporting_context
  • get_financial_statement
  • get_journal
  • get_operation_status
  • get_payables_aging
  • get_receivables_aging
  • get_sales_order
  • get_trial_balance
  • invoice_order
  • list_companies
  • list_entities
  • list_journals
  • list_open_customer_items
  • list_open_supplier_items
  • list_sales_orders
  • list_worst_payers
  • lookup_cvr
  • query_entity
  • review_period
  • suggest_tool
  • switch_company
  • update_customer