NodePen docs

Connect your agent

Bring the model you already use and pay for (Claude, Cursor, GitHub Copilot, or anything else that speaks MCP) to NodePen. Every client below needs the same one address:

https://agent.nodepen.io/mcp

What it can do

  • Find and read scripts by name, or browse your team's folders. You never have to hand it an id.
  • Build and change scripts the same way you can: add components, wire them, set up sliders and parameters, groups and controls, etc.
  • Check the result geometry or values. In clients that support MCP Apps, it can also open a live 3D view of it right in the conversation.
  • Verify without looking. It can read a script's results as tree shapes and geometry measurements — counts, areas, volumes, bounding boxes, closed and planar flags, measured on request with your team's compute — and every warning and error as data, tied to the input and wire that caused it.
  • Test scripts and clusters. It can run a saved version with temporary input values, or a sweep of several, without changing the script. Each run is a solve on your team's compute.
  • Get the source file as a .gh or .3dm export, or stream it for processing elsewhere...
  • Bring in your own models. Clients that can run commands on your computer, like Claude Code, can upload .3dm files straight from disk, then draw a script against them and wire their geometry in, object by object: "upload the models in ./site and use the buildings in a script". Clients without a shell can use models you upload yourself from the team's files tab.
  • Read your own files. Any other file you upload — a table, a JSON file, a format only one of your plug-ins understands — can go on a File Path in a script, which reads it as a real file: "use zones.csv in this script and read it line by line".
  • Keep the team tidy by making folders and moving scripts and files into them.

How it works

  • It works as you. The first time a client connects, it sends you to NodePen to sign in and approve it. It can never open anything you could not, and it loses access the moment you do.
  • One team per connection. You choose which team when you approve it, and can change it — or disconnect the client entirely — under Profile → Connected apps.
  • It edits live, alongside everyone else. Changes land in the document as they are made, with their own labelled cursor ("Cursor · Alice"), so anybody with the script open can watch. Each burst of work is one step in the document's undo. Follow safe practices as you would with any other collaborator: use versions to checkpoint work and clusters to divide and concquer.
  • Your model does the thinking, on your own plan with that client.

Claude

In Claude on the web or desktop, open Settings → Connectors, choose Add custom connector, name it NodePen, and paste the address above. Select Connect to sign in, then turn NodePen on from the tools menu in a conversation.

On a Team or Enterprise plan, an owner may need to add the connector for the organization first. See Getting started with custom connectors.

Claude Code

claude mcp add --transport http nodepen https://agent.nodepen.io/mcp

Then run /mcp inside Claude Code and choose nodepen to sign in. See Connect Claude Code to tools via MCP.

Cursor

Add NodePen to ~/.cursor/mcp.json to have it in every project, or to .cursor/mcp.json in one:

{
  "mcpServers": {
    "nodepen": {
      "url": "https://agent.nodepen.io/mcp"
    }
  }
}

Cursor shows it under Settings → MCP, where Connect starts the sign-in. See Model Context Protocol in Cursor.

GitHub Copilot

In VS Code, run MCP: Add Server from the command palette, choose HTTP, and paste the address above — or add it to .vscode/mcp.json yourself:

{
  "servers": {
    "nodepen": {
      "type": "http",
      "url": "https://agent.nodepen.io/mcp"
    }
  }
}

Start the server when VS Code offers to, sign in, and NodePen's tools appear in Copilot Chat's agent mode. See Use MCP servers in VS Code, or Extending Copilot Chat with MCP for Copilot in other editors.

Anything else

Any client that supports remote MCP servers over HTTP, with OAuth sign-in, can connect with the same address. Point it at https://agent.nodepen.io/mcp and it will find its own way to the sign-in.