manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANAGER_API_KEY | Yes | API key sent as X-API-KEY header | |
| MANAGER_API_URL | Yes | Opaque base URL of Manager.io API (include /api2 when needed) | |
| MANAGER_MCP_ALLOW_WRITES | No | Opt-in writes: 1/true/yes/on registers api_write tool (POST/PUT/PATCH/DELETE). Unset → read-only. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_resourcesA | List curated Manager.io capabilities. Default is read-only (10 tools). Task tools register when write scopes match; CRUD tools are deprecated unless raw scope is set. |
| list_recordsA | Search/page a curated collection. Core: customers, suppliers, sales_invoices, purchase_invoices, chart_of_accounts, bank_accounts. Also writable domains when present in discovery (e.g. receipts, payments, sales_quotes). bank_accounts is the searchable collection; use bank_balances for snapshot balances. |
| get_recordA | Fetch one collection record by GUID via Manager form endpoint (e.g. /customer-form/{key}). chart_of_accounts has no single form. For bank/cash account detail use resource=bank_accounts (not bank_balances). |
| aged_receivablesB | Aged receivables / outstanding customer balances (read-only snapshot). |
| aged_payablesC | Aged payables snapshot (read-only). |
| bank_balancesB | Bank/cash balances snapshot (read-only). For search/drill-in of individual accounts use list_records/get_record on bank_accounts. |
| trial_balanceC | Trial balance snapshot (read-only). |
| profit_and_lossB | Profit and loss snapshot (read-only). |
| balance_sheetC | Balance sheet snapshot (read-only). |
| tax_summaryC | Tax summary snapshot (read-only). |
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 has a clearly distinct purpose: listing/searching resources and records, fetching a single record, and specific financial report snapshots. There is no ambiguity between tools like list_records and get_record, as one is for searching and the other for retrieving by ID.
The tools follow two clear naming patterns: verb_noun for list and get operations (list_resources, list_records, get_record) and noun_phrases for financial reports (aged_receivables, trial_balance, etc.). While the shift between patterns is noticeable, it is predictable and domain-appropriate.
With 10 tools, the server covers a reasonable set of operations for an accounting system: resource introspection, data retrieval, and key financial reports. The count is well-scoped, neither too sparse nor too heavy.
The tool set is read-only, providing search, retrieval, and report snapshots but lacking any create, update, or delete operations. For a management tool, this is a notable gap that limits agent functionality for common tasks like entering invoices or managing customers.