247afk Block Editor MCP Server
The 247afk Block Editor MCP Server enables AI assistants to programmatically build, edit, and manage visual block editor scripts in real-time through a WebSocket bridge connecting to the 247afk script editor in your browser.
Documentation & Inspection: Retrieve full documentation (node types, connection rules, graph format, examples) with
get_docs, and inspect the current script structure (nodes, edges, variables) withget_graph.Full Graph Management: Replace the entire script graph from scratch with
set_graph, or clear all nodes and edges while preserving variables withclear_graph.Node Operations: Add nodes with
add_node, remove nodes and their connected edges withremove_node, update node data withupdate_node_data, reposition nodes withmove_node, inspect a single node withget_node, and auto-arrange nodes by execution flow withauto_layout.Edge Operations: Connect node ports with
add_edgeand delete specific edges by ID withremove_edge.Variable Management: Replace the entire variables list with
set_variables, add or replace a single variable withadd_variable, and remove a variable by name withremove_variable.Validation & Saving: Check for errors or warnings with
validate_graph, and save the script to the server (equivalent to Ctrl+S) withsave_graph.
Compatible with MCP clients such as Claude Desktop, Cline, Cursor, and Gemini CLI.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@247afk Block Editor MCP Server Add a loop to my script that clicks every 5 seconds"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
247afk Block Editor MCP Server
Lets AI assistants (Claude Desktop, Cline, Cursor, and any MCP-compatible client) build and edit block editor scripts in real time.
How it works
The MCP server runs locally and starts a WebSocket bridge on
127.0.0.1:3002Open a script in the 247afk editor, the site will connect to your websocket.
Your ai assistant can now use the MCP server to make changes in scripts.
NPM package -> https://www.npmjs.com/package/247afk-mcp
Related MCP server: screenslick
Install
npm install -g 247afk-mcpGet Started
Codex CLI
codex mcp add 247afk-mcp -- npx -y 247afk-mcpGemini CLI
gemini mcp add 247afk-mcp npx "-y 247afk-mcp"Claude Code
claude mcp add 247afk-mcp -- npx -y 247afk-mcpClaude Desktop
{
"mcpServers": {
"247afk-mcp": {
"command": "npx",
"args": [
"-y",
"247afk-mcp"
]
}
}
}Cursor
paste this in your browser:
cursor://anysphere.cursor-deeplink/mcp/install?name=247afk%20Block%20Editor%20MCP%20Server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIjI0N2Fmay1tY3AiXX0=Manual
Copy configuration below
Add it to your MCP client configuration
Follow your client's specific setup instructions
Restart your MCP client to apply changes
Configuration
{
"mcpServers": {
"247afk-mcp": {
"command": "npx",
"args": [
"-y",
"247afk-mcp"
]
}
}
}Restart antigravity/claude code after saving.
Test without an AI client
npx @modelcontextprotocol/inspector 247afk-mcpOpens a browser UI to call tools manually.
Changelog
1.0.1
Added
update_node_data— merge field values into a node without replacing itAdded
move_node— reposition a node on the canvasAdded
get_node— inspect a single node's type, position, and dataAdded
clear_graph— wipe all nodes and edges while keeping variablesAdded
validate_graph— run client-side validation and return errors/warningsAdded
save_graph— save the script to the server (equivalent to Ctrl+S)Added
auto_layout— auto-arrange nodes left-to-right by execution flowAdded
add_variable— add or replace a single variable without touching othersAdded
remove_variable— remove a single variable by nameFixed variable picker dropdowns being empty in MCP-built graphs
1.0.0
Initial release
Requirements
Node.js 18 or later
247afk account with access to the script editor
Browser open on the script to edit. (on https://247afk.com)
Available Tools
8 toolsadd_edgeB
Connect two node ports with an edge. Use get_graph first to know existing node ids.
Inputs: sourceNodeId (required), sourceHandle (required), targetNodeId (required), targetHandle (required).
add_nodeC
Add a single node to the script editor canvas.
Inputs: type (required), position, data.
get_docsA
Get full documentation for the 247afk block editor, node types, connection rules, graph format, and examples. Call this first before building any script.
Inputs: no named parameters.
get_graphA
Get the current script graph from the open editor tab. Returns nodes, edges, and variables. The editor tab must be open.
Inputs: no named parameters.
remove_edgeC
Remove a specific edge by id.
Inputs: edgeId (required).
remove_nodeB
Remove a node and all its connected edges from the editor.
Inputs: nodeId (required).
set_graphA
Replace the entire script graph at once. Use this to build a complete script from scratch. All existing nodes and edges are replaced.
Inputs: nodes (required), edges (required), variables.
set_variablesC
Replace the script variables list. Existing variables are overwritten.
Inputs: variables (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: add/remove operations for nodes and edges, get operations for docs and graph, and set operations for graph and variables. The descriptions clarify boundaries, such as set_graph replacing everything while add_node adds a single node.
All tools follow a consistent verb_noun pattern with snake_case: add_edge, add_node, get_docs, get_graph, remove_edge, remove_node, set_graph, set_variables. This predictable naming makes it easy for an agent to infer functionality.
With 8 tools, the server is well-scoped for a block editor domain, covering core operations like CRUD for nodes and edges, graph retrieval and replacement, variable management, and documentation access. Each tool earns its place without bloat.
The toolset provides complete coverage for the block editor domain: create (add_node, add_edge), read (get_docs, get_graph), update (set_graph, set_variables), and delete (remove_node, remove_edge). There are no obvious gaps, enabling full script lifecycle management.
Maintenance
Related MCP Connectors
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Build, run, inspect, and continue AgentScript workflows on connected Super Chrome and Mac clients.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Related MCP Servers
- FlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with running Roblox game instances by inspecting the game hierarchy, reading client-side scripts, and executing Lua code directly within the Roblox client through a WebSocket bridge.4430 npm-
- AlicenseBqualityCmaintenanceEnables AI agents to control the ScreenSlick browser video editor, supporting tasks like voiceover generation, transcript creation, and video export via a local WebSocket bridge.1738 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to access live console logs, errors, and network requests from web applications via a local WebSocket connection, without copying data to chat.15 npm19MIT
- -licenseNot gradedqualityCmaintenanceEnables AI assistants to control Roblox clients through a WebSocket connection, allowing execution of Lua scripts, game state inspection, and player manipulation.-