Skip to content
MCP server

Azahar 3DS emulator

MCP server and CLI to automate testing of 3DS homebrew in the Azahar emulator

Runs locally
Install
Pricing
Open source
Platforms
CLI, Linux, macOS
Runs
Locally
Version
0.1.0
Listing updated
1 day ago

Similar MCP servers

About Azahar 3DS emulator

Azahar 3DS emulator is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

The README says mcp-azahar is an unofficial tool that drives the Azahar 3DS emulator through its built-in RPC server, letting developers launch homebrew, send button and touch input, capture screenshots, read and write memory, and manage save states. It ships as one Go binary with two front ends: a command-line interface for scripts, CI and shell-using agents, and an MCP server for MCP-compatible clients.

Tests can be written as YAML or JSON sequence files that run without any AI involved. When an ELF with debug info is supplied, variables can be read by name rather than raw address, and asserts or waits can check program state against values in the binary. Sessions are shared between the CLI and the MCP tools so a person can watch an instance an agent is driving.

The project is aimed at homebrew developers and anyone automating 3DS app tests locally or in continuous integration. The README notes that the emulator's RPC port is unauthenticated, so it should be run on isolated networks or inside the provided container.

Install

Run in a terminal

claude mcp add mcp-azahar -- npx -y mcp-azahar

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mcp-azahar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-azahar"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-azahar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-azahar"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-azahar": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-azahar"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-azahar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-azahar"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-azahar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-azahar"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (20)

Taken from the project documentation; the running server may differ.

azahar_launch
Launch an app in an Azahar session.
azahar_attach
Attach to an already running Azahar instance.
azahar_stop
Stop the emulator session.
azahar_status
Show the state of a session.
azahar_sessions
List sessions.
azahar_press
Press a button.
azahar_hold
Hold a button.
azahar_release
Release held input.
azahar_touch
Send a touch input.
azahar_circle_pad
Move the circle pad.
azahar_screenshot
Take a screenshot as PNG.
azahar_save_state
Save an emulator state.
azahar_load_state
Load an emulator state.
azahar_read_memory
Read emulator memory.
azahar_write_memory
Write emulator memory.
azahar_logs
Read session logs.
azahar_symbols
List symbols from an ELF.
azahar_read_symbol
Read a variable by symbol name.
azahar_wait_for
Wait until a target meets a condition.
azahar_sequence
Run a sequence file or inline script.

What it does

Input and touch control
Press, hold and release buttons, send touch coordinates and drive the circle pad from the CLI or MCP tools.
Screenshots and memory access
Capture PNG screenshots and read or write emulator memory with verification by read-back.
Symbol-based state reads
Read C and C++ variables, structs and bitfields by name from a debug ELF instead of by address.
Scripted test sequences
Run YAML or JSON test files with asserts, waits, save states and log checks, with exit codes for CI.
Save states and logs
Save and load emulator states and read or follow app debug output from the session log.
Shared sessions
CLI and MCP clients use the same named sessions, so humans and agents can share one emulator instance.

Good for

  • Automated smoke tests of 3DS homebrew in continuous integration
  • Letting an AI agent launch an app, press buttons and check program state
  • Capturing screenshots of a homebrew build at fixed points in a test run
  • Inspecting or patching memory of a running 3DS app during debugging

Pricing

Open source

Free under GPL-3.0-or-later; you still need Azahar on the host.

Azahar 3DS emulator FAQ

Is this an official Azahar project?

No. The README states it is unofficial and not affiliated with or endorsed by the Azahar project.

Which Azahar version is required?

The README says Azahar 2127.0 or newer is required for RPC input injection and save states.

Which platforms are supported for headless launch?

The README says headless launch needs Linux with Xvfb. On macOS, launch runs on the desktop, and on Windows only attach is supported.

Is the RPC server secure?

The README warns that Azahar's RPC server is unauthenticated and listens on all interfaces on UDP port 45987, so it should be firewalled or run in an isolated container.

Is Azahar 3DS emulator free?

Yes. Azahar 3DS emulator is open source, so you can use and self-host it for free.

How do I add Azahar 3DS emulator to Claude Code?

Run this command in your terminal: claude mcp add mcp-azahar -- npx -y mcp-azahar

What are the best alternatives to Azahar 3DS emulator?

The closest alternatives to Azahar 3DS emulator are adb-mcp: Android emulator and device control over adb, Jidr, Oh My Android, Karagöz and Jidr.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers