Connect RightMessage to your AI assistant

Connect your assistant so you can describe what you'd like to build and have it work in your RightMessage project. It can read your existing setup, save changes to a draft, and publish them when you tell it to.

Your assistant connects through MCP, a standard way for AI assistants to use other apps. You'll need a RightMessage account with access to an eligible project and an assistant that supports remote MCP connections.

Start from your dashboard

1. Open the project you want to work on in RightMessage.
2. Choose Use RightMessage with your agent. It copies a setup prompt with your project already filled in.
3. Paste the prompt into your assistant and follow along.
4. When it asks, sign in to RightMessage in your browser and approve the connection.

Enlarge

WorkForge dashboard heading with the Use RightMessage with your agent button highlightedOriginalOriginal

The prompt also asks your assistant to install RightMessage's skills if it can. They teach it how to audit, segment, personalize, and test safely. It then reads your project and summarizes the setup before asking what you'd like to work on.

Claude and ChatGPT on the web need you to add RightMessage in their connector settings yourself. Follow the connection steps below. Use them if you don't see the dashboard button, too.

Add RightMessage in your assistant's settings

The recommended connection uses hosted OAuth. You sign in and approve access without giving your assistant an API token.

1. Open your assistant's remote MCP or connector settings. In Claude or ChatGPT on the web, add RightMessage as a custom connector.
2. Enter this server URL:

https://api.rightmessage.com/mcp/rightmessage

3. Choose HTTP or Streamable HTTP if it asks for a transport.
4. Start the connection or authorization action.
5. Sign in to RightMessage in the browser it opens.
6. Check Signed in as, Application, Redirect host, and Requested permission. Choose Approve if the account and application are correct, or Cancel to deny access.
7. Return to your assistant. Refresh its tool list if it hasn't updated automatically.

Enlarge

RightMessage OAuth approval for WorkForge Assistant, signed in as docs-developer@example.com, requesting mcp:use permissionOriginalOriginal

The requested scope is mcp:use. The approval page follows your operating system's light or dark appearance, independently of your dashboard setting.

Each assistant has its own settings layout, which can change. Use its remote MCP instructions rather than looking for the same menu in every app. The MCP authorization reference covers supported connections, project selection, and permissions.

If you use Claude Code, this command adds the same hosted server. Complete the browser authorization afterward:

claude mcp add --transport http rightmessage https://api.rightmessage.com/mcp/rightmessage

Confirm the project before making changes

Ask your assistant to tell you the project name, website, and existing flows before it edits anything. The dashboard setup prompt already asks it to select your project and read that context.

If you connected manually, copy your project ID from the dashboard URL. It's the part immediately before /dashboard. Give that ID to your assistant with a request like this:

Use the RightMessage project ID I supplied. Tell me its name, website, and existing flows. Don't change anything yet.

Check that the name and website match the project you intended. If you work across several projects, ask your assistant to specify the project ID for each operation. Its remembered active project is a default, not a restriction on which projects it can access.

Use an API token if OAuth isn't available

If your assistant can't use OAuth, create an API token. Creating an API token requires Scale or Pro. Add the same hosted server URL, then put Authorization: Bearer YOUR_API_TOKEN in the assistant's secure credential settings.

For Claude Code, the manual command is:

claude mcp add --transport http rightmessage \
	https://api.rightmessage.com/mcp/rightmessage \
	--header "Authorization: Bearer YOUR_API_TOKEN"

Replace YOUR_API_TOKEN with your token. Keep the real value out of committed configuration and shared command history. REST token abilities don't make an MCP connection read-only. Confirm the project as described above before allowing edits.

Build a draft, then decide when to publish

Connecting an assistant doesn't grant features outside your project's plan or your access. For example, the connection alone doesn't grant visitor profiles, split testing, or publishing permission.

Ask your assistant for a specific change and tell it to leave the work in draft. After it builds, have it describe the edits. In RightMessage, choose Preview on your site to try the draft on your website with the debugger. Testing your changes explains how to check each visitor path.

Once you're happy with it, tell your assistant to publish. You can also choose Publish in RightMessage to review and publish there. Visitors see the configuration changes after that separate publish action.

Not every assistant action is a draft edit. Integration tools can contact external services. Exports create jobs, feedback queues immediately, and split tests have separate start and end actions. Check the relevant MCP reference before approving those operations.

When your assistant describes the correct project and you can inspect its draft in RightMessage, you're connected. Next, build a resource recommendation with your assistant.

Disconnect an assistant

To remove an OAuth connection:

1. Open Your profile in RightMessage, then AI Connections.
2. Choose Disconnect beside the assistant.
3. Confirm Disconnect in the Disconnect AI Client dialog.

This revokes that assistant's OAuth access and refresh tokens for your account. You'll need to approve a new connection to reconnect. For a bearer-token connection, revoke the token under API Tokens instead.

If you can't connect or your assistant can't find its tools, follow external AI connection troubleshooting.