메뉴
Use when working on APXM MCP surfaces: the Rust HTTP `/v1/mcp` endpoint, the Rust stdio `mcp-server` binary, or cross-agent MCP registration. Prefer server-owned HTTP MCP for workflow/orchestration control.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | mcp-server |
| description | Use when working on APXM MCP surfaces: the Rust HTTP `/v1/mcp` endpoint, the Rust stdio `mcp-server` binary, or cross-agent MCP registration. Prefer server-owned HTTP MCP for workflow/orchestration control. |
Load _shared/apxm-development-rules.md before broad work.
APXM has two Rust MCP surfaces:
apxm-server exposes HTTP MCP at POST /v1/mcp. This is the
server-owned control plane for long-running workflows, retained events,
cancellation, server-owned sessions, skill inventory, and orchestration.mcp-server exposes stdio MCP for compile/query/debug tools. It does
not own background workflow sessions or orchestration state.MCP should stay a thin interface over APXM server/runtime capabilities.
validate, compile, ops_list,
run, prompt_as_workflow, trace_fetch, aam_recall,
evidence_lookup, capability_discovery.skills_list, skill_get, skill_validate,
skill_call.workflow_start, workflow_status,
workflow_events, workflow_cancel.The stdio binary exposes compile/query tools such as validate,
compile, get_contract, analyze, prompt_as_workflow,
trace_fetch, aam_recall, evidence_lookup, and
capability_discovery. Use HTTP MCP when a caller needs workflow start/status,
events, cancel, or orchestration.
dekk agents mcp install # registers with supported agent configs
# (Claude Code, Cursor, etc.)
The installation path is owned by tools/scripts/apxm_mcp_install.py.
Do not bypass it.
execution_id, session_id,
session_dir, workflow_path, and retained event cursors. Do not invent
shell process handles for server-managed runs.api_key or
LLM_GATEWAY_KEY as a tool argument.dekk agents build-server — compile the HTTP and stdio MCP binaries.dekk agents mcp install — register; surfaces config errors.A new surface spans the handler, route/tool registration, the MCP manifest, the
Dekk wrapper, and a smoke test — miss one and it ships half-wired. A REST route
that should also be an MCP tool needs both the handler and the tool wrapper
(don't ship REST-only). Route paths, env names, response markers, and tool names
are contract strings — keep them in contract.rs / apxm.contract, not as
handler literals.
Use when changing APXM compiler frontends: Rust AirModule, TypeScript @apxm/frontend, Python apxm, frontend codegen, or Studio/source lowering into AIR.
Use when rebasing the external/vllm fork onto a new upstream tag, cherry-picking APXM commits, or resolving conflicts in the fork. Covers the G1 build/smoke gate.
Commit gate — runs simplify + finish first, drafts message in repo log style, lints it with dekk agents commit-lint, commits at a clean stopping point, and pushes only when authorized. Never --force. Does not open PRs.
Use when editing conceptual docs under docs/. Gates two shipped failure modes — overclaim (present-tense prose about unwired behaviour) and citation drift (claims with no anchor to shipped code).
Use when registering a new APXM inference backend (cloud, on-prem, or local). Enforces hard-fail-at-config-time resolver behavior.
Use when adding, modifying, or reordering MLIR passes in the APXM compiler pipeline. Enforces the single pass-list source of truth, the AIS-core ownership rule, and the build-dialect + codegen cadence after .td edits.