Skip to main content
Glama
poweroffice-mcp

poweroffice-mcp

PowerOffice MCP for Codex

A local MCP server for secure access from Codex to the PowerOffice Go API v2 with read-only and explicitly confirmed write operations. The server works with the DEMO API, uses OAuth 2.0 Client Credentials, and provides small, explicitly limited tools instead of a generic HTTP proxy.

What is already available

  • poweroffice_configuration_status — checks whether configuration exists without exposing key values.

  • poweroffice_connection_info — checks the connection and returns available integrations/privileges.

  • poweroffice_search_customers — searches customers with filters and pagination.

  • poweroffice_get_customer — gets a single customer by numeric ID.

  • poweroffice_list_general_ledger_accounts — reads the chart of accounts.

  • poweroffice_list_account_transactions — reads transactions for a required date range.

  • poweroffice_create_customer — creates a customer after confirm=true.

  • poweroffice_update_customer — applies an allowed JSON Patch to a customer after confirm=true.

  • poweroffice_create_general_ledger_account — creates an account after confirm=true.

  • poweroffice_update_general_ledger_account — applies an allowed JSON Patch to an account after confirm=true.

Read tools remain read-only. Write tools modify data only with an explicit confirm=true; deleting, posting, and sending documents are not part of this stage.

Related MCP server: dooray-mcp-link

Requirements

  • Node.js 22 or newer

  • pnpm 11

  • PowerOffice application key, client key, and subscription key

  • the access roles needed for the endpoints being called

Installation

pnpm install
cp .env.example .env.local
pnpm build
pnpm test

Fill in .env.local locally:

PO_ENV=demo
PO_APPLICATION_KEY=...
PO_CLIENT_KEY=...
PO_SUBSCRIPTION_KEY=...
PO_USER_AGENT=poweroffice-mcp/0.1 your-email@example.com

.env.local is excluded from Git. Do not send keys in chat and do not add them to .codex/config.toml.

Connecting to Codex

The project file .codex/config.toml already launches the built dist/index.js via STDIO. It reads .env.local if the file exists, and can also receive the listed variables from the Codex process environment.

After pnpm build, restart the Codex task for this project. Start by calling poweroffice_configuration_status, then poweroffice_connection_info.

Local development

pnpm dev
pnpm typecheck
pnpm test
pnpm build
pnpm smoke

The server writes only MCP messages to stdout; startup errors go to stderr. Tokens are cached with a margin before expiration; on 401 one token refresh is performed, and on 429 up to two retries with a delay of at least one second for read requests. Write requests are not retried automatically to avoid duplicates. The overall request rate is limited by the PO_MAX_REQUESTS_PER_SECOND value and cannot exceed 10.

Environment variables

Variable

Required

Default value

PO_ENV

no

demo

PO_APPLICATION_KEY

yes

—

PO_CLIENT_KEY

yes

—

PO_SUBSCRIPTION_KEY

yes

—

PO_USER_AGENT

no

poweroffice-mcp/0.1

PO_REQUEST_TIMEOUT_MS

no

30000

PO_MAX_REQUESTS_PER_SECOND

no

10

For production, switch PO_ENV=production; the token and API URLs are selected by code, not entered by the user.

MVP boundaries

  • Only the PowerOffice API v2 and the STDIO transport.

  • No webhooks, automatic paging through all pages, or operations for deleting, posting, and sending documents.

  • Write tools are limited to Customers and GeneralLedgerAccounts and require confirm=true.

  • The Fields field can be overridden, but by default the server requests compact data sets.

  • The next page is always requested explicitly via pageNumber; the X-Pagination header metadata is returned together with the result.

Documentation: PowerOffice Developer Portal, MCP in Codex.

Available Tools

10 tools
poweroffice_configuration_statusPowerOffice configuration statusA
Read-onlyIdempotent

Check whether the PowerOffice MCP process has the required environment variables. Does not reveal credential values and does not call PowerOffice.

Inputs: no named parameters. Returns: configured, environment, missingVariables

poweroffice_connection_infoPowerOffice connection and privilegesA
Read-onlyIdempotent

