MCP

Sprocket Rocket has a remote MCP server, so the AI app you already use can work on your portals: list them, build and edit page drafts, place modules, start installs and updates, and have custom modules built. The app acts as you, with exactly the access you have in Sprocket Rocket, in the organizations you choose when you connect it.

The server URL is the same for everyone:

https://app.sprocketrocket.co/mcp

You'll also find it, with a copy button and these steps, in Sprocket Rocket: open the user menu, select Account settings, then MCP.

What's included

• It comes with Sprocket Rocket AI. You can connect an app only to organizations that have the subscription, and an app with no such organization can't use any tool, the docs search included. If an organization's subscription ends, its portals are refused until it's back. See Pricing.
• Your AI app does the thinking, so most calls don't touch your AI budget. The one exception is building a custom module: Module Builder's agent writes the code on our side, so it uses the organization's Sprocket Rocket AI budget and counts toward your own limit, exactly like a module card you confirm in Page Builder. Your app is told this before it starts one.

Connect an app

Each app asks you to sign in to Sprocket Rocket the first time. You then choose the organizations and the permissions the app gets, and select Allow. Only organizations with Sprocket Rocket AI are listed.

Claude

1. Open Settings > Connectors and choose Add custom connector.
2. Name it Sprocket Rocket and paste the server URL.
3. Choose Connect and sign in.

This works on claude.ai and in the Claude desktop and mobile apps.

ChatGPT

1. Open Settings > Apps and Connectors.
2. Under Advanced, turn on developer mode, then choose Create.
3. Name it Sprocket Rocket, paste the server URL, choose OAuth, and sign in.

Claude Code

Run this in a terminal:

claude mcp add --transport http sprocket-rocket https://app.sprocketrocket.co/mcp

Then run /mcp in Claude Code, choose sprocket-rocket, and sign in.

Cursor

Add this to .cursor/mcp.json in your project, or to your global Cursor MCP settings:

{
	"mcpServers": {
		"sprocket-rocket": { "url": "https://app.sprocketrocket.co/mcp" }
	}
}

Cursor asks you to sign in the first time it uses the server.

Codex

Run these in a terminal. The second command opens the sign-in page.

codex mcp add sprocket-rocket --url https://app.sprocketrocket.co/mcp
codex mcp login sprocket-rocket

Other apps

Any AI app that supports remote MCP servers with OAuth works. Add the server URL and sign in when it asks.

What each permission allows

You choose these on the sign-in screen. Leave out anything you don't want the app to do; it can ask again later if it needs more.

There's no permission to delete pages or uninstall anything.

The app never gets more than you have. If you're a member who only sees some portals, so does the app. If you're removed from an organization, the app loses it on its next call.

Tell it which site

You never need to look up ids or theme names. Name the site the way you'd say it: its HubSpot portal ID, a domain it serves, a link to a page, or the portal's name. If your connection can reach only one portal, you don't need to name it at all. A page can be named by its link, its HubSpot page ID, or its name or browser title.

• "Change the hero headline on acme.com/about to 'Built for every job'."
• "List the landing pages on portal 8510912."
• "Show me https://www.acme.com/pricing and tighten the copy."
• "Is there an update for Globex?"
• "Rewrite the intro on the page called Pricing on portal 8510912."

A page is always worked on in the theme it's built on. For anything else on a portal with more than one theme, the app uses the portal's main theme: the one you've been editing in Sprocket Rocket, or the one that publishes to the portal's main domain, and it tells you which one it used and why. If that isn't clear, you're asked to choose, with each theme described by things you'd recognize, such as how many pages it has, when it was last edited and where it publishes. An update always asks which install when a portal has more than one.

If what you said fits more than one site, say two clients with similar names, or only part of a domain, you're asked which one you mean, or the app lists them so you can tell it. It never picks one for you. Every answer names the site it worked on, such as "Edited About on Acme (portal 8510912, acme.com)", so you can check it's the right one. A site your account can't reach is simply not found.

How the app works with your portals

• Drafts first. Edits go to the page's HubSpot draft, the same draft Page Builder shows. The app checks that nobody changed the page since it last read it, so it can't overwrite your edits.
• Publishing and updates ask first. So do changing a live page's type, changing one of the portal's own modules, and cancelling a module job. The app has to show you what would happen and then send your approval. Apps that can put the question to you directly do that as well.
• Custom modules follow the same path as a module card: Module Builder builds the module in the background, checks that it renders, and publishes it to the portal. The app can place it on a page in the same request, or place it later. If a job stops, the app can retry it. Stock Sprocket Rocket modules are never changed; a change to one makes a copy. Changing one of the portal's own modules updates it everywhere it's used, live pages included, so the app first shows you the module and the change and waits for your approval.
• Pages on any theme. The app can find and read any page on a connected portal, whatever theme it's built on. Sprocket Rocket works best on its own themes, and the app tells you when a page isn't on one. If the page is on a Sprocket Rocket theme that Sprocket Rocket hasn't added yet, the app adds the theme as soon as it opens the page, in the organization that connects the portal, just as adding it under Portals would; this writes nothing to HubSpot. A custom, child or Marketplace theme is added the first time you ask the app to edit a page on it, and the app then makes the edit straight away. Either way the theme's full scan runs in the background, and adding it needs the install permission; without it, the app can still read the page. Because opening a page can add a theme, some apps ask you before they read a page when the app has the install permission. If two of your organizations connect the portal, you're asked which one. Adding a custom theme prepares its Module Builder preview once the scan finishes, as it does in Sprocket Rocket: two preview files of Sprocket Rocket's own go into the theme folder, a hidden "SR Module Preview" page is published, and fitting the preview can use the organization's AI budget. Marketplace and child themes get no preview. On a theme that isn't Sprocket Rocket's, every field is checked against that theme's own module before it's written, and a field that can't be checked yet isn't written; the app tells you what to send again. A page on a coded template that isn't part of any theme can be read but not edited here.
• Unsplash photos the app finds credit the photographer on the page, as Unsplash requires.
• Everything is recorded. Restore points for the app's edits are marked AI app in Page Builder's Version history, and module jobs it starts count toward your AI usage.

Disconnect an app

In Sprocket Rocket, open the user menu, select Account settings, then MCP. Under Connected apps, select Disconnect next to the app. It loses access at its next call.

A connection also ends when you change or reset your password, sign out of all sessions, or don't use it for 30 days, and when a Sprocket Rocket admin resets your password, two-step verification or passkeys. Signing out of Sprocket Rocket in your browser doesn't disconnect your apps. To add an organization you joined later, connect the app again.