Notsy Facturación
Server Details
Emite CFDIs 4.0 y resuelve claves del SAT para agentes de IA (México), con permisos por API key.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: preview before emission, actual emission, SAT key lookup, and identity confirmation. No overlap or ambiguity.
Inconsistent naming: Spanish and English mixed (emitir_cfdi, preview_factura, resolver_claves_sat, whoami). Different verb styles and one single-word name break the pattern.
4 tools is well-scoped for an invoicing server covering preview, emission, key resolution, and identity. Not too few or too many.
Covers core emission workflow but lacks obvious operations like cancel, search, or list invoices, which are expected in a billing domain.
Available Tools
4 toolsemitir_cfdiInspect
Emite y timbra un CFDI 4.0 OFICIAL ante el SAT (acción real, con costo y difícil de revertir). Llama primero a preview_factura. El motor aplica los límites de la API key (puede requerir aprobación humana) y registra la acción en la bitácora.
Args: iguales a preview_factura, más:
observaciones: texto libre opcional en el CFDI.
anticipo_id: opcional, id de un anticipo previo a aplicar (relación 07 + nota de crédito).
idempotency_key: OBLIGATORIA en producción (genera un UUID por operación y reúsalo en
los reintentos). Si reintentas con la misma clave, NO se timbra de nuevo: se
devuelve el resultado original (evita CFDIs duplicados ante el SAT).
| Name | Required | Description | Default |
|---|---|---|---|
| cliente | No | ||
| conceptos | Yes | ||
| emisor_id | No | ||
| cliente_id | No | ||
| forma_pago | No | 03 | |
| anticipo_id | No | ||
| metodo_pago | No | PUE | |
| observaciones | No | ||
| idempotency_key | No |
preview_facturaInspect
DRY-RUN: valida la factura y calcula los totales (subtotal, IVA, retenciones, total) SIN timbrar y sin costo. Úsalo SIEMPRE antes de emitir_cfdi para confirmar el monto y que los datos pasen la validación.
Args:
conceptos: lista de conceptos. Cada uno: {descripcion, clave_prodserv, clave_unidad,
cantidad, valor_unitario, precio_incluye_iva (bool), tasa_iva (0.16/0.08/0.0),
objeto_imp ("02"), retencion ("honorarios"|"arrendamiento"|"comisiones"|"fletes"|"")}.
cliente: datos del receptor {rfc, nombre, regimen_fiscal, cp, uso_cfdi, email,
es_publico_general} — o usa cliente_id si ya está guardado.
cliente_id: id de un cliente guardado (alternativa a `cliente`).
forma_pago: clave SAT de forma de pago (default "03" transferencia).
metodo_pago: "PUE" (de contado) o "PPD" (a crédito).
emisor_id: opcional, desde qué RFC emitir (multiemisor); None = predeterminado.
| Name | Required | Description | Default |
|---|---|---|---|
| cliente | No | ||
| conceptos | Yes | ||
| emisor_id | No | ||
| cliente_id | No | ||
| forma_pago | No | 03 | |
| metodo_pago | No | PUE |
resolver_claves_satInspect
Convierte una descripción en lenguaje natural a las claves del SAT necesarias para facturar.
Devuelve `sugerencia` con clave_prodserv, clave_unidad, objeto_imp, tasa_iva y uso_cfdi, más
`candidatos` por si quieres elegir otra. Llámalo antes de armar un concepto si no conoces las claves.
Args:
descripcion: qué se vende, p.ej. "consultoría de marketing" o "laptop Dell".
unidad_hint: opcional, unidad de medida en palabras ("servicio", "hora", "pieza", "kg").
con_iva: si el producto/servicio causa IVA 16% (default True).
| Name | Required | Description | Default |
|---|---|---|---|
| con_iva | No | ||
| descripcion | Yes | ||
| unidad_hint | No |
whoamiInspect
Confirma la identidad del agente: a qué negocio pertenece la API key, sus permisos (scopes), límites de emisión y uso del día. Úsalo para diagnosticar la conexión.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!