Automate Customer Onboarding with JustOneCX MCP
Résumé
Pixel’s announcement introduces the JustOneCX remote MCP server for AI-assisted customer onboarding with Claude Code, Codex, Cursor, and Gemini CLI. Assistants can create product tours, surveys, announcements, and funnels, while changes remain drafts until published and access stays limited by your role.
DEV Community
Use an AI assistant for customer onboarding with MCP
You can use an AI coding assistant for customer onboarding by connecting it to the JustOneCX remote MCP server at https://api.justonecx.com/mcp. It works with Claude Code, Codex, Cursor and Gemini CLI. You sign in through your browser, pick the workspace and choose an access level. Everything it creates is a draft until a person publishes it. What does the assistant do for onboarding? Once connected, the assistant can install the SDK, build product tours from your code, announce features, add surveys, answer chat, manage your roadmap, read your analytics and event log, set up funnels and Brand Kit, and find out why something does not show. It acts as you, so it can never do more than your own role allows. For a vague request such as "add a tour", a planning skill makes it study your product and propose a ranked list first. It chooses where each tooltip, survey or announcement sits from where the element is on screen, and asks when unsure. How do you connect it? Your assistant signs in through your browser the first time. No token goes in any config file. Claude Code claude mcp add --transport http justonecx https://api.justonecx.com/mcp
Then run /mcp, pick justonecx and sign in. Codex. Add this to ~/.codex/config.toml, then run codex mcp login justonecx: [mcp_servers.justonecx]
url = "https://api.justonecx.com/mcp"
Cursor. Put this in .cursor/mcp.json: { "mcpServers": { "justonecx": { "url": "https://api.justonecx.com/mcp" } } }
Gemini CLI. Add this to ~/.gemini/settings.json, then run /mcp auth justonecx: { "mcpServers": { "justonecx": { "httpUrl": "https://api.justonecx.com/mcp" } } }
For CI and tools without browser sign-in, you can create a token in Settings → Developers → AI assistants. Keep the token in an environment variable and never in a config file. A token has the same limits as the browser sign-in and can be revoked in the same place. See the MCP server docs. What are the access levels? When you sign in, you pick how much the assistant may do. Level What it can do See your content and setup Reads only. Create and edit drafts (default) Nothing your users see changes until a person publishes. Make changes live Can also publish. Off unless you choose it. A workspace owner can switch AI assistants off or cap them in Settings → Developers → AI assistants. What can it not do? It cannot empty the Trash, export survey responses as a file, or change members, roles, billing or keys. For those it points you to the dashboard page and the steps. It never handles the Secret key. The Secret key is never returned, read, asked for or pasted into chat. You set JUSTONECX_SECRET_KEY in your own server environment yourself. The get_install_info tool returns your Public key and the install snippet, never the Secret key. For identity verification, it adds the server code and an .env.example entry, and passes userHash to identify(). It switches Require on only after your live site sends userHash and you say yes, because that setting changes the live site. See identify users with the SDK. What stays a draft, and what needs confirm? Everything it creates is a draft until a person publishes it. Changes that reach customers or the live site need an explicit confirm. Examples are: A chat reply, which goes to the customer at once. A roadmap status change, because voters are emailed. Workspace settings and custom CSS. Deleting a tour, announcement or survey, which leaves the site at once. Contact details such as email, phone and address are hidden unless the task asks for them. Every change shows in your audit log as made by the AI assistant. How should you review the assistant's work? Use the same steps every time. Ask it to run workspace_status. It returns your role, plan and a setup checklist, with a fix for every failing item. Ask it to build the content as a draft, for example a tour. Run validate_tour to check the selectors, page rule and step flow. Open the preview link. get_tour_preview_link previews the draft on your site for 2...

Powered by Readybot.io