Skip to main content
Glama
rodascaar

ProfitPilot MCP Server

by rodascaar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
profitpilot_analyzeA

Ejecuta el pipeline completo de ProfitPilot usando Chain of Thought.

Este servidor NO usa LLMs externos. Genera prompts estructurados que el cliente MCP debe ejecutar con su propio modelo.

El flujo es:

  1. Cliente llama a profitpilot_analyze con el problema

  2. Servidor genera un prompt de razonamiento

  3. Cliente ejecuta el prompt con su modelo

  4. Cliente llama a profitpilot_continue con la respuesta

  5. Se repite hasta completar el análisis

ProfitPilot combina agentes especializados en:

  • Data Intelligence (análisis de métricas y anomalías)

  • Revenue & Margin (LTV, CLV, márgenes por canal)

  • Financial Modeling (cash flow, working capital, payback)

  • Competitor Intelligence (precios, tendencias del mercado)

  • Customer Insight (comportamiento, churn prediction)

  • Operations & Inventory (forecasting, stock levels)

  • Scenario & Risk Engine (simulación de escenarios)

  • Execution Agent (acciones automáticas)

  • Global Constraint Strategist (cuellos de botella globales)

profitpilot_continueA

Continúa una sesión de razonamiento con la respuesta del cliente.

Debe llamarse después de ejecutar el prompt generado por profitpilot_analyze o profitpilot_continue.

profitpilot_statusA

Obtiene el estado actual de una sesión de razonamiento.

profitpilot_resetC

Reinicia una sesión de razonamiento.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool occupies a distinct phase in the session lifecycle: analyze starts, continue advances, status inspects, and reset clears. There is no overlap, and the sequential dependency between analyze and continue is clearly documented.

Naming Consistency4/5

All tools share the consistent profitpilot_ prefix and lowercase snake_case style. Three use verbs (analyze, continue, reset), while status is a noun rather than get_status, which is a minor naming deviation.

Tool Count5/5

Four tools is a well-scoped surface for a session-driven reasoning workflow. Each operation is essential for starting, continuing, inspecting, and resetting a session, with no redundant tools.

Completeness4/5

The core session lifecycle is covered: start, continue, inspect status, and reset. The main gap is the lack of an explicit final-report retrieval endpoint, though status may partially cover this and the client already holds the model responses.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources