Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEEPSEEK_API_KEYNoRequired when RESEARCH_BRIDGE_RVA_PROVIDER is set to DEEPSEEK_NATIVE_V1.
CONTROL_PLANE_API_KEYNoAPI key used for the optional OpenAI Secure MCP Tunnel connection.
RESEARCH_BRIDGE_DATA_DIRNoDirectory for the SQLite state database and research knowledge data.~/.research-bridge
RESEARCH_BRIDGE_AUDIT_DIRNoDirectory for audit logs..agents/audit/bridge
RESEARCH_BRIDGE_REPO_ROOTNoThe target Git repository that Codex operates on.current working directory
RESEARCH_BRIDGE_TUNNEL_IDNoTunnel ID used for the optional OpenAI Secure MCP Tunnel connection.
RESEARCH_BRIDGE_CODEX_MODELNoDefault model used by Codex.gpt-6-astra
RESEARCH_BRIDGE_RVA_PROVIDERNoRVA provider to use. Set to DEEPSEEK_NATIVE_V1 to enable native DeepSeek RVA.CLAUDE_CODE_LEGACY_V1
RESEARCH_BRIDGE_ALLOW_NETWORKNoWhether to allow task requests to access the network.0
RESEARCH_BRIDGE_ALLOWED_MODELSNoComma-separated list of models that callers may select.gpt-6-astra
RESEARCH_BRIDGE_RVA_CLAUDE_PATHNoOptional path to the Claude Code executable when using the legacy Claude Code RVA provider.
RESEARCH_BRIDGE_RVA_DEEPSEEK_MODELNoOptional model name for DeepSeek RVA requests.
RESEARCH_BRIDGE_ALLOW_WORKSPACE_WRITENoWhether to allow task requests to write to the workspace.0
RESEARCH_BRIDGE_RVA_DEEPSEEK_ENDPOINTNoOptional endpoint for DeepSeek RVA requests.
RESEARCH_BRIDGE_WORKER_READ_CONCURRENCYNoMaximum number of parallel read-only tasks for the same repository.4

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": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
bridge_healthA

Check bridge configuration and target repository connectivity.

repo_snapshotA

Return the target repository branch, commit, dirty status, and top-level entries.

repo_readB

Read a bounded line range from a UTF-8 text file inside the target repository.

repo_searchB

Search text files under the target repository without leaving its root.

codex_start_taskA

Start a background Codex turn. EXECUTION_ONLY workstreams require accepted_handoff_path/sha256 and explicit next_workstream: TASK with exact task_id/task_ref or NONE. Omission and legacy next_workstream_task_* inputs are errors. Uses TRUSTED_EXECUTOR_AUTO_ADVANCE with worker-owned DoD and mechanical pointer-only closure. RESEARCH retains candidate/review/RVA acceptance. Without workstreams, completion_policy is MANUAL, BRIDGE_AUTO_MACHINE_VERIFIED, or BRIDGE_AUTO_TRIVIAL; execution-only with zero required obligations defaults to trivial, required obligations to MANUAL.

research_cycle_statusC

Return the durable research-cycle artifacts, gate settlements, reviews, and linked finite Codex tasks.

research_knowledge_statusB

Read the authoritative research graph/ledger snapshot and separately listed migration candidates.

research_publish_knowledgeA

Required post-result step for a research cycle. Call this exact tool after the latest ResultClaim has an acceptable settled mandatory RESULT_REVIEW and before any follow-up decision, next-experiment proposal, cycle closure, or linked execution. task_id MUST be the latest execution task UUID (the latest executionTaskIds entry / ResultClaim.executionTaskId), never the research cycle UUID. Use PUBLISH_AUTHORITATIVE to project the reviewed ResultClaim into deterministic Evidence and publish it directly to the authoritative Knowledge Graph. Use NO_KNOWLEDGE_TO_PUBLISH only when no reusable knowledge exists and provide a non-empty reason. The same action is idempotent, and no separate confirmation is required.

research_migration_scanA

Offline bounded scan of the target repository (default) or bridge-owned data. Extracted artifacts remain PROPOSED.

bridge_artifact_writeA

Atomically persist a text or structured reconstruction/source-registry artifact under an allowed bridge-owned data namespace.

research_migration_resolveA

Explicitly confirm or reject one PROPOSED migration candidate with an auditable actor and reason.

rva_review_contractC

Submit a new or revised typed Research Contract without RVA review; the updated contract is persisted and the task is queued for execution.

rva_challenge_resultB

Backward-compatible alias: record any typed result disposition and queue the generic mandatory result-review gate.

rva_review_resultA

Record a FAVORABLE, NULL, ADVERSE, INCONCLUSIVE, or FEASIBILITY_ONLY result bound to the latest completed execution and canonical artifact hashes, then queue mandatory RVA result review.

research_record_followup_decisionA

After settled result review, explicitly record NO_NEXT_EXPERIMENT or DEFERRED. Formal NEXT_EXPERIMENT_PROPOSED is recorded by rva_review_next_experiment and must settle before closure/linking.

research_record_settlement_decisionA

Record the orchestrator's content-based conclusion and next step, bound to the latest settled gate outcome. Required after scientific RVA budget exhaustion before publication, closure, or next execution. Address every objection from both rounds with evidence, preserve unsupported conclusions, and bound any experiment. A decision cannot clear a FAIL_CLOSED provider-failure gate; use rva_retry_unavailable_review after provider recovery.

rva_retry_unavailable_reviewA

Explicitly retry the latest RESULT_REVIEW or NEXT_EXPERIMENT_REVIEW after a FAIL_CLOSED RVA provider failure. The original artifact and failure remain auditable. A settlement decision, including BOUNDED_EXPERIMENT, cannot replace a successful RVA review. Scientific review rounds retain their original limit.

rva_review_next_experimentB

Record a next-experiment proposal. Each execution step permits at most two RVA rounds across revisions. The final rejecting round releases the gate immediately while preserving objections; record research_record_settlement_decision before linking execution.

codex_send_followupA

Send a correction immediately to the active Codex turn. awaiting_closure accepts followups and invalidates prior verdict/obligation settlements; completed rejects followups (create a new task). If no turn is active, start a follow-up on the same thread when execution gates permit. Inspect followup.steered or followup.delivery_failed events for delivery confirmation.

codex_statusA

Return persisted task plus execution_status, execution_binding (run_id/generation), closure_status, closure_blockers and exact next_workstream TASK/NONE decision (null for legacy/missing/not applicable; never inferred). DRAINED/awaiting_closure consumes no executor slot. COMPLETED means manual or bridge policy closure. AUTO_BLOCKED reports stable verifier reasons; legacy/v1 stays manual without fabricated acceptance.

codex_eventsA

Read ordered, append-only bridge and Codex events after a sequence cursor.

codex_diffB

Return the current repository-wide staged and unstaged diff plus the task baseline reference.

workstream_accept_candidateA

Trusted ChatGPT/bridge governance only. Accept a reviewed agent-workstream-context-v1 CANDIDATE, create its immutable accepted handoff, and atomically advance the configured target repository. Requires a persisted chatgpt.review ACCEPTED JSON binding candidate, prior current SHA-256/revision/handoff, and next task. Task completion/auto-close never authorizes this action. Repeating the same committed transition is idempotent.

codex_record_audit_eventA

Trusted ChatGPT/bridge governance only. final_verdict content: JSON {verdict: ACCEPTED|REJECTED|NEEDS_REVISION, reason?: string}. completion_obligation_settled: JSON {obligation_id: string, evidence_ref: string}. task_closed atomically requires ACCEPTED, settled obligations, drained execution and research gates. bridge.test_evidence machine payload: JSON {version:1, run_id:string, generation:integer, evidence_key:string, status:PASS|FAIL, exit_code:integer}, using current codex_status execution_binding. Both PASS and exit_code=0 are required for command verification. Legacy prose is audit-only. Executors cannot certify evidence or acceptance. Duplicate closure is idempotent.

codex_auditB

Read a bounded page of machine-readable audit events and report their research-bridge paths.

codex_artifactsB

Check expected artifact paths and list all currently changed repository paths.

codex_abortA

Request cancellation of a queued or running Codex task.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 27 tools

Disambiguation4/5

Most tools are clearly distinct with specific purposes (e.g., repo_read vs repo_search, codex_status vs codex_events). However, a few pairs like rva_challenge_result/rva_review_result and research_record_followup_decision/research_record_settlement_decision are close in function and could be misselected without careful reading.

Naming Consistency4/5

Tool names consistently use snake_case with domain-specific prefixes (repo_, codex_, research_, rva_, bridge_, workstream_), and most follow a verb_noun pattern (e.g., repo_read, codex_start_task). The consistency is strong, though some longer names like research_record_settlement_decision mix multiple nouns but remain readable.

Tool Count2/5

With 27 tools, the surface is heavily populated for a single server. Even for a complex research-bridge system with Codex integration, the count exceeds the typical threshold and may overwhelm agents, increasing the risk of misselection and cognitive load.

Completeness4/5

The tool set covers the full workflow: repository inspection, Codex task lifecycle (start, status, events, abort, followup), research cycle status, knowledge publishing, migration handling, RVA reviews, and governance actions. Minor gaps exist (e.g., no direct tool for reading knowledge graph entries, only status), but the core lifecycle appears complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues