CODE CONTEXT TOOLS

97 tools from the Code Context MCP Server, categorised by risk level.

// ALL 97 CODE CONTEXT TOOLS

READ 54 tools

Read acknowledge_ticket_changes Acknowledge board-edited tickets after reacting to their changes: clears pending_change flags and completes... Read advance_sprint Advance sprint to the next phase. Checks all gates, advances if they pass, returns summary + next actions. ... Read analyze_retro_patterns Analyze retrospective findings across all sprints — category breakdown, recurring issues, and action follow... Read dump_database Export the entire database to JSON for backup/restore Read find_symbol Find which file(s) export a given function, component, type, or constant Read get_agent Get full details of a scrum agent by role Read get_audit_trail Get audit trail for an entity — all state changes over time Read get_backlog List all backlog tickets — unassigned to any sprint or carried over from closed sprints Read get_burndown Get burndown data for a sprint — daily snapshots of remaining vs completed points Read get_changes Get recent file changes grouped by file path, showing what changed (size, lines, exports, summary diffs) Read get_dependency_graph Get all dependencies for a ticket or sprint Read get_discovery_coverage Get coverage report for a discovery sprint — auto-promotes planned discoveries whose linked ticket is DONE Read get_file_context Get a file Read get_mood_trends Get mood history for an agent or all agents — detects burnout patterns Read get_onboarding_status Check project setup status and return what is configured vs missing Read get_project_status Check if the project is properly set up and return health status Read get_resume_state Single-call resume detection. Returns minimal structured data (~150 tokens) for all command Step 0 flows. R... Read get_skill Fetch the full content of a single skill by name (e.g. Read get_sprint Get full sprint details with tickets, bugs, blockers, and retro findings Read get_sprint_config Read the SPRINT_PROCESS skill from the database — returns the current sprint process configuration Read get_sprint_instructions Get sprint process instructions — lifecycle, ticket workflow, retro rules, role responsibilities, and close... Read get_sprint_playbook Get the current sprint playbook: phase, ticket summary, gate status, blockers, and directive next actions. ... Read get_sprint_summary Get a one-line summary per sprint — name, status, velocity, ticket progress. Ultra-compact for quick overvi... Read get_ticket Get full ticket details with subtasks and linked bugs Read get_time_report Get time tracking report for a sprint — estimated vs actual hours per agent Read get_token_usage Get token usage history, optionally filtered by sprint or ticket Read get_user_response Poll for the user Read get_velocity_trends Get velocity trend data across sprints — committed vs completed, completion rate, bugs Read health Check server health and connectivity Read link_discovery_to_ticket Link a discovery finding to its implementation ticket — auto-sets status to planned (or implemented if tick... Read link_ticket_to_epic Link a ticket to an epic, or unlink by passing null epic_id Read link_ticket_to_milestone Link a ticket to a milestone by setting its milestone_id Read list_agents List all scrum team agents with their roles and capabilities Read list_decisions List logged decisions with optional category filter Read list_discoveries List discovery findings with optional filters. Compact by default (open items, truncated one-liners) — pass... Read list_epics List epics with optional status and milestone filters, including ticket progress counts. Use compact=true f... Read list_recent_events List recent events from the audit trail — use this to detect dashboard-initiated changes (e.g. user moved a... Read list_retro_findings List retrospective findings with optional filters Read list_sprints List all sprints with status and ticket counts. Use compact=true for minimal output (id, name, status only)... Read list_tags List all available tags with usage counts Read list_tickets List tickets with optional filters. Use compact=true for minimal output (id, title, status) to save tokens. Read load_phase_context Single-call phase context loader. Bundles all data needed for a specific workflow phase into one response, ... Read log_bug Log a bug against a sprint Read log_decision Log an architectural or process decision with rationale and alternatives considered Read log_event Manually log an event in the audit trail Read log_time Log estimated or actual hours on a ticket Read log_token_usage Record token usage for a session/task. Use at the end of a task to track real consumption for benchmarking. Read query Run a read-only SELECT query against the context database Read record_mood Record an agent Read request_user_input Request user input via the dashboard wizard modal. Writes a question to the bridge action queue. If the das... Read search_files Search indexed files by path or summary (supports % wildcards) Read search_scrum Full-text search across tickets, retro findings, blockers, and bugs Read snapshot_sprint_metrics Capture a daily burndown snapshot for a sprint — records remaining, completed, added, and removed points Read sync_scrum_data Re-seed scrum data from factory defaults (agents + skills). Does not overwrite existing data — only fills e...

WRITE 33 tools

Write add_dependency Add a dependency between two tickets (blocks, blocked_by, or related) Write add_retro_finding Add a retrospective finding to a sprint Write add_tag Add a tag to a ticket (creates tag if it doesn Write create_blocker Report a blocker on a sprint Write create_discovery Log a finding from a discovery sprint Write create_epic Create a new epic to group related tickets Write create_milestone Create a new milestone for the product roadmap Write create_sprint Create a new sprint Write create_ticket Create a new ticket in a sprint Write export_sprint_report Generate a complete markdown sprint report Write export_to_file Export database to a JSON file on disk Write generate_vision_animation Generate project vision animation data (JSON) and provide the Remotion render command Write handle_run_kickoff Handle the /kickoff ceremony triggered from the dashboard. Initiates the full project lifecycle from vision... Write handle_run_retro Handle the retrospective ceremony triggered from the dashboard. Runs retro for the specified sprint. Write handle_run_review Handle the sprint review ceremony triggered from the dashboard. Shows sprint completion summary and demo. Write import_from_file Restore database from a JSON dump file on disk Write plan_sprint Create a new sprint and assign tickets to it in one operation Write resolve_blocker Mark a blocker as resolved Write restore_database Restore database from a JSON dump. Wraps in transaction for safety. Write send_claude_output Stream Claude Write send_claude_step Notify the dashboard wizard about a step transition during a ceremony. Shows step status in the output stre... Write send_step_progress Send real-time step progress updates to the wizard modal. Shows which step Claude is executing and current ... Write set_change_reason Set a reason/explanation for a recorded file change Write set_description Set a manual description for a file (persists across re-indexes) Write set_directory_description Set a manual description for a directory (persists across re-indexes) Write update_discovery Update a discovery Write update_epic Update an existing epic Write update_milestone Update a milestone Write update_skill_sets Enable or disable predefined skill sets (frontend fe:*, landing la:*, workflow wf:*) for this project. Part... Write update_sprint Update sprint status or details Write update_sprint_config Create or update the SPRINT_PROCESS skill — stores sprint process configuration in the database Write update_ticket Update a ticket Write update_vision Create or update the PRODUCT_VISION skill content

DESTRUCTIVE 6 tools

Destructive remove_dependency Remove a dependency between two tickets Destructive remove_tag Remove a tag from a ticket Destructive reset_agents Reset all agents to factory defaults. WARNING: This deletes all current agents and re-seeds from TypeScript... Destructive reset_skills Reset all skills to factory defaults. WARNING: This deletes all current skills and re-seeds from TypeScript... Destructive reset_sprint_process Reset sprint process configuration to factory defaults. Destructive triage_retro_finding Triage an open try_next retro finding at sprint planning: adopt it as a ticket, drop it with a reason, or d...

EXECUTE 4 tools

Execute execute Run an INSERT, UPDATE, or DELETE against the context database Execute index_directory Scan a directory, parse all files, extract metadata/exports and build a dependency graph. Use freshness_che... Execute run_onboarding Run the full project onboarding sequence — checks and fixes all missing setup steps Execute start_sprint Create a sprint with tickets in one call. Creates the sprint, creates tickets from provided list, assigns a...

// FAQ

How many tools does the Code Context MCP server have? +

The Code Context MCP server exposes 97 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Code Context tools? +

Route the Code Context server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Code Context tools fall into? +

Code Context tools are categorised as Read (54), Write (33), Destructive (6), Execute (4). Each category has a recommended default policy.

Enforce policy on every Code Context tool call.

Start from Code Context, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Instant setup, no code required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.