Emuluxe

io.github.EmuluxePublished by GitHub account Emuluxev1.1.1Updated Oct 24, 2026

Launch and verify high-fidelity mobile simulations from an AI agent.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant launch and verify high-fidelity mobile simulations on the Emuluxe platform.

What you can do
This MCP server connects an AI assistant to Emuluxe so it can launch and verify high-fidelity mobile simulations. It is offered both as a remote endpoint and as a local npm package run over stdio. The manifest does not list individual tools, so the exact operations are not documented here. Configuration covers the platform URL, a default network profile, and the client environment.
When to use it
Reach for it when you want an assistant to start mobile simulations and check their results as part of a development or testing workflow, rather than driving a device or emulator by hand. It fits teams already using Emuluxe who want that platform reachable from an agent. If you do not use Emuluxe or need documented tool-level control, look elsewhere.
Requirements
A remote endpoint at or a local process run with npx from the npm package @emuluxe/mcp-server over stdio. Authentication is required: a bearer token passed as EMULUXE_TOKEN or in the Authorization header, obtained from the Emuluxe dashboard under Integrations > CLI Access Tokens. Optional settings include EMULUXE_API_URL (defaults to EMULUXE_DEFAULT_NETWORK (defaults to no-throttle), and EMULUXE_IDE, which is detected automatically. Network and a
Before you install
Requires a secret token, supplied as EMULUXE_TOKEN or as the Authorization header (bearer plus the token), so treat it as a credential and avoid exposing it in logs or shared configuration. The server can launch and verify simulations, which are actions taken on the Emuluxe platform under your account; confirm what runs and what is changed before letting an assistant invoke it. No payment, wallet, or private-key handling is described in the available material.

Installation

In SourceWeft

  1. Open Emuluxe in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Emuluxe%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "emuluxe": {
      "type": "http",
      "url": "https://app.emuluxe.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.1LatestOct 10, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.