Skip to main content
Glama
CelpAI

celp-mcp

Official
by CelpAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MONGO_URLNoMongoDB connection URL
CELP_API_KEYNoAPI key for Celp orchestration backend
DATABASE_HOSTNoDatabase host
DATABASE_NAMENoDatabase name
DATABASE_PORTNoDatabase port (optional, defaults to standard port)
DATABASE_TYPENoType of database: postgres, mysql, mongodb, databricks
DATABASE_USERNoDatabase user
PG_DISABLE_SSLNoSet to 'true' to disable SSL for PostgreSQL
DATABRICKS_HOSTNoDatabricks host
DATABRICKS_TOKENNoDatabricks token
DATABASE_PASSWORDNoDatabase password
STREAMING_API_URLNoOverride streaming API URL
DATABRICKS_CATALOGNoDatabricks catalog
DATABRICKS_HTTP_PATHNoDatabricks HTTP path

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
query-databaseB

Data Analyst Agent: Reasoning Analysis Mode

This tool translates natural language into multi-step SQL analysis plans and executes them against databases. Use this for complex analytical questions requiring more reasoning.

Capabilities

  • Performs multi-step analyses with each step building on previous results

  • Analyzes data across multiple tables with complex relationships

  • Handles complex queries requiring careful reasoning and planning

  • Produces comprehensive markdown reports with insights

When to Use

  • For complex analytical questions requiring deep reasoning

  • When accuracy and comprehensiveness is more important than speed

  • For queries involving multiple tables or complex relationships

  • When detailed insights and explanations are needed

Effective Prompts

  • Be specific about metrics, time periods, and entities of interest

  • Include relevant business context for interpretation

  • Specify desired output format (tables, charts, insights)

  • For complex analyses, break down into logical components

Restrictions:

  • Don't sent database credentials in the payload, it's handled by the server.

  • Don't sent API keys in the payload, it's handled by the server.

query-database-turboC

When to Use (Natural-Language Heuristics)

Because the model sees only the user's question and minimal schema hints, Turbo Mode should activate automatically whenever the request exhibits every one of these surface-level cues. Each cue corresponds to a first-principles driver of SQL complexity that the model can infer without deep schema knowledge:

Signal in the User's Question

Why It Indicates Turbo Is Safe

Single Factual Verb — verbs like "count," "list," "show," "sum," "average," or "max/min," used once.

One aggregate or projection keeps the SQL to a single SELECT.

At Most One Qualifier Clause — a lone filter such as a date range, status, or simple equality ("where status = 'active'").

Few filters avoid nested logic or subqueries.

No Comparative Language — absent words like "versus," "compare," "trend," "change over time," "prior year," "by each," etc.

Comparisons imply multiple groupings, time windows, or self-joins.

No Multi-Dimensional Grouping Phrases — avoids "by region and product," "per user per month," "split across categories."

Multiple dimensions require complex GROUP BY and often joins.

Mentions One Table-Like Concept — either explicitly ("in orders") or implicitly ("orders today," "users last week").

Referencing several entities hints at join logic the model can't verify quickly.

Requests Raw IDs or a Small Top-N List — e.g., "give me the top 5 order IDs."

The result set will be tiny, so execution latency is dominated by query planning—not data transfer.

No Need for Explanation or Visualization — the user asks only for the numbers or rows, not "explain why" or "graph this."

Generating narrative or charts costs tokens and time; Turbo avoids it.

Quick mental check: Could you answer this with a single short sentence and a single-line SQL query template? If yes, Turbo Mode is appropriate.

Limitations

  • Unsuitable for multi-step or exploratory workflows

  • May miss domain nuances captured in the standard reasoning path

  • Provides limited explanation and simplistic visuals

Effective Prompts

  • "How many active users signed up last week?"

  • "List the five most expensive orders."

  • "Show the total revenue for March 2025."

  • "What is the average session length today?"

get-schemaB

Returns the schema map for the database. Only use this tool after previous attempts fail, or when specifically requested

get-index-mapB

Returns the index map for the database. Only use this tool after previous attempts fail, or when specifically requested

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

B3.3/5.0

Scored across 4 tools

Disambiguation4/5

The two metadata tools (get-index-map, get-schema) are clearly distinct. The two query tools (query-database, query-database-turbo) serve different complexity levels, but their overlapping purpose could cause confusion if the agent misjudges the query difficulty.

Naming Consistency5/5

All tool names follow a consistent hyphenated lowercase pattern: get for metadata retrieval and query for querying, with a suffix for the turbo variant. The naming is uniform and predictable.

Tool Count5/5

With 4 tools covering metadata retrieval and two query modes, the count is well-scoped for a database server. No unnecessary tools, and each serves a distinct purpose.

Completeness3/5

The tool surface covers schema/index inspection and both simple and complex querying. However, it lacks write operations (insert, update, delete) and explicit table listing, which are notable gaps for a comprehensive database server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources