mcpField
A
ARClip

ARClip

Remote
arclip.designMedia & Design1Updated 4d ago

About ARClip

ARClip’s MCP server lets people build, edit, check and publish 3D, AR and game scenes in ARClip from MCP clients. It supports scene work such as placing objects, adding interactions and preparing scenes for sharing as phone-accessible AR links.

Key features

  1. 01Create and inspect projects
  2. 02Add objects from libraries or AI generation
  3. 03Configure AR placement
  4. 04Add cards, events and scripts
  5. 05Check scenes and preview screenshots
  6. 06Publish scenes as links

Use cases

  1. 01Build a product preview in a room
  2. 02Create an interactive 3D lesson
  3. 03Make a guided tour or tabletop game

MCP support

Exposes ARClip project and scene operations to MCP clients over a hosted streamable HTTP server with OAuth sign-in. Permissions control reading, editing, generation and publishing.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://editor.arclip.design/api/mcp/v1
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

ARClip MCP server

Build, edit and publish live 3D, AR and game scenes in ARClip from Claude, Cursor, VS Code, Codex and other MCP clients. Ask for a product people can place in their room, a 3D lesson, a guided tour or a small game: the assistant builds it in your ARClip project, checks it and, when you ask, publishes it as a link that opens on a phone in AR.

Server URL (streamable HTTP, OAuth sign-in):

https://editor.arclip.design/api/mcp/v1

What you can do

  • Create a project or open one you have, and see what is in the scene.
  • Add objects from your team library, public 3D libraries or AI generation.
  • Set up AR: on a floor, a table or a wall, or over a printed picture.
  • Add interface cards, events and scripts: buttons, quizzes, scores, tours.
  • Check the scene for errors and look at screenshots before you share it.
  • Publish when you say so.

Your team can keep editing the same scene in the browser while the assistant works, and sees its changes live.

Connect

claude.ai and Claude Desktop. Settings → Connectors → Add custom connector, paste the server URL and sign in when asked.

Claude Code.

claude mcp add --transport http arclip https://editor.arclip.design/api/mcp/v1

Then run /mcp and choose to authenticate. To get the server together with the skills below, install the plugin instead:

/plugin install arclip --marketplace arclip/mcp

Cursor. Add to .cursor/mcp.json (one project) or ~/.cursor/mcp.json (all projects):

{
  "mcpServers": {
    "arclip": { "url": "https://editor.arclip.design/api/mcp/v1" }
  }
}

VS Code.

code --add-mcp '{"name":"arclip","type":"http","url":"https://editor.arclip.design/api/mcp/v1"}'

Codex, Cursor and OpenCode from the ARClip CLI: npx arclip skill install --mcp adds the server to their settings.

Gemini CLI. gemini extensions install https://github.com/arclip/mcp

Kiro. Add the power in kiro/.

Cline. See llms-install.md.

Apps that only run local servers. Use mcp-remote with a personal API token:

{
  "mcpServers": {
    "arclip": {
      "command": "npx",
      "args": [
        "-y", "[email protected]",
        "https://editor.arclip.design/api/mcp/v1",
        "--header", "Authorization:Bearer <your-api-token>"
      ]
    }
  }
}

Sign-in and permissions

On the first connection your browser opens your ARClip account with the list of permissions the app asks for. Untick what you don't want and press Allow. You can review or revoke access at any time under API & MCP in your account. A personal API token is created there too; treat it like a password.

PermissionWhat it allows
editor:readRead projects, scenes, resources and the AI balance
editor:writeCreate, change and delete objects, components and settings
editor:aiUse generation, which spends your team's AI credits
editor:publishPublish a project, which makes it public
editor:pluginsWrite editor plugins and add them to a project

On the Free plan, apps can read and check projects. Building, generation and publishing need a paid plan.

To keep a connection on one project, add ?projectId=<project-id>&pin=1 to the server URL. The project ID is the last part of the editor address: editor.arclip.design/project/<project-id>.

Skills

This repository is also a plugin for Claude (claude.ai, Cowork and Claude Code) and Cursor. Besides the server it adds skills that tell the assistant how to do common jobs well:

SkillFor
arclip-sceneThe build, check and publish loop, and where objects come from
product-in-your-roomA product at real size in the viewer's room, with variants and one button
lesson-3d-topicA 3D lesson on one school topic with numbered parts and a short check
place-tourA guided tour of a real place, stop by stop
tabletop-mini-gameA small game on a table in AR or in a browser
ar-print-comes-aliveAR over a postcard, packaging, a poster or a book page
quiz-checkpointsA quiz on top of an existing scene
scene-polish-passA final check before publishing

Data

The server and the plugin send your requests, the scene content you create or change and the files you import to ARClip at editor.arclip.design, under your ARClip account. Generation runs on ARClip and spends your team's AI credits. Published scenes are public. The plugin itself stores nothing.

License

The files in this repository are licensed under the Apache License 2.0. The ARClip service itself is provided under its terms.

Copyright 2026 Web-AR.Studio Corp.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.