Connection setup · Updated 4 November 2026

Connect Accounting Scalable to Codex CLI

Connect the terminal client Codex CLI through Streamable HTTP using deliberately configured read access. The native configuration references a private environment variable instead of writing a token into the configuration file.1

Prerequisite: Access enabled for Codex CLI is required. OpenAI expressly lists CLI access with the Plus plan; check whether your specific account is enabled. Separately billed API access is another possible method. A ChatGPT web plugin uses its own connection method.2

Client, data path and browser functionality

Platform
Terminal client, Linux here; the commands apply to Codex CLI. For other operating systems, configure the terminal and secure environment variable management appropriately.
Germany and account
Germany is listed as a country with OpenAI API access. This does not replace checking the specific account, plan or browser authorisation.
MCP and authentication
Streamable HTTP, Bearer token through bearer_token_env_var. Use the actual HTTPS MCP address taken from your instance.
Browser
The data connection does not include browser control. ELSTER requires a separately available and expressly authorised browser method.3

1. Provide personal agent access with read permission

In your Accounting Scalable instance, open user management, select the intended active agent and explicitly leave “Write access” disabled. This setting is crucial for read access: token rotation must not unintentionally enable write permissions. Access nevertheless covers all companies in the instance.

  1. Open the intended agent under /#/accounting/table_user; administrator/superuser permissions are required.
  2. Take the MCP address from the agent profile. The app endpoint is /mcp; it is not the website’s product knowledge server.
  3. Deliberately select “Change access token” only if a new access token is needed. It is displayed once and revokes all previous tokens for that agent.
  4. Store the token directly in the client’s access field or in a private process environment variable. Do not put it in URLs, HTML, screenshots, Git or analytics events.

2. Register the native URL/Bearer connection

Take the server address from the instance. The known public demo MCP address is https://demo-api.accountingscalable.de/mcp; it is a different data space and requires separately supplied read access. The ordinary browser demo login does not provide a personal agent token.

  1. Set the private process environment variable AS_MCP_TOKEN to your personally supplied token, without writing it into shell history or screenshots.
  2. Use the native configuration shown below with your actual server address. A placeholder is not a server address.
  3. Alternatively, use the documented native command: codex mcp add accounting_scalable --url "<MCP_ADRESSE_AUS_IHRER_INSTANZ>" --bearer-token-env-var AS_MCP_TOKEN.
  4. In a new Codex session, open /mcp and check tools/permissions. codex mcp list or get alone confirms only registration, not a successful accounting data retrieval.

3. Check with a task that makes no changes

A configured connection does not yet prove that the correct data has been retrieved. Check permissions, company and period against the actual server response.

  1. Read the current tool list and capabilities_get response in the client; the annual accounts functionality available through MCP is narrower than the full app assistant.
  2. Determine the company using companies_list and select the financial year using economic_years_search.
  3. Request a report with explicitly confirmed company_id and cut-off date.
  4. Compare the response’s identity, parameters, currency and retrieval status with your selection. The company active in the UI is not used automatically.

4. Narrow down common errors specifically

HTTP 401 may indicate a missing, revoked or incorrectly transmitted token. For 403, check the agent status and permissions. HTML instead of MCP or HTTP 404 suggests an incorrect address.

  1. Check the fixed Bearer header on every request without copying the token into error reports.
  2. Do not invent an OAuth login: the current app MCP does not offer this sign-in method.
  3. Stop if the company is missing or the period does not match; do not guess a substitute ID.
  4. A monthly VAT advance return request may not match a quarterly filing interval. Check the master data instead of concealing an error with zero values.

5. Revoke the connection and distinguish remaining tasks

Remove the connection in the client and deliberately disable the agent or rotate its token in the app. Rotation affects all previous tokens for that agent.

  1. Check whether the same agent access is still needed by other authorised workflows.
  2. Browser control and access to tax forms are authorised and checked separately. The MCP connection alone does not open an ELSTER form.
  3. For tax returns, clarify the required additional information and professional questions; deliberately stop before submission.
  4. Remove the local client connection with codex mcp remove accounting_scalable. codex mcp logout handles OAuth credentials; it does not revoke a fixed App bearer token. Revoke server access separately through the personal agent.

A first, read-only task

Replace the placeholders using the actual tool response. The result must identify the intended company and correct cut-off date. A saved server configuration alone is not a successful data retrieval.

Connect the appropriate workflow

When data access and additional browser access are both available and authorised, you can have confirmed values entered in the appropriate ELSTER form.

View compatibility and actual verification status →

Official client documentation

Guide updated on 4 November 2026. Check the account and client features available to you before setup.

Notes and requirements

  1. You check business transactions, results and professional decisions. The app enables independent ongoing bookkeeping and annual accounts; the specific MCP access has its own, potentially narrower scope.

  2. Agent access applies to all companies across the instance. Your chosen client processes the authorised data under its own terms; a cloud connector transmits data to its provider. Credentials belong only in the designated confidential client fields.

  3. MCP data access, browser control, tax review and actual transmission are separate steps. A form check does not replace substantive professional review. Signing in and deciding to submit remain your responsibility.