poweroffice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PO_ENV | No | Environment for PowerOffice API: 'demo' or 'production'. Defaults to 'demo'. | demo |
| PO_CLIENT_KEY | Yes | PowerOffice client key. | |
| PO_USER_AGENT | No | User agent string for API requests. Defaults to 'poweroffice-mcp/0.1'. | poweroffice-mcp/0.1 |
| PO_APPLICATION_KEY | Yes | PowerOffice application key. | |
| PO_SUBSCRIPTION_KEY | Yes | PowerOffice subscription key. | |
| PO_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds. Defaults to '30000'. | 30000 |
| PO_MAX_REQUESTS_PER_SECOND | No | Maximum requests per second, cannot exceed 10. Defaults to '10'. | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| poweroffice_configuration_statusA | Check whether the PowerOffice MCP process has the required environment variables. Does not reveal credential values and does not call PowerOffice. |
| poweroffice_create_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. |
| poweroffice_update_customerA | 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. |
| poweroffice_create_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. |
| poweroffice_update_general_ledger_accountA | 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. |
| poweroffice_connection_infoA | Call GET /ClientIntegrationInformation to verify authentication and return the client subscriptions and API privileges granted to the configured integration. |
| poweroffice_search_customersA | 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. |
| poweroffice_get_customerA | Read one customer by PowerOffice numeric ID from GET /Customers/{id}. Returns a compact field set unless Fields is supplied. |
| poweroffice_list_general_ledger_accountsA | Read a paginated list from GET /GeneralLedgerAccounts. Supports account ranges such as 1000-1999,2500,3000-. |
| poweroffice_list_account_transactionsA | Read posted account transactions from GET /AccountTransactions for an inclusive date range. Use filters and small pages to keep accounting queries narrow. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
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.
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.
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.
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.