Skip to main content

mekara mcp

Run mekara as an MCP (Model Context Protocol) server for Claude Code integration.

Usage

mekara mcp

Description

Starts mekara as an MCP server that provides script execution tools to Claude Code. This command is typically not invoked directly by users—instead, it's configured in ~/.claude.json so Claude Code launches it automatically.

For project-level customization workflows, see Customizing Bundled Content.

MCP Tools

The server exposes five tools via FastMCP:

Script execution flow:

  • start(name, arguments) - Start executing a script. Runs auto steps until first LLM step, NL script, or completion.
  • continue_compiled_script(outputs) - Continue after completing an LLM step in a compiled script. Pass an empty dict when no outputs are expected. Errors if an NL script is pending.
  • finish_nl_script() - Signal completion of a natural language script. Errors if an LLM step (not NL script) is pending.
  • status() - Get current execution state including pending step info (uses the pending step's format() method for display).
Why Separate Tools for Compiled vs NL Scripts?

LLMs often get confused when executing an NL script, and will call continue_script after completing a single step of the NL script instead of only calling it to signal completion. As such, in order to:

  1. ensure that LLMs are aware of the different semantics around continuing versus completing scripts, and
  2. ensure a clean mental model for the humans maintaining the code

we separate the two actions into two very clearly separate domains.

Project customization:

  • write_bundled(name, force) - Write a bundled skill or standard to the local .agents/ directory for project-level customization. Auto-detects whether name refers to a skill (written to .agents/skills/) or a standard (written to .agents/standards/). Use the standard: prefix to force standard lookup when the name is ambiguous. Used by the /customize command to get bundled source on disk for editing. See Customizing Bundled Content for the full workflow. Errors if a local override already exists (unless force=True).

Configuration

When you run mekara install hooks or mekara install, it creates this configuration in ~/.claude.json:

{
"mcpServers": {
"mekara": {
"command": "mekara",
"args": ["mcp"]
}
}
}

Claude Code reads this configuration on startup and launches the MCP server automatically.

When to Use

You typically don't need to run this command manually. It's automatically started by Claude Code when configured via mekara install hooks.

See Also