Call GET /ClientIntegrationInformation to verify authentication and return the client subscriptions and API privileges granted to the configured integration.

Inputs: no named parameters. Returns: status, apiBaseUrl, environment, integration

poweroffice_create_customerCreate a PowerOffice customerA

Create one customer with POST /Customers. This writes to the configured PowerOffice client. Set confirm=true only after the user has explicitly approved the exact customer data.

Inputs: confirm (required), customer (required). Returns: resource

poweroffice_create_general_ledger_accountCreate a PowerOffice general ledger accountA

Create one general ledger account with POST /GeneralLedgerAccounts. VatCode or VatCodeId is required. Set confirm=true only after the user has explicitly approved the exact account data.

Inputs: account (required), confirm (required). Returns: resource

poweroffice_get_customerGet a PowerOffice customerA
Read-onlyIdempotent

Read one customer by PowerOffice numeric ID from GET /Customers/{id}. Returns a compact field set unless Fields is supplied.

Inputs: id (required), fields. Returns: customer

poweroffice_list_account_transactionsList PowerOffice account transactionsA
Read-onlyIdempotent

Read posted account transactions from GET /AccountTransactions for an inclusive date range. Use filters and small pages to keep accounting queries narrow.

Inputs: toDate (required), fromDate (required), fields, orderBy, +14 more. Returns: items, pagination

poweroffice_list_general_ledger_accountsList PowerOffice general ledger accountsA
Read-onlyIdempotent

Read a paginated list from GET /GeneralLedgerAccounts. Supports account ranges such as 1000-1999,2500,3000-.

Inputs: fields, orderBy, pageSize, accountNos, +4 more. Returns: items, pagination

poweroffice_search_customersSearch PowerOffice customersA
Read-onlyIdempotent

Read a paginated list from GET /Customers. Filters that accept multiple values use PowerOffice comma-separated syntax. Returns a compact field set unless Fields is supplied.

Inputs: fields, orderBy, pageSize, pageNumber, +10 more. Returns: items, pagination

poweroffice_update_customerUpdate a PowerOffice customerA
DestructiveIdempotent

Update one customer with JSON Patch at PATCH /Customers/{id}. Only mutable CustomerPatchDto paths are accepted. Set confirm=true only after the user has explicitly approved the exact changes.

Inputs: id (required), patch (required), confirm (required). Returns: resource

poweroffice_update_general_ledger_accountUpdate a PowerOffice general ledger accountA
DestructiveIdempotent

Update one general ledger account with JSON Patch at PATCH /GeneralLedgerAccounts/{id}. Only mutable account paths are accepted. Set confirm=true only after the user has explicitly approved the exact changes.

Inputs: id (required), patch (required), confirm (required). Returns: resource

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: connection info, configuration status, customer CRUD/search, general ledger account CRUD/list, and account transactions. Even the similar list/search/get operations are clearly separated by resource type and described filters.

    Naming Consistency4/5

    Tool names consistently use the poweroffice_ prefix and mostly follow a verb_noun pattern such as create_customer, update_customer, list_account_transactions. The two status/info tools break the pattern slightly, but the overall style is uniform and predictable.

    Tool Count5/5

    Ten tools is a well-scoped size for a PowerOffice MCP server covering customers, general ledger accounts, transactions, and connection diagnostics. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    The server covers the main customer and general ledger account workflows including create, update, and read operations, plus transaction listing. Minor gaps exist such as no single-account fetch for general ledger accounts and no delete operations, but these are not critical for common integration workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Codex to access Feishu knowledge bases and authorized shared cloud drives, allowing listing, searching, and reading wikis, documents, spreadsheets, bitable, and files, with scoped and approval-gated create and edit capabilities.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to access Saxo Bank portfolio data, account balances, positions, orders, transactions, and market data such as instruments, quotes, and charts. It is read-only by default, with trading tools available only when explicitly enabled.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and write accounting data in PowerOffice Go, including bookkeeping, sales, purchases, payroll, time tracking, and read-only bank access, with support for multiple companies and strict isolation.
      MIT