io.github.codespar/mcp-omie

NPM · @CODESPAR/MCP-OMIE · SCANNED AUG 3

MCP server for Omie — ERP, customers, products, orders, invoices, financials

Available components

+21 this week 67 67 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 41 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability66

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 2638 tokens (~87/item across 30 items; 30 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @codespar/mcp-omie

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add codespar-mcp-omie -- npx -y @codespar/mcp-omie

# add to Codex CLI

codex mcp add codespar-mcp-omie -- npx -y @codespar/mcp-omie

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codespar-mcp-omie": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@codespar/mcp-omie"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add codespar-mcp-omie --command npx --arg -y --arg @codespar/mcp-omie

# ~/.hermes/config.yaml

mcp_servers:
  codespar-mcp-omie:
    command: "npx"
    args: ["-y", "@codespar/mcp-omie"]

// mcp.json

{
  "mcpServers": {
    "codespar-mcp-omie": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-omie"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +46
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Dependency health: unverified → partial ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
1 Aug 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 46

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@codespar/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 30 exposed · ~2,571 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

create_account_payable ~150

Create an accounts payable (AP) entry in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_categoria	string	yes	Category code (chart of accounts)
codigo_cliente_fornecedor	number	yes	Omie supplier ID
codigo_lancamento_integracao	string	yes	Integration code (unique)
data_previsao	string	—	Expected payment date (DD/MM/YYYY)
data_vencimento	string	yes	Due date (DD/MM/YYYY)
id_conta_corrente	number	—	Bank account ID
numero_documento	string	—	Document/invoice number
observacao	string	—	Notes
valor_documento	number	yes	Document value in BRL

No output schema declared.

No examples provided.

create_cash_entry ~111

Create a bank account ledger entry (lançamento de conta corrente) in Omie ERP

Input Output Examples

Name	Type	Req	Description
cabecalho	object	yes	Entry header: { cCodIntLanc, nCodCC, dDtLanc, nValorLanc, cNatureza (E=entrada, S=saida), cTipo (DEB/CRE), cHistorico }
detalhes	object	—	Entry details: { cCodCateg, nCodCliente, cObs, nCodProjeto, nCodDepto }

No output schema declared.

No examples provided.

create_customer ~129

Create a customer in Omie ERP

Input Output Examples

Name	Type	Req	Description
bairro	string	—	Neighborhood
cep	string	—	Postal code
cidade	string	—	City
cnpj_cpf	string	yes	CPF or CNPJ
email	string	—	Email address
endereco	string	—	Street address
endereco_numero	string	—	Address number
estado	string	—	State (UF)
nome_fantasia	string	—	Trade name
razao_social	string	yes	Legal name
telefone1_numero	string	—	Phone number

No output schema declared.

No examples provided.

create_invoice ~32

Consult a specific NF by ID in Omie ERP

Input Output Examples

Name	Type	Req	Description
nIdNF	number	yes	Omie NF ID

No output schema declared.

No examples provided.

create_order ~90

Create a sales order in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_cliente	number	yes	Omie customer ID
codigo_pedido_integracao	string	yes	Integration order code (unique)
data_previsao	string	yes	Expected date (DD/MM/YYYY)
frete	object	—	Shipping details
itens	array	yes	Array of order items (produto, quantidade, valor_unitario)

No output schema declared.

No examples provided.

create_product ~80

Create a product in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo	string	yes	Product code (internal)
descricao	string	yes	Product description
ncm	string	yes	NCM code (tax classification)
unidade	string	yes	Unit of measure (UN, KG, etc.)
valor_unitario	number	yes	Unit price in BRL

No output schema declared.

No examples provided.

create_purchase_order ~94

Create a purchase order in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_fornecedor	number	yes	Omie supplier ID
codigo_pedido_integracao	string	yes	Integration order code (unique)
data_previsao	string	yes	Expected date (DD/MM/YYYY)
itens	array	yes	Array of items (produto, quantidade, valor_unitario)
observacoes	string	—	Order notes/observations

No output schema declared.

No examples provided.

create_service_order ~97

Create a service order (OS) in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_cliente	number	yes	Omie customer ID
codigo_pedido_integracao	string	yes	Integration order code (unique)
data_previsao	string	yes	Expected date (DD/MM/YYYY)
observacoes	string	—	Order notes/observations
servicos	array	yes	Array of services (descricao, valor_unitario, quantidade)

No output schema declared.

No examples provided.

create_stock_adjustment ~157

Create an inventory adjustment (entry/exit/balance) in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_local_estoque	number	—	Warehouse location ID
codigo_motivo	number	—	Reason code
codigo_produto	number	—	Omie product ID
codigo_produto_integracao	string	—	Product integration code (alternative)
data_ajuste	string	yes	Adjustment date (DD/MM/YYYY)
observacao	string	—	Notes
quantidade	number	yes	Quantity
tipo_ajuste	string	yes	Adjustment type: ENT (entry), SAI (exit), SLD (balance), TRF (transfer)
valor	number	—	Unit value in BRL

No output schema declared.

No examples provided.

get_bank_accounts ~48

List registered bank accounts in Omie ERP

Input Output Examples

Name	Type	Req	Description
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

get_bank_statement ~105

Retrieve bank account statement (extrato) for a period from Omie ERP

Input Output Examples

Name	Type	Req	Description
cCodIntCC	string	—	Bank account integration code (alternative to nCodCC)
cExibirApenasSaldo	string	—	Show only balances (S/N)
dPeriodoFinal	string	yes	End date (DD/MM/YYYY)
dPeriodoInicial	string	yes	Start date (DD/MM/YYYY)
nCodCC	number	—	Bank account ID

No output schema declared.

No examples provided.

get_company_info ~47

List companies registered in Omie ERP

Input Output Examples

Name	Type	Req	Description
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

get_financial ~84

List accounts receivable from Omie ERP

Input Output Examples

Name	Type	Req	Description
dDtEmiFinal	string	—	End emission date (DD/MM/YYYY)
dDtEmiInicial	string	—	Start emission date (DD/MM/YYYY)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

get_sales_order ~53

Consult a specific sales order by ID or integration code in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_pedido	number	—	Omie order ID
codigo_pedido_integracao	string	—	Integration order code (alternative)

No output schema declared.

No examples provided.

get_stock_position ~102

Get current stock position / balance in Omie ERP

Input Output Examples

Name	Type	Req	Description
cExibirTodos	string	—	Include items with zero stock (S/N)
codigo_local_estoque	number	—	Filter by warehouse location ID
dDataPosicao	string	—	Position reference date (DD/MM/YYYY)
nPagina	number	—	Page number (default 1)
nRegPorPagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

invoice_sales_order ~53

Generate an invoice (NF) from an existing sales order in Omie ERP

Input Output Examples

Name	Type	Req	Description
cCodIntPed	string	—	Integration order code (alternative)
nCodPed	number	—	Omie order ID

No output schema declared.

No examples provided.

list_accounts_payable ~111

List accounts payable (AP) titles in Omie ERP

Input Output Examples

Name	Type	Req	Description
dDtVencAte	string	—	Due date to (DD/MM/YYYY)
dDtVencDe	string	—	Due date from (DD/MM/YYYY)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)
status_titulo	string	—	Title status (ABERTO, LIQUIDADO, etc.)

No output schema declared.

No examples provided.

list_categories ~48

List chart of accounts categories in Omie ERP

Input Output Examples

Name	Type	Req	Description
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_customers ~68

List customers from Omie ERP

Input Output Examples

Name	Type	Req	Description
clientesFiltro	object	—	Filter object (nome_fantasia, cnpj_cpf, etc.)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_departments ~50

List departments (cost centers) in Omie ERP

Input Output Examples

Name	Type	Req	Description
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_dre ~44

List DRE (income statement) chart of accounts in Omie ERP

Input Output Examples

Name	Type	Req	Description
apenasContasAtivas	string	—	Only active accounts (S/N, default S)

No output schema declared.

No examples provided.

list_financial_movements ~143

List unified financial movements (AP + AR + CC) in Omie ERP

Input Output Examples

Name	Type	Req	Description
cNatureza	string	—	Nature (R=receivable, P=payable, T=all)
cStatus	string	—	Status (ABERTO, LIQUIDADO, VENCIDO, etc.)
dDtPagtoAte	string	—	Payment date to (DD/MM/YYYY)
dDtPagtoDe	string	—	Payment date from (DD/MM/YYYY)
nPagina	number	—	Page number (default 1)
nRegPorPagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_invoices ~83

List invoices (NF) from Omie ERP

Input Output Examples

Name	Type	Req	Description
dEmiFinal	string	—	End emission date (DD/MM/YYYY)
dEmiInicial	string	—	Start emission date (DD/MM/YYYY)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_orders ~80

List sales orders from Omie ERP

Input Output Examples

Name	Type	Req	Description
etapa	string	—	Order stage filter (10=Pedido, 20=Separar, 50=Faturar, 60=Faturado)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_products ~60

List products from Omie ERP

Input Output Examples

Name	Type	Req	Description
apenas_importado_api	string	—	Only API-imported products
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_projects ~60

List projects in Omie ERP

Input Output Examples

Name	Type	Req	Description
apenas_importado_api	string	—	Only API-imported projects
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_purchase_orders ~74

List purchase orders from Omie ERP

Input Output Examples

Name	Type	Req	Description
etapa	string	—	Order stage filter (10=Pedido, 50=Receber, 60=Recebido)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

list_service_orders ~84

List service orders (OS) from Omie ERP

Input Output Examples

Name	Type	Req	Description
etapa	string	—	Order stage filter (10=OS, 20=Executar, 50=Faturar, 60=Faturado)
pagina	number	—	Page number (default 1)
registros_por_pagina	number	—	Records per page (default 50)

No output schema declared.

No examples provided.

pay_account_payable ~132

Settle / record payment (baixa) for an AP title in Omie ERP

Input Output Examples

Name	Type	Req	Description
codigo_baixa	string	yes	Settlement integration code (unique)
codigo_conta_corrente	number	yes	Bank account ID used for the payment
codigo_lancamento	number	—	Omie AP title ID
codigo_lancamento_integracao	string	—	Integration code (alternative to codigo_lancamento)
data	string	yes	Payment date (DD/MM/YYYY)
observacao	string	—	Payment notes
valor	number	yes	Paid amount in BRL

No output schema declared.

No examples provided.

update_sales_order ~102

Alter an existing sales order in Omie ERP

Input Output Examples

Name	Type	Req	Description
cabecalho	object	yes	Order header: { codigo_pedido, codigo_pedido_integracao, codigo_cliente, data_previsao, etapa, ... }
frete	object	—	Shipping details
informacoes_adicionais	object	—	Additional info (codigo_vendedor, etc.)
itens	array	—	Updated order items
observacoes	object	—	Order observations

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug