How it works

Foe: Clockwork Imp, a chore you keep doing by hand.

Clockwork Imp

1. Clockwork Imp

   The Clockwork Imp blocks the way.

   What really happensIt stands for a chore you keep doing by hand.

   Artificer: Context 100/100.

2. Grind

   The imp winds up and hits again, and again.

   What really happensA chore done by hand repeats until someone automates it.

   Artificer takes 3. Artificer takes 3. Artificer takes 3. Artificer: Context 91/100.

3. n8n Instance-Level MCP

   The n8n Orb opens a portal into your own instance.

   What really happensClaude Code or Codex connects to https://<your-n8n-domain>/mcp-server/http after you enable instance-level MCP. Sign in with OAuth, or send an API token.

   Clockwork Imp takes 29.

4. n8n Instance-Level MCP

   The orb lists workflows you already allowed it to see.

   What really happensThe client can search workflows exposed to MCP. From n8n 2.13 it can create and edit workflows, and it can build data tables.

   Clockwork Imp takes 13.

5. Grind

   The Clockwork Imp uses Grind.

   Artificer takes 3. Artificer takes 3. Artificer takes 3. Artificer: Context 82/100.

6. n8n Instance-Level MCP

   A strike wires nodes on the instance, then runs the workflow from chat.

   What really happensYou describe the workflow. The agent creates or edits it on the instance, then runs and checks it. This is separate from the MCP Server Trigger node.

   Clockwork Imp takes 32.

7. n8n Instance-Level MCP

   The imp drops a workflow living on your n8n, cloud or self-hosted.

   What really happensThe workflow is saved on that instance. Enable MCP under Settings, Instance-level MCP. The server URL is not the editor address in the browser bar.

   Clockwork Imp takes 26. Clockwork Imp falls.

8. Victory

   The Clockwork Imp falls.