MCP RifaExpress Backend
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_URL | No | API REST URL (optional) | |
| DB_HOST | Yes | PostgreSQL host | |
| DB_NAME | Yes | PostgreSQL database name | |
| DB_PORT | Yes | PostgreSQL port | |
| DB_USER | Yes | PostgreSQL user | |
| API_TOKEN | No | API REST JWT token (optional) | |
| DB_PASSWORD | Yes | PostgreSQL password |
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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rifaexpress_query_dbA | Ejecuta una query SELECT en la base de datos PostgreSQL de RifaExpress. Solo queries SELECT están permitidas por seguridad. |
| rifaexpress_inspect_tableB | Inspecciona el schema de una tabla específica (columnas, tipos, nullability, etc.). |
| rifaexpress_list_tablesC | Lista todas las tablas en el schema especificado. |
| rifaexpress_get_companiesB | Obtiene companies (empresas) con filtros opcionales de subscriptionStatus. |
| rifaexpress_get_usersC | Obtiene users con filtros opcionales de companyId y role. |
| rifaexpress_get_plansC | Obtiene plans de suscripción. |
| rifaexpress_get_subscriptionsC | Obtiene subscriptions (si la tabla existe). Esta entidad se creará en Fase 1 del SaaS Core. |
| rifaexpress_health_checkA | Verifica la conexión con la base de datos PostgreSQL. Útil para diagnosticar problemas de configuración. |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: get_companies, get_plans, get_subscriptions, get_users retrieve specific entities, health_check tests connectivity, inspect_table examines schema, list_tables enumerates tables, and query_db executes custom queries. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent 'rifaexpress_verb_noun' pattern using snake_case, with verbs like 'get', 'health_check', 'inspect', 'list', and 'query'. This predictability aids agent understanding and tool selection without confusion from mixed conventions.
With 8 tools, this server is well-scoped for a backend database interaction server. It covers essential operations like data retrieval, schema inspection, and health checks without being overly sparse or bloated, making each tool earn its place in the set.
The toolset provides strong read-only coverage for database interaction, including entity retrieval, schema exploration, and connectivity checks. However, it lacks write operations (e.g., create, update, delete), which could be a gap for full CRUD workflows, though this might be intentional for security as noted in query_db's description.