HowdyGo MCP Server

The HowdyGo MCP server connects your HowdyGo account to Claude, ChatGPT, and other AI assistants that support the Model Context Protocol (MCP). Once it’s connected, paste a demo link into the chat and ask your assistant to work on it. It can write the step text, set up chapters and the end-of-demo CTA, play the demo inline, and give you a share link or embed code, all without leaving the chat.

The assistant uses the same tools and writing guidelines as Howdy AI in the editor. It reads each step’s page, the element that was clicked, and a screenshot, so it writes about what your product actually does instead of guessing from the demo’s title.

The server URL is:

https://app.howdygo.com/api/mcp

Connecting your assistant

The first time your assistant uses a HowdyGo tool, it asks you to connect your account. You’ll be sent to HowdyGo to sign in as usual (or start a free trial), then returned to the chat.

The assistant acts as you. It can open only the demos you can open in HowdyGo, and it can only change demos your team role lets you edit.

Claude

Add HowdyGo as a custom connector. It then works in Claude on the web, Claude Desktop, and Claude in Chrome.

1. Go to Customize > Connectors, click + Add, then Add custom connector.
2. Name it HowdyGo, paste the server URL, and click Continue.
3. Keep the default sign-in settings and click Add.
4. Click Connect and sign in to HowdyGo.

On Claude Team and Enterprise plans, an owner adds the connector first from Organization settings > Connectors. Members then find the HowdyGo custom connector under Customize > Connectors and click Connect. See Claude’s guide to custom connectors  for more detail.

ChatGPT

Add HowdyGo as a custom MCP server:

1. Go to chatgpt.com/plugins , click +, and choose Add custom MCP server.
2. Name it HowdyGo, paste the server URL, and choose OAuth for authentication.
3. Accept the warning and create the plugin.
4. In a new chat, type @ and pick HowdyGo. Sign in when asked.

Claude Code

Add the server from your terminal:

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

Then run /mcp inside Claude Code to sign in.

Other MCP clients

Any client that supports remote MCP servers over HTTP with OAuth sign-in can connect. Add the server URL as a remote (HTTP) server and sign in when prompted.

Working on a demo

Paste a demo’s editor, share, or embed link into the chat and tell your assistant what you want. For example:

• “Set up this demo: https://app.howdygo.com/edit/… ”
• “Rewrite step 4 to focus on how much time this saves.”
• “Make the CTA ask people to book a call with our sales team.”
• “Turn on autoplay for this demo.”

Asking the assistant to “set up”, “annotate”, or “write” a demo covers the full setup in one pass:

• Step text for every step
• Auto-progress on transitional steps, such as navigation clicks
• Chapters for longer demos
• A descriptive title, if the demo still has a default one
• The end-of-demo CTA and its background
• Whether to turn on autoplay

If you ask about a single step, it changes only that step.

Most assistants ask you to approve each change before it runs. Approved changes apply to the live demo straight away, just like edits made in the editor, and each one is saved in the demo’s version history. When it’s finished, the assistant gives you the demo’s editor link so you can review the changes.

What the assistant can change

• Step headings and text
• Button and opt-in labels on overlays
• Auto-progress on individual steps
• Chapters
• The demo title
• The end-of-demo CTA and its background
• Autoplay and its speed
• Whether the demo is published

Some changes still need the editor: adding, removing, or reordering steps, moving hotspots, zoom, media, and editing text on the captured pages. The assistant sends you the editor link when you ask for one of these.

Playing and sharing demos

Ask your assistant to show you a demo and it plays inline in the chat, where you can click through it. Only published demos can play this way. Sandboxes show a card that opens them full size.

Your assistant can also get a demo’s share link or embed code, the same ones you’d copy in HowdyGo. Both use your custom domain if you’ve set one up. Sandboxes don’t have embed code, so you’ll get their share link instead.

Recording a new demo

If your assistant can control your browser, such as Claude in Chrome, it can record a new demo for you with the HowdyGo Chrome extension. Make sure the extension is installed and signed in to HowdyGo in the same browser, then describe the flow:

• “Record a demo of creating a new project on app.example.com, then set it up.”

The assistant starts the recording, clicks through the flow, stops it, and waits for the upload to finish. It then sets up the new demo and gives you its editor and share links. If the extension can’t be started from the page, the assistant asks you to start recording from the HowdyGo extension’s toolbar button, then carries on from there.

AI usage

The HowdyGo MCP server doesn’t count toward your organization’s AI usage. The writing is done by your own AI assistant, so your assistant’s plan and limits apply instead.