io.github.SamuelMoraesF/mcp-organizze
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORGANIZZE_EMAIL | Yes | Seu email de login do Organizze. | |
| ORGANIZZE_API_KEY | Yes | Sua chave de API do Organizze. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getUserC | Detalhar usuário |
| getAccountsA | Listar contas bancárias |
| createAccountC | Criar conta bancária |
| getAccountB | Detalhar conta bancária |
| updateAccountC | Atualizar conta bancária |
| deleteAccountB | Excluir conta bancária |
| getBudgetsB | Listar metas do mês atual |
| getYearBudgetsC | Listar metas do ano |
| getMonthBudgetsB | Listar metas de um mês específico |
| getCategoriesB | Listar categorias |
| createCategoryD | Criar categoria |
| getCategoryC | Detalhar categoria |
| updateCategoryD | Atualizar categoria |
| deleteCategoryC | Ao excluir, pode-se informar uma |
| getCreditCardsB | Listar cartões de crédito |
| createCreditCardC | Criar cartão de crédito |
| getCreditCardC | Detalhar cartão de crédito |
| updateCreditCardD | Atualizar cartão de crédito |
| deleteCreditCardC | Excluir cartão de crédito |
| getCreditCardInvoicesA | Se start_date e end_date não forem informados, retorna apenas faturas em aberto e/ou futuras. |
| getCreditCardInvoiceD | Detalhar uma fatura |
| getCreditCardInvoicePaymentB | Retorna o lançamento de pagamento referente a uma fatura. |
| getTransactionsA | Lista as movimentações. Atenção: Existe um limite de 300 transações por resposta. Caso esse limite seja atingido, recomenda-se realizar buscas por períodos menores (usando |
| createTransactionB | Cria movimentações simples, recorrentes (fixas) ou parceladas. |
| getTransactionC | Detalhar movimentação |
| updateTransactionD | Atualizar movimentação |
| deleteTransactionD | Excluir movimentação |
| getTransfersB | Listar transferências |
| createTransferA | Cria uma transferência entre duas contas. Cartões de crédito não são aceitos. |
| getTransferC | Detalhar transferência |
| updateTransferD | Atualizar transferência |
| deleteTransferD | Excluir transferência |
| getBalancesC | Obter relatório de saldos |
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 33 tools
Most tools are clearly separated by resource and action, but the budget trio (getBudgets, getYearBudgets, getMonthBudgets) and invoice trio (getCreditCardInvoices, getCreditCardInvoice, getCreditCardInvoicePayment) are closely related and could be misselected without careful reading. Plural vs singular naming helps, but descriptions are needed to fully disambiguate.
All tools follow a consistent verb + resource convention, using plural for list operations and singular for detail operations (e.g., getAccounts vs getAccount). The pattern is uniform across all resources, with no mixed casings or irregular verbs.
With 33 tools, the server is well beyond the typical well-scoped range of 3-15. The count reflects a full CRUD API for many resources, but it feels heavy and could be consolidated (e.g., merging budget list variants).
Accounts, credit cards, transactions, transfers, and categories have full CRUD coverage, but budgets are read-only with no create/update/delete operations. Invoice management is also limited to reading and payment lookup, leaving notable gaps in budget management workflows.