Use your preferred AI assistant to work directly in WorkLink Create. With MCP (Model Context Protocol), you can explore a scenario, edit steps and objects, and automate repetitive work by describing what you need. Changes appear in your open Create project.

Before you begin

You need an Author license, AI Companion enabled for your organization, and an installed MCP-compatible assistant such as Codex, Cursor, or Claude Code. Open your project in Create and leave the browser tab open.

1. Ask your assistant to set up the connection

Copy this prompt into your assistant. In Cursor, use Agent mode:

Set up WorkLink Create MCP in this AI client using Streamable HTTP at https://worklink-ai.scopear.com/mcp. Use personal/user settings, preserve existing MCP servers, and use browser sign-in with OAuth client ID create-mcp (no client secret). Guide me through any sign-in or restart steps I must complete.

Never ask me to paste passwords, API keys, or sign-in tokens into chat. If browser sign-in is unavailable, show me where to enter a CMS MCP API key privately and pause for me to do it. Do not read or display the key.

Once connected, use worklink_setup to verify authentication, follow the server’s connection guidance, and tell me my current step’s name without changing anything. Ask which project to use if several are open, and ask before taking over a tab another assistant controls.

Using a different environment? Replace the URL in the prompt with MCP server URL from Create → Preferences → AI Companion → Copy URL. For Dev1, use https://worklink-ai-dev1.scopeartest.com/mcp. Create, CMS, and MCP must use the same environment.

2. Sign in and verify

Browser sign-in is recommended where available. Follow the assistant’s instructions to open the WorkLink sign-in page. Sign in yourself and select Allow when WorkLink Create MCP requests access. You do not need an API key for this method.

If the assistant cannot configure your client automatically, use these settings with the same MCP URL:

• Codex: add the server with --oauth-client-id create-mcp, then run codex mcp login worklink. Codex setup guide
• Cursor: in the personal MCP server entry, add "auth": { "CLIENT_ID": "create-mcp" }, then select the server’s login/connect action. Cursor setup guide
• Claude Code: add an HTTP server with --client-id create-mcp, then use /mcp to authenticate. Claude Code setup guide

With one available Create tab, the assistant can connect automatically. With several, tell it the project name. You can also ask it to open the optional session picker. Confirm [MCP] in the chosen tab’s title and MCP Connected in Create’s status bar. The assistant should also successfully read your current step; a tool list alone does not prove access.

Alternative: use a CMS API key

1. In Create’s account menu, select View Profile. In CMS, open your profile’s Integrations → MCP API Key section.
2. Select Generate if you do not have a key. Save it securely; the full key is shown only once. If a key exists, reuse your saved copy.
3. Enter it yourself in your assistant’s private MCP configuration: header name Authorization, value Bearer YOUR_MCP_API_KEY. Replace the placeholder with your full key, keeping one space after Bearer.
4. Save, restart/reload the MCP connection, and ask the assistant to verify access again.

Keep the key out of chat, screenshots, and shared files. A configured API key takes precedence over browser sign-in. Rotate Key replaces the key for every client using it; update those clients afterward.

3. Start working

• “Summarize the steps in this scenario.”
• “Add a red cube to the current step.”
• “Arrange ten copies of the selected object in a circle.”

Review changes in Create and save as usual. Start with a small task: edits affect your live project. When finished, ask “Disconnect from Create.” You can also use Disconnect All MCP Connections in AI Companion preferences; this keeps your sign-in or API key valid.

If you cannot connect

• Sign-in fails: check the client ID is exactly create-mcp and that you have an Author license. Use an API key if browser sign-in is unavailable.
• No project found: keep Create open and check that the account and environment match your sign-in or key.
• Configuration changed: restart/reload the MCP connection and verify again. An assistant may need you to enable the server or start a new chat.