Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OLLAMA_MODELNoOllama model name
OPENAI_MODELNoOpenAI model name
OPENAI_API_KEYNoOpenAI API key for generation
ANTHROPIC_MODELNoAnthropic model name
OLLAMA_BASE_URLNoOllama base URL
OPENAI_BASE_URLNoOpenAI base URL
ANTHROPIC_API_KEYNoAnthropic API key

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
orangepro_list_agentsA

List all configured OrangePro agents for a tenant. Use this first to discover available agents before getting details or triggering runs. Returns agent_id, name, type, status, and last run timestamp for each agent.

orangepro_get_agentA

Get full detail, configuration, timeline, and recent runs for a specific OrangePro agent. Use after orangepro_list_agents to inspect a particular agent. Returns agent config, run history, and current status.

orangepro_run_agentA

Start an OrangePro agent run. Safe to retry — the API returns the active run if one is already in progress. Use this to trigger data ingestion, KG sync, or test generation agents.

orangepro_list_agent_runsA

List recent runs for a specific OrangePro agent. Use to check run history, find failed runs, or verify a recent run completed. Returns run_id, status, start time, duration, and records processed.

orangepro_get_agent_logsA

Read recent log lines for an OrangePro agent. Use to debug failures, check processing details, or verify what an agent did during a run. Returns timestamped log lines.

orangepro_get_agent_healthA

Read health and connectivity status for an OrangePro agent. Use to diagnose why an agent is failing — checks source config, auth, and runtime status.

orangepro_resolve_storyA

Resolve a user story, requirement, or feature description against the OrangePro Knowledge Graph. Returns grounded entities, matched concepts, and confidence scores. Use to verify story coverage or find KG gaps.

get_coverage_gapsA

Find application areas lacking test coverage. Returns a heatmap of critical (red), partial (yellow), and healthy (green) coverage zones with test counts. Use to identify where to generate additional tests.

convert_bug_to_testsA

Analyze a bug report and generate durable regression tests to prevent recurrence. Provide a detailed bug description for best results. Returns root cause analysis, affected areas, and generated test cases with steps.

build_regression_packA

Generate a focused regression test pack for a feature area or recent change. Use after a refactor, migration, or risky change to ensure the area stays stable. Returns a set of test cases targeting the specified area.

explain_quality_riskA

Get a quality risk assessment using coverage heatmap, execution history, and 30-day trend data. Identifies high-risk and medium-risk areas. Use to answer questions like 'are we safe to ship?' or 'what areas need more tests?'

generate_missing_coverageA

Generate test cases for a user story or feature that needs better coverage. Submits a test generation job and polls for results (up to 2 minutes). Returns categorized test cases with steps and expected results.

analyze_pr_riskA

Analyze a pull request for quality risk. Returns overall risk score (0-100), risk drivers, impacted categories, similar historical bugs, coverage gaps, and recommended tests to run. Use before merging to catch regressions.

analyze_release_readinessA

Get a tenant-wide release readiness assessment. Returns a ship/review/block recommendation with confidence score, coverage analysis, execution summary, script readiness, risk areas, recent failures, and recommended actions. Use before deciding whether to release.

generate_test_scriptsA

Convert test cases from a completed test generation job into executable test scripts. Requires a source_job_id from a prior generate_missing_coverage or convert_bug_to_tests call. Generates scripts for Playwright, Cypress, Selenium, or Puppeteer. Use this as the second step after generating test cases to get runnable automation code.

Prompts

Interactive templates invoked by user choice

NameDescription
review_agent_runAnalyze an OrangePro agent run for outcome, failures, and next actions.
debug_failed_agentInvestigate why an OrangePro agent failed or produced no useful graph writes.

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/OrangeproAI/orangepro-mcp'

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