247afk Block Editor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| get_graphA | Get the current script graph from the open editor tab. Returns nodes, edges, and variables. The editor tab must be open. |
| 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. |
| add_nodeC | Add a single node to the script editor canvas. |
| remove_nodeB | Remove a node and all its connected edges from the editor. |
| add_edgeB | Connect two node ports with an edge. Use get_graph first to know existing node ids. |
| remove_edgeC | Remove a specific edge by id. |
| set_variablesC | Replace the script variables list. Existing variables are overwritten. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.