npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gastos-flow-mcp-server

v1.0.1

Published

MCP server for Gastos Flow expense tracking API

Readme

gastos-flow-mcp-server

Servidor MCP (Model Context Protocol) para Gastos Flow, una aplicación de seguimiento de gastos personales. Expone todas las operaciones de la API REST como herramientas utilizables desde Claude Desktop u otros clientes MCP.

Herramientas disponibles

| Recurso | Herramientas | |---|---| | Autenticación | login, logout, get_perfil | | Gastos | list, get, create, update, delete | | Ingresos | list, get, create, update, delete | | Categorías de gasto | list, get, create, update, delete | | Orígenes de ingreso | list, create, update, delete | | Monedas | list, create, update, delete | | Cuentas | list, get, create, update, delete | | Personas | list, create, update, delete | | Deudas propias | list, get, create, update, delete, marcar_pagada | | Deudas por cobrar | list, get, create, update, delete, marcar_cobrada | | Gastos recurrentes | list, get, create, update, delete, activar, desactivar |

Instalación

No requiere instalación previa. Se ejecuta directamente con npx:

npx gastos-flow-mcp-server

Configuración en Claude Desktop

Agrega la siguiente entrada en tu claude_desktop_config.json:

{
  "mcpServers": {
    "gastos-flow": {
      "command": "npx",
      "args": ["-y", "gastos-flow-mcp-server"],
      "env": {
        "GASTOS_FLOW_TOKEN": "tu-token-sanctum"
      }
    }
  }
}

El archivo de configuración se encuentra en:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Autenticación

Hay dos formas de autenticarse:

1. Variable de entorno (recomendado): Define GASTOS_FLOW_TOKEN con un token válido de Sanctum antes de arrancar el servidor (como se muestra en la configuración de Claude Desktop arriba).

2. Tool en tiempo de ejecución: Llama a gastos_flow_login con tu email y contraseña. El token se almacena en memoria para el resto de la sesión.

Para obtener un token puedes hacer:

curl -X POST https://gastosflow.com/api/v1/login \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","password":"tu_password"}'

Desarrollo local

git clone <repo>
cd gastos-flow-mcp
npm install
npm run dev    # Ejecuta con tsx watch (auto-reload al guardar)
npm run build  # Compila TypeScript → dist/
npm start      # Ejecuta el servidor compilado

Modo HTTP

Para correr el servidor en modo HTTP en lugar de stdio:

TRANSPORT=http PORT=3000 npm start

Esto expone el servidor en http://localhost:3000/mcp.

Estructura del proyecto

src/
├── index.ts           # Punto de entrada, registra tools y selecciona transporte
├── constants.ts       # API_BASE_URL, enums (TipoCuenta, Frecuencia, ResponseFormat)
├── types.ts           # Interfaces TypeScript para los objetos de la API
├── services/
│   └── api.ts         # Cliente Axios, almacén de token, manejo de errores
└── tools/
    ├── auth.ts        # Login, logout, perfil
    ├── gastos.ts      # CRUD gastos
    ├── ingresos.ts    # CRUD ingresos
    ├── catalogos.ts   # Categorías, orígenes, monedas, personas
    ├── cuentas.ts     # CRUD cuentas
    ├── deudas.ts      # Deudas propias y por cobrar
    └── recurrentes.ts # Gastos recurrentes