Advertise
MCP.so
Sign In

Scenic MCP - Input Control for Scenic Applications

@scenic-contrib

Repository

Basic information

Category

Other

Transports

stdio

Author

scenic-contrib

About Scenic MCP - Input Control for Scenic Applications

an EXPERIMENTAL implementation of an MCP server for Scenic apps.

#scenic#mcp#input-control

Scenic MCP - Input Control for Scenic Applications config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "scenic_mcp_experimental": {
      "command": "node",
      "args": [
        "src/index.ts"
      ]
    }
  }
}

Scenic MCP - Input Control for Scenic Applications tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Scenic MCP - Input Control for Scenic Applications?

It is an MCP server that enables external keyboard and mouse input injection into Scenic GUI applications, allowing remote control via any MCP-compatible client.

How to use Scenic MCP - Input Control for Scenic Applications?

Add the dependency to your Scenic application's mix.exs and install Node.js dependencies. Start the Elixir server and run the MCP server. Invoke MCP tools like send_keys, send_mouse_move, and send_mouse_click from an MCP client.

Key features of Scenic MCP - Input Control for Scenic Applications

  • Send text and special keys to Scenic applications
  • Move mouse cursor and click at specific coordinates
  • Works with any MCP-compatible client (Claude Desktop, etc.)
  • TCP-based connection for low-latency input
  • Uses proper Scenic ViewPort input routing

Use cases of Scenic MCP - Input Control for Scenic Applications

  • Automating GUI testing in Scenic applications
  • Remote control of Scenic interfaces from AI assistants
  • Integrating Scenic apps with external automation workflows

Frequently asked questions

1

What are the runtime requirements?

Elixir/OTP 24+, Node.js 18+, and Scenic 0.11+ are required.

2

How does it communicate with Scenic?

It uses a TCP-based connection (port 9999) to an Elixir GenServer bridge that sends inputs via Scenic.ViewPort.Input.send/2.

3

Can I send keyboard modifiers?

Yes, the send_keys tool supports modifiers like ctrl, shift, alt, cmd, and meta.

4

Is this server compatible with any MCP client?

Yes, it works with any MCP-compatible client such as Claude Desktop.

5

What transport protocol does it use?

The MCP server uses TCP for real-time communication.

Comments

More Other MCP servers

P

PickFu MCP

PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct

Volley.sh

Volley

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi

Yuppsy

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code

Activepieces

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

23.2K

Codelf

unbug

A search tool helps dev to solve the naming things problem.

14.2K
Advertise