Skip to main content
Glama
kroq86

Runtime Copilot MCP Server

by kroq86

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORKSPACE_ROOTNoRoot directory for workspace operations./workspace

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
init_engineD

Initialize persistent engine storage.

insert_rowC

Insert one row into the persistent engine.

upsert_rowC

Upsert one row by order_id.

create_indexC

Create customer index for engine table.

explain_customerC

Run EXPLAIN ANALYZE style output by customer filter.

reindex_projectC

Re-index this project dataset (engine_cli index).

run_e2e_flowC

Execute full MiniPG + MiniDatabricks + DuckDB end-to-end flow.

explain_runC

Explain one recorded run_id from the local trace store.

demo_explain_runC

Run a traced demo flow, then explain the run immediately.

demo_explain_run_failureC

Run a traced failing flow, then explain the failed run immediately.

demo_explain_semantic_failureC

Run a traced semantic-corruption flow and explain the failed validation.

demo_explain_idempotency_conflictB

Run a traced idempotency-conflict flow through WriteCore.

demo_explain_concurrency_failure_stormC

Run a traced concurrency conflict plus failure-storm scenario.

explain_regression_suiteC

Run regression checks and return explain output for each traced run.

record_tool_traceC

Append one MCP tool trace record to local trace store.

similar_incidentsC

Find semantically similar historical incidents.

refresh_trace_pathC

Incrementally ingest new lines from source path into trace store.

refresh_docs_pathC

Incrementally ingest project docs, code, and config files.

memory_upsertC

Upsert one operational memory entry for semantic recall.

memory_searchC

Search memory entries by semantic similarity and metadata filters.

health_checkC

Run a quick MCP smoke flow and summarize status.

benchmark_callsC

Benchmark MCP operations with SLO-style summary metrics.

scenario_load_testD

Mixed workload load test: insert/upsert/explain/reindex/e2e and summary metrics.

capture_roi_baselineC

Capture baseline KPI snapshot for ROI Phase 0.

report_drift_bugC

Increment and persist split-logic drift bug counter.

decision_gateC

Evaluate migration triggers and return pass/fail gate.

project_manifestB

Describe project state roots, schemas, and supported regression primitives.

project_capabilitiesB

Return declared runtime capabilities and contract coverage.

project_tool_catalogB

Return the full MCP tool catalog with groups, entrypoints, and summaries.

project_get_defaultsA

Return default workspace, paths, runtime mode, and project metadata.

project_run_regressionD

Run the explain-first regression bundle and return a unified verdict.

project_capture_baselineC

Capture a baseline snapshot and return a unified verdict envelope.

project_compare_baselineC

Compare current benchmark/scenario results against a stored baseline.

project_list_entitiesC

List declared project entities from the generic state store.

project_get_entityC

Load one declared project entity by identity key.

project_upsert_entityC

Create or update a declared entity in the generic state store.

project_delete_entityC

Delete a declared entity from the generic state store.

project_append_eventC

Append a generic project event to the local event log.

project_ingest_traceC

Append one normalized trace record through the generic project ingest path.

project_explain_runC

Read one run explanation through the generic project explain entrypoint.

project_export_stateC

Export generic project state as a JSON snapshot.

project_list_heuristicsA

List declared heuristic profiles available for generic project analysis.

project_run_heuristicC

Run one declared heuristic profile over a source and persist the analysis through project state.

schema_load_toolA

Ingest DDL from file or raw text, validate with DuckDB, store metadata in project state (schemas/).

schema_explain_toolB

Run EXPLAIN for each profile in query_profiles_json (JSON: name -> SQL). Optional seed_sql_json (JSON array of SQL) runs before EXPLAIN. Writes explain_.txt.

schema_evaluate_toolB

Build verdict from schema metadata and EXPLAIN outputs; write evaluation_report.json and verdict.md. If query_profile_names empty, discovers explain_*.txt in artifacts.

schema_evaluate_full_toolC

One-shot: load schema → run EXPLAIN (from query_profiles_json/seed_sql_json) → evaluate. Generic: you supply queries and optional seed SQL.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kroq86/data-engineering-runtime-lab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server