Skip to main content
Glama
itzdaimy

247afk Block Editor MCP Server

by itzdaimy
README.md
# 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

1. The MCP server runs locally and starts a WebSocket bridge on `127.0.0.1:3002`
2. Open a script in the 247afk editor, the site will connect to your websocket. 
3. Your ai assistant can now use the MCP server to make changes in scripts. 

NPM package -> https://www.npmjs.com/package/247afk-mcp

## Install

```bash
npm install -g 247afk-mcp
```

## Get Started

### Codex CLI
```bash
codex mcp add 247afk-mcp -- npx -y 247afk-mcp
```

### Gemini CLI
```bash
gemini mcp add 247afk-mcp npx "-y 247afk-mcp"
```

### Claude Code
```bash
claude mcp add 247afk-mcp -- npx -y 247afk-mcp
```

### Claude Desktop
```json
{
  "mcpServers": {
    "247afk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "247afk-mcp"
      ]
    }
  }
}
```

### Cursor

paste this in your browser:
```txt
cursor://anysphere.cursor-deeplink/mcp/install?name=247afk%20Block%20Editor%20MCP%20Server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIjI0N2Fmay1tY3AiXX0=
```

### Manual
1. Copy configuration below
2. Add it to your MCP client configuration
3. Follow your client's specific setup instructions
4. Restart your MCP client to apply changes

Configuration
```json
{
  "mcpServers": {
    "247afk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "247afk-mcp"
      ]
    }
  }
}
```

Restart antigravity/claude code after saving. 

## Test without an AI client

```bash
npx @modelcontextprotocol/inspector 247afk-mcp
```

Opens a browser UI to call tools manually.

## Changelog

### 1.0.1
- Added `update_node_data` — merge field values into a node without replacing it
- Added `move_node` — reposition a node on the canvas
- Added `get_node` — inspect a single node's type, position, and data
- Added `clear_graph` — wipe all nodes and edges while keeping variables
- Added `validate_graph` — run client-side validation and return errors/warnings
- Added `save_graph` — save the script to the server (equivalent to Ctrl+S)
- Added `auto_layout` — auto-arrange nodes left-to-right by execution flow
- Added `add_variable` — add or replace a single variable without touching others
- Added `remove_variable` — remove a single variable by name
- Fixed 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)

TDQS

A3.8/5.0

Scored across 8 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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

ActivityInactive
ResponsivenessNo issues