Skip to main content
Glama
arale-code

arale-code

Official
by scalacore

arale-code

Local engineering guidance for coding agents, served through MCP. arale-code gives an agent four reusable instructions, a control Guide and 20 software engineering procedures. The server provides documents; the agent decides what to do with them under its own tools and permissions.

An original guide character holding a book and pointing to three procedure cards

Read the Guide, choose one procedure, then read its full document.

Find the right procedure

  1. Connect an MCP client to the local STDIO server.

  2. Read arale://procedure/guide for the selection rules, or call list_procedures to discover IDs and resource URIs.

  3. Read the selected procedure in full, then apply it to the user’s task within the agent’s existing permissions.

For example, call the list_procedures MCP tool with an empty argument object:

{}

It returns a JSON string whose first entry is the Guide (excerpt; the full documents array has 21 entries):

{"schema_version":1,"documents":[{"id":"guide","code":"GUIDE","title":"Control Guide","kind":"guide","uri":"arale://procedure/guide"}]}

Read that URI as an MCP resource to get the YAML Guide. Its meta.id is GUIDE and its meta.version is '1.7'. The example shows catalog discovery; it does not cause the server to edit a project.

Related MCP server: CodeContext MCP

Get started

You need Python 3.12 and uv, with the locked dependencies available locally. From the repository root, prepare the environment without a network request:

uv sync --locked --offline --no-python-downloads

Then follow INSTALL.md to register one client and check its live MCP connection. It documents Codex CLI, Claude Code, Cursor, OpenCode and Antigravity CLI, including the local launch command. An offline sync can fail if Python or a locked dependency is missing from the local cache; the installation guide explains what to check before downloading anything.

What is included

Interface

Contents

Tools

list_instructions, list_procedures

Catalog resources

instructions://catalog, arale://catalog

Resource templates

instructions://document/{id}, arale://procedure/{id}

Prompt

apply_instruction with an instruction id and a nonempty task

The bundled documents are four Markdown instructions, one YAML Guide and 20 YAML procedures. See the MCP contract for exact IDs, response shapes and errors.

Boundaries and verification

The server is read-only and stateless. It serves bundled guidance over local STDIO; it does not execute procedures, grant permissions or make outbound network requests. The consuming agent remains responsible for any project changes.

Repository tests and an isolated local STDIO package check have verified the bundled interface and Guide 1.7 assets. The five client paths in INSTALL.md are documented installation paths; live discovery in each client has not been verified here. See the verification contract for the checks required after client registration.

Develop and contribute

Prepare the locked environment as above, then run the repository’s quality gates:

uv run ruff check .
uv run ruff format --check .
uv run mypy src tests
uv run pytest

For changes to the MCP interface or bundled documents, read the server contract and quality gates, and include the relevant verification with your proposed change. For installation questions, start with INSTALL.md.

License and maintainer

Maintained by Scala Core. Licensed under Apache 2.0; see NOTICE for attribution.

Available Tools

2 tools
list_instructionsList InstructionsA
Read-onlyIdempotent

List valid engineering-instruction IDs and their resource URIs. Call this before requesting an instruction when the ID is not already known.

Inputs: no named parameters. Returns: result

list_proceduresList ProceduresA
Read-onlyIdempotent

List the Arale control guide and procedures with their IDs and resource URIs. Call this before reading a procedure when the ID is not already known.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are mostly distinct: one lists procedures/control-guide entries and the other lists engineering-instruction IDs. They share a very similar list-by-ID/URI pattern, but the descriptions make the resource type clear enough to avoid most confusion.

    Naming Consistency5/5

    Both tools follow the same predictable list_noun convention. There are no naming inconsistencies across the set.

    Tool Count3/5

    Two tools is thin for a server surface, and both only list identifiers rather than offering broader procedure/instruction interaction. The count is borderline rather than clearly wrong, but it feels under-scoped.

    Completeness2/5

    The surface only lists procedure and instruction IDs/URIs; there are no tools to actually read, fetch, or operate on a procedure or instruction. Descriptions imply later reading/requesting, but the tool set does not provide those operations, creating a significant dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search local repositories and retrieve bounded, cited source chunks, look up full indexed chunks, and inspect index statistics through read-only MCP tools over stdio.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read, navigate, and query long-term memory stored as readable, reviewable source files, exposing paged catalogs, indexed searches that explain their misses, bounded relation traces, link diagnostics, raw file access, and preflight checks of drafts against MUST constraints. It serves this read-only by default over stdio so any MCP client can start from a memory catalog and keep reading toward the answer instead of relying on a single similarity guess.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to consult a project's Git-versioned Markdown knowledge base over local stdio — checking knowledge health, listing the catalog, searching topics, and reading guides before acting. Access stays read-only, so project guidance, decisions, and lessons learned remain shared with human teammates and traceable beside the code.
      4
      1
      MIT