manager-full-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@manager-full-mcp open the permissions panel and show me what's currently blocked"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
manager-full-mcp
Full-surface MCP server for Manager.io, with a local control panel where you tick exactly what Claude may do — per business, per resource, per operation.
Why
The stock manager-mcp server exposes 24 hand-curated document types out of the
~310 your Manager instance actually has, and hides the rest behind a hard-coded
denylist (tax codes, exchange rates, custom fields, projects, fixed assets, lock
date, recurring documents …). Permissions are nine coarse CSV "scopes" set in
environment variables.
This server:
Reads the API surface from your own instance. Manager serves an OpenAPI document at the API base URL; every path in it becomes a resource. Nothing is curated away, and a Manager upgrade that adds document types shows up after
refresh_catalog.Gates every call on a tick box, with three states. Read / create / update / delete, for each of the ~310 resources: blocked, ask first, or allowed. Edited in a local web panel and re-read on every tool call — no restart.
Marks the dangerous resources in red. 111 of the 310 change the structure of the books rather than record a transaction. They are labelled ⚠ HIGH RISK everywhere, and switching one to "allowed without asking" needs a second confirmation.
Serves any number of businesses. Each one has its own token, its own catalog and its own permission file.
The only permanent block is account security: access_tokens,
user_permissions and customer_portal are read-only, because writing there
changes who can reach your books.
Related MCP server: Governed MCP Gateway
Install
git clone https://github.com/nezaralzien/manager-full-mcp.git
cd manager-full-mcp
uv venv --python 3.12 ~/.manager-full-mcp/venv
uv pip install --python ~/.manager-full-mcp/venv/bin/python .For Claude Desktop, build the extension bundle and double-click it:
python3 build_mcpb.py # writes manager-full-mcp.mcpb, pointing at the venv aboveFor any other MCP host, add this to its config:
{
"mcpServers": {
"manager-full": {
"command": "/Users/you/.manager-full-mcp/venv/bin/python",
"args": ["-m", "manager_full_mcp.server"]
}
}
}No API URL or token in the config: businesses are added in the control panel.
First run
Ask Claude to open the permissions panel (tool
open_permissions_panel), or run~/.manager-full-mcp/venv/bin/manager-full-panel.Businesses tab → add a business: display name, API URL (usually ends with
/api2), and an access token from Manager → Settings → Access Tokens. The panel tests the connection and loads the resource list. Repeat for as many businesses as you like.Permissions tab → set what Claude may do. Presets: Read only, Safe writes (day-to-day documents, no deletes), Ask first for everything, Everything (high-risk resources land on ask first), Clear all. Press Save.
Claude picks up the new settings on its very next call.
The three states
State | Meaning |
✕ Blocked | Claude cannot do it. The tool answers with which box to tick. |
? Ask first | Claude stops before writing and a confirmation box appears on your screen with the business, the operation and a preview of the exact fields. Buttons: Deny, Allow once, Allow 15 min. No answer within two minutes counts as Deny, and if no dialog can be shown the operation is refused. |
✓ Allowed | Goes through without asking. |
"Ask first" is enforced in the server, not suggested to the model: the write does not happen until the dialog comes back with a yes.
High-risk resources
Shown in red, tagged ⚠ HIGH RISK, with an explanation on the group:
Group | Why it is risky |
Chart of accounts & account definitions | Decide how every past and future transaction is classified |
Starting balances | Feed every period after them |
Tax (tax codes, withholding) | Apply to documents that already exist, so filed totals can be restated |
Currencies & exchange rates | Revalue every foreign-currency transaction |
Custom fields, themes, email templates, lock date | Change behaviour business-wide; the lock date is what protects closed periods |
Bank reconciliations | Audit evidence that an account was checked |
Account security | Permanently read-only — access tokens, user permissions, customer portal |
manager_catalog reports risk and risk_note for each resource, and every
write to a high-risk resource comes back with a caution field so Claude tells
you exactly what changed.
Tools
Tool | What it does |
| Businesses this connection can reach |
| Opens the tick-box panel, returns its URL |
| Browse/search every resource and what is allowed |
| What is currently allowed, and where the rules come from |
| Search/page any collection, feed or report |
| One record by Key, in Manager's own shape |
| Create a record |
| Update a record (merge by default, |
| Delete a record (returns a copy of what was deleted) |
| Raw GET on any path (needs Raw read) |
| Raw POST/PUT/DELETE (needs Raw write) |
| Rasterise a PDF to one PNG per page — Manager's Image field silently rejects PDFs |
| Re-read the instance's API description |
Every tool takes an optional business; it can be omitted when only one
business is configured.
Attachments
Manager's Image field accepts images and silently drops PDFs, and a multi-page
document has to become one image per page. prepare_attachment does that
conversion in-process (pypdfium2 + a small PNG writer — no poppler, no
ImageMagick, no Pillow), so the rule cannot fail because a converter is missing
from the machine. Converted pages land in ~/.manager-full-mcp/converted/.
Where things live
Path | Contents |
| Businesses and access tokens (mode 0600) |
| The tick boxes for one business |
| Cached resource catalog |
Tokens never travel through the chat: they are typed into the local panel, which
binds to 127.0.0.1 only and requires a per-session token on every request.
Environment variables (optional)
Variable | Effect |
|
|
| Default create/update for a group before the panel is used. For high-risk groups a tick means ask first, never silent access |
| Same, for delete |
| Defaults for the raw escape hatches |
| Config directory (default |
| Bootstrap a single business without the panel |
Group ids: parties, sales, purchases, banking, inventory, payroll, assets, ledger, projects, tax, currencies, recurring, starting_balances, accounts, reports, customization, attachments.
Once you save in the panel, the panel file wins and these defaults are ignored.
بالعربي — باختصار
الـ MCP هاد بيفتح كل موارد Manager (~310 مورد) مو بس 24.
الصلاحيات بتتحكم فيها من لوحة تحكم محلية، ولكل مورد ولكل عملية (قراءة / إنشاء / تعديل / حذف) ثلاث حالات: ✕ ممنوع، ؟ اسأل أولاً، ✓ مسموح.
«اسأل أولاً» تنفيذ حقيقي: كلود بيوقف، وبتطلعلك نافذة تأكيد من النظام فيها الشركة والعملية وتفاصيل الحقول، وأزرار: رفض / سماح مرة / سماح ١٥ دقيقة. ما في جواب خلال دقيقتين = رفض.
الموارد الخطرة (١١١ مورد: شجرة الحسابات، رموز الضريبة، أسعار الصرف، الأرصدة الافتتاحية، تاريخ الإقفال، الإعدادات) بتطلع بلون أحمر مع تحذير، وتحويلها لـ «مسموح بدون سؤال» بيطلب تأكيد إضافي.
بتضيف أي عدد شركات من اللوحة نفسها: اسم + رابط الـ API + رمز الوصول.
التغيير بصير فوري — ما في داعي تسكّر كلود وتفتحه.
الشي الوحيد المقفول دايماً: رموز الوصول وصلاحيات المستخدمين وبوابة العملاء (قراءة فقط).
لفتح اللوحة: اطلب من كلود «افتح لوحة صلاحيات Manager» أو شغّل
~/.manager-full-mcp/venv/bin/manager-full-panel.
Development
pip install -e ".[dev]"
pytest -q # 42 tests, no network: a stub Manager instance is served locally
python3 tools/make_icon.py # regenerates the extension icontests/data/openapi.json is a real Manager 26.9.1 API description with the
instance URL replaced by localhost. It contains no business data.
Relationship to manager-mcp
Independent implementation, written from scratch, inspired by flumpiey/manager-mcp — a read-first server with nine CSV write scopes over 24 curated document types. This project takes the opposite approach: expose the instance's whole API surface and put a three-state permission grid in front of it. No code is shared between the two.
License
MIT
Available Tools
13 toolslist_businessesList BusinessesARead-only
List the Manager businesses this connection can reach, with their ids. Every other tool takes an optional 'business' argument; it can be left out when only one business is configured.
Inputs: no named parameters. Returns: object
manager_api_getManager Api GetARead-only
Escape hatch: GET any Manager API path directly (e.g. '/customers' or '/sales-invoice-form/{key}'). Only for paths the catalog does not model. Requires 'Raw read' in the control panel.
Inputs: path (required), params, business. Returns: object
manager_api_requestManager Api RequestA
Escape hatch: send any method (POST/PUT/DELETE) to any Manager API path. Bypasses per-resource tick boxes, so it requires the separate 'Raw write' box in the control panel. Prefer manager_create / manager_update.
Inputs: path (required), method (required), body, business. Returns: object
manager_catalogManager CatalogARead-only
Browse the resource catalog of a business: every document, list, report and setting the Manager instance exposes, with the operations allowed by the current tick boxes. Start here when you do not know a resource name. Filter with 'search' (e.g. 'invoice', 'tax') or 'group'.
Inputs: group, limit, search, business, +1 more. Returns: object
manager_createManager CreateA
Create a record (invoice, payment, customer, journal entry, tax code, …). 'fields' is Manager-native JSON: copy the shape from manager_get on an existing record of the same resource. Returns the new Key. For resources the catalog marks risk='high', get an explicit yes from the user first.
Inputs: fields (required), resource (required), business. Returns: object
manager_deleteManager DeleteADestructive
Delete a record permanently. Manager has no undo, so confirm with the user first; the deleted document is returned in the response so it can be re-created if needed.
Inputs: key (required), resource (required), business. Returns: object
manager_getManager GetARead-only
Fetch one record by its Key (GUID) in the exact shape Manager stores it. Always do this before an update, and use an existing record as the template for a create — Manager's field names are not guessable.
Inputs: key (required), resource (required), business. Returns: object
manager_listManager ListARead-only
Search or page any Manager collection, report feed or list (customers, sales_invoices, payments, tax_codes, general ledger feeds, …). 'term' searches, 'sort_by' takes a column name, and date feeds accept from_date / to_date (YYYY-MM-DD). Unsupported parameters are reported back rather than silently dropped.
Inputs: resource (required), skip, term, fields, +7 more. Returns: object
manager_permissionsManager PermissionsARead-only
Show what this connection is currently allowed to do for a business: the totals per operation, where the rules come from, and the full list of resources with write access. Use it before telling the user something is not possible.
Inputs: business. Returns: object
manager_updateManager UpdateA
Update a record. For resources the catalog marks risk='high' (accounts, tax codes, rates, opening balances, settings) confirm with the user first — those changes restate existing books. Default mode 'merge' reads the live document first and changes only the fields you pass, which is what you normally want because Manager's PUT replaces the whole document. Use mode='replace' to send the body verbatim.
Inputs: key (required), fields (required), resource (required), mode, +1 more. Returns: object
open_permissions_panelOpen Permissions PanelARead-only
Open the local permissions control panel in the browser and return its URL. That panel is where the user ticks which resources this connection may read, create, update or delete, and where businesses and their access tokens are added. Changes apply immediately, no restart.
Inputs: open_browser. Returns: object
prepare_attachmentPrepare AttachmentARead-only
Turn a file into something Manager will accept as evidence. Manager's Image field silently rejects PDFs, so ALWAYS run this on any PDF before attaching it: it rasterises every page and returns the image paths. Images pass through untouched. combine='vertical' (or 'horizontal') joins the pages of ONE document — a statement, a contract — into a single image, which is the right shape when the pages are one document. Leave combine='none' when the PDF holds several different documents, and never merge two different proofs into one image: each proof is its own attachment.
Inputs: file_path (required), dpi, combine. Returns: object
refresh_catalogRefresh CatalogARead-only
Re-read the Manager instance's own API description and rebuild the resource catalog. Run this after upgrading Manager or when a resource seems missing.
Inputs: business. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: business listing, permissions, catalog management, file preparation, and per-resource CRUD operations are all uniquely scoped. Even the escape hatches (manager_api_get/api_request) are clearly differentiated from the typed CRUD tools by their raw, unvalidated nature.
Most tools follow a readable pattern: CRUD operations use 'manager_' + verb (list/get/create/update/delete), while auxiliary tools use verb_noun (prepare_attachment, open_permissions_panel, refresh_catalog). The mix is not chaotic, but the 'manager_' prefix is applied inconsistently (manager_permissions, manager_catalog are nouns, not verbs), so it is not fully uniform.
13 tools is within the ideal range and perfectly scoped for a full Manager integration covering catalog discovery, CRUD operations, permissions, attachments, and raw API access. Each tool serves a distinct need without redundancy or bloat.
The tool surface is essentially complete for the Manager domain: it covers business discovery, permission introspection, catalog browsing and refreshing, full CRUD for arbitrary resources, list/search, file preparation for evidence, and raw API fallbacks. There are no obvious dead ends or missing lifecycle stages.
Maintenance
Related MCP Connectors
Connect AI to store orders, products and inventory with scoped access and human approvals.
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
QuickBooks Online for AI assistants, with per-user, per-company permissions.
Connect assistants to your company tools with per-person, per-action grants and a full audit log.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely interact with operations systems such as cloud inventory, runbooks, and ticketing while enforcing role-based access, JWT authentication, write confirmation, secret and PII redaction, rate limits, and audit logging.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and safely configure point-of-sale accounts across multi-location restaurant and café networks, with dry-run-by-default writes, account allow-lists, and audit logging.MIT
- AlicenseAqualityBmaintenanceSafety-first MCP server for the sevDesk accounting API (unofficial): invoices, credit notes and orders, receipts with e-invoice import (XRechnung, ZUGFeRD), bank reconciliation, a VAT summary, EÜR and DATEV export. Read-only by default; write tiers are opt-in, and finalizing, booking or sending needs a human to confirm.31422 npm1MIT