MartinLoop — Stop Runaway Loops, Bad Code & Token Waste
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| martin_runA | Execute a governed Martin Loop run on a coding task and return the run summary, spend, artifact rollup, and verification state. This hard-blocks until martin_doctor, martin_estimate, martin_plan, and martin_preflight receipts exist for the same task. |
| martin_inspectA | Summarise Martin Loop run records from a saved loop file or run-store directory. |
| martin_statusA | Return the current budget and cost state of a Martin loop record. |
| martin_doctorA | Read-only environment and run-store diagnostics for the Martin MCP server. This is the expected first call before governed work begins. |
| martin_planA | Read-only planning step that turns an objective into a scoped implementation plan, verifier proposal, policy pack, and risk recommendation. Use before preflight and before any real coding run. |
| martin_preflightA | Read-only validation of a planned Martin run before any execution or spend. This is the last required step before martin_run. |
| martin_logsB | Read recent Martin loop events, ledger entries, and operator control receipts for live observability. |
| martin_pauseA | Record a durable pause request for a Martin run so humans and runtimes can see that execution should pause before risky follow-up work. |
| martin_cancelA | Record a durable cancellation request for a Martin run. This writes a control receipt; it does not silently kill a process without evidence. |
| martin_continueA | Record a durable continue or resume request for a Martin run after a human pause or approval checkpoint. |
| martin_list_runsA | List recent Martin runs from the run store with lightweight filters for status, lifecycle, engine metadata, and recency. |
| martin_triage_runsA | Prioritize Martin runs that need operator or agent attention based on verification, lifecycle, and budget pressure. |
| martin_get_runA | Load one Martin run and return its budget, cost, verification, artifact, and canonical path summary. |
| martin_get_attemptA | Load one Martin attempt summary with artifact directory references for a canonical run. |
| martin_get_verification_resultsB | Load verification evidence for a Martin run from stored loop events and ledger entries. |
| martin_run_dossierA | Return the full governed execution dossier for one Martin run, including attempts, events, artifacts, and related discovery surfaces. |
| martin_dossierA | Alias for martin_run_dossier with support for JSON, Markdown, or GitHub PR formatting. Use after martin_run to understand what happened and whether the result is actually safe to trust. |
| martin_evalC | Grade a Martin run for task completion, verifier health, diff discipline, risk, and reviewability. |
| martin_pr_summaryC | Generate a PR title and body with a MartinLoop dossier block for a completed run. |
| martin_create_prA | Create or preview a GitHub PR with a MartinLoop dossier body. Use execute=true to actually call gh. |
| martin_review_prC | Review a PR or PR draft against the Martin dossier and evaluation evidence. |
| martin_estimateA | Estimate the cost, recommended route, and Pre Work Burn for an objective without spending anything. Use before martin_run to understand what a task will cost. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| martin_start | Start a governed agent workflow with the smallest safe Martin context. [server 0.3.2, discovery 2eda35200174] |
| martin_preflight | Prepare the exact preflight payload and safety envelope before a governed run. [server 0.3.2, discovery 2eda35200174] |
| martin_triage | Prioritize run-store failures and choose the next inspection surface. [server 0.3.2, discovery 2eda35200174] |
| martin_resume | Resume from a prior run safely using compact evidence before spending another attempt. [server 0.3.2, discovery 2eda35200174] |
| martin_prove | Build a proof-first receipt from the latest or selected Martin run. [server 0.3.2, discovery 2eda35200174] |
| martin_release_check | Run a release-readiness review using Martin MCP discovery and evidence surfaces. [server 0.3.2, discovery 2eda35200174] |
| martin_governed_coding_kickoff | Frame a governed Martin Loop coding request before preflight or execution. [server 0.3.2, discovery 2eda35200174] |
| martin_debug_failed_run | Diagnose a failed or degraded Martin run using persisted run, attempt, and verification data. [server 0.3.2, discovery 2eda35200174] |
| martin_publish_readiness_review | Run a findings-first publish-readiness review for the Martin MCP package. [server 0.3.2, discovery 2eda35200174] |
| martin_triage_run_store | Prioritize persisted Martin runs and decide which one to inspect or debug next. [server 0.3.2, discovery 2eda35200174] |
| safe_bug_fix | Plan a small scoped bug fix through doctor, plan, preflight, run, and dossier. [server 0.3.2, discovery 2eda35200174] |
| write_tests_first | Constrain the plan around failing tests first, then a small fix. [server 0.3.2, discovery 2eda35200174] |
| small_refactor | Keep a refactor small, verifier-backed, and path-scoped. [server 0.3.2, discovery 2eda35200174] |
| security_review | Review a risky change with Martin risk, scope, and verifier evidence first. [server 0.3.2, discovery 2eda35200174] |
| pr_review | Generate a Martin-aware PR review checklist with dossier and eval evidence. [server 0.3.2, discovery 2eda35200174] |
| release_check | Run a release-readiness check grounded in Martin evidence. [server 0.3.2, discovery 2eda35200174] |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| martin_server_health | Health and environment readiness for the Martin MCP server. |
| martin_recent_runs | Recent Martin loop previews derived from the current runs root. |
| martin_run_triage | Priority-ranked Martin runs that likely need attention. |
| martin_latest_run | Full latest-run dossier surface for agents that need more than the compact summary. |
| martin_latest_summary | Compact latest-run summary for context-constrained agents. |
| martin_latest_receipt | Canonical structured receipt for the latest run; use this before optional proof-card views. |
| martin_latest_proof_card | Optional Markdown proof view derived from the latest receipt. |
| martin_latest_budget_status | Compact budget, token, and stop-condition snapshot for the latest run. |
| martin_latest_verifier_evidence | Compact verifier evidence and warnings for the latest run. |
| martin_latest_rollback_evidence | Compact rollback and artifact evidence for the latest run. |
| martin_current_policies | Local policy-pack presets and the recommended default pack for the current repo. |
| martin_repo_risk_map | Sensitive repo surfaces and the recommended policy pack for this workspace. |
| martin_latest_verifier_results | Latest verifier results alias for compact run evidence. |
| martin_agent_next_step | Single next recommended Martin tool, prompt, or resource for a context-constrained agent. |
| martin_mcp_usage_guide | Recommended workflow for using Martin Loop over MCP. |
| martin_agent_start_guide | Short agent-facing guide for using Martin with minimal context and low tool bloat. |
| martin_command_map_guide | Command-by-command guide for choosing the right Martin tool or surface. |
| martin_ide_onboarding_guide | IDE-facing setup guide for making MartinLoop part of the default MCP workflow. |
| martin_operating_rules_guide | Built-in operating rules that tell agents when Martin commands must be used before work proceeds. |
| martin_publish_readiness_guide | Checklist-oriented guide for MCP publish readiness reviews. |
| martin_governance_status | Proactive governance status: whether work is governed, budget remaining, unreceipted runs, and recommended next action. Read this before starting agent work. |
| martin_memory_summary | MartinLoop persistent memory: user preferences, consent signals, budget patterns, and behavioral observations aggregated over time. Read at session start to personalize recommendations. |
| martin_mode_status | Current Martin working mode (auto, plan, or edits) and consent state. Read before starting agent work to confirm whether the user expects autonomous execution, plan approval, or per-edit review. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/Keesan12/martin-loop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server