Financial Cents MCP vs YouTrack

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.

YouTrack

Every instance serves an OpenAPI 3.0 document, a 23-tool MCP server with OAuth and PKCE, and field selection on each REST call, and the free plan covers ten users. No rate limits, 429 handling, error reference or SLA were found, and JetBrains disclosed two sets of critical vulnerabilities affecting YouTrack Cloud in 2026, both patched.

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

YouTrack

1. Send fields on every REST request. Without it the server returns only the database ID and $type of each entity
2. Page collections with $top and $skip. Most resources return 42 items by default
3. Call get_issue_fields_schema before create_issue or update_issue, because required custom fields differ by project
4. Connect MCP clients to https://<instance>.youtrack.cloud/mcp. OAuth needs an administrator to enable CIMD or register the client, since Dynamic Client Registration is not supported
5. Create permanent tokens with the YouTrack scope only, and add ?tools= to the MCP URL to limit the tools listed