Financial Cents MCP vs Redmine

Financial Cents MCP

The server gives assistants 40 tools over an accounting firm's Financial Cents data, under the user's own permissions and bound to one firm by OAuth. Tool descriptions are detailed and client chat is marked as untrusted. It can send and charge invoices with one undivided scope, and there's no status page, numeric MCP rate limit or readable tool schema.

Redmine

Redmine's REST API covers issues, projects, time entries and 20 other resources, and versions 6.1 and later add OAuth 2 with one scope per permission. The software is free under the GPL. No OpenAPI document exists, most errors return a bare status code, and 24 security advisories were published in twelve months, two rated critical.

Financial Cents MCP

1. Call whoami first and work out date windows from user.timezone, not company.timezone
2. Resolve clients and projects with list_clients or list_projects search, since lookup covers only reference data such as users, tags and service items
3. Check money units per tool. Invoices, payments, proposals and credit memos use integer cents, while time entries and service-item rates use dollars
4. Never retry a successful invoice_actions, proposal_actions or credit-memo create, since a second call can email or charge the client again
5. Get the person's approval before any write, and use preview: true before sending a proposal

Redmine

1. Ask an administrator to tick Enable REST API under Administration, Settings, API. It is off by default and every call fails until then
2. Send the key in the X-Redmine-API-Key header, never as the key query parameter, and set Content-Type: application/json on every POST and PUT
3. Add status_id=* to issue lists. The default returns open issues only, 25 a page with a maximum of 100
4. Comment on an issue by sending notes in a PUT to /issues/<id>.json. There is no separate comment endpoint
5. A DELETE on a project through the API skips the confirmation the web page asks for, so run the agent as a non-administrator user