One minute of setup gives your AI assistant the worksby.design documentation — hundreds of hours of real HubSpot build and troubleshooting experience, read live while it works. Ask it for a UI extension, a CMS module, a quote template or a complete HubSpot app and it builds from patterns proven to work; point it at existing code and it troubleshoots against best practice. Daily HubSpot developer or describing your first build in plain English — you ask, your assistant does the reading.
Access is set up from your AI client — there is no token to copy. Add the server, and your client opens a sign-in page; enter your work email there and click the link we send you. No invitation needed: if your work address is approved, signing in is all it takes; if it isn't, the sign-in page says so and tells you who to ask — it costs you nothing to try.
Pick one — the client you actually use. A and B need no terminal. After signing in you'll see a "You're connected" page with one final copy-paste for your assistant — don't skip it: it is what makes the documentation (and new skills) load from the start of every session.
In Claude, open Settings → Connectors and look for
worksbydesign: if it is listed, just click Connect.
Otherwise choose Add custom connector, name it worksbydesign,
and paste this as the server URL — leave Client ID and Client Secret empty:
https://mcp.worksby.design/
Click Connect: enter your approved work email on the page that opens and click the link we email you. Once connected, the documentation prompts your access includes appear in Claude automatically — nothing more to install.
That is not you missing it — on a managed or company Claude plan an administrator can turn custom connectors off, and then the option simply isn't shown. Ask whoever manages your Claude workspace to allow custom connectors, or use B, which is unaffected.
Type these two commands into Claude Code itself — the chat
input where you talk to Claude (VS Code panel, desktop app, or the terminal app).
They start with / and only Claude Code understands them — not
a PowerShell/Terminal prompt:
Type /plugin into Claude Code's chat input and press Enter —
the plugin manager opens (in VS Code, choose Manage plugins). On the
Marketplaces tab, add this address:
https://worksby.design/git/plugins.git
Then on the Plugins tab install worksbydesign
(for you) and restart when asked; run /plugin again afterwards to
confirm it shows as installed and enabled. Prefer typing? Where plugin commands run
(a terminal-run Claude Code always does), these do the same in one go:
/plugin marketplace add https://worksby.design/git/plugins.git
/plugin install worksbydesign@worksby-design
That installs the documentation server and the skills in one go.
When Claude Code asks you to authenticate worksbydesign (it prompts on first
use — or run /mcp and choose Authenticate), enter your work
email and click the link we send. One setup covers VS Code, the desktop app and the
terminal — they share one configuration. A surface that answers
"/plugin isn't available in this environment" to the commands wants the clicks
above instead.
Last step — turn on auto-update: in a terminal-run Claude
Code, /plugin → Marketplaces →
worksby-design → Enable auto-update. It is off by
default for marketplaces outside Anthropic's own; without it, new skills we publish never
reach you. The VS Code dialog has no auto-update toggle — its ↻ refresh is a manual
pull; the toggle set from any surface applies to all of them.
Doing presales demos? The plugin already includes the five demo skills (demo pages, workspaces, customer context, brand capture, business case) — nothing extra to install. They need the business-context documentation grant; without it they refuse politely and explain how to request access. The sign-in confirmation tells you which grants you have.
Then prove it: ask Claude Code to "Check my worksby setup" — the setup-check skill verifies the whole install end to end and offers to fix anything missing, asking before it changes anything.
Run this in a normal terminal (PowerShell on Windows, Terminal on macOS) — not inside Claude Code:
claude mcp add --scope user --transport http worksbydesign https://mcp.worksby.design/
Keep --scope user — without it the server is
registered only for the folder you ran the command in and silently disappears everywhere
else. Then, inside Claude Code, run /mcp and choose Authenticate
next to worksbydesign; confirm with claude mcp get worksbydesign.
claude not found? On macOS run /install-cli inside Claude Code and
reopen your terminal; on Windows reopen the terminal so it picks up PATH.
HTTP 401?If you set the server up before 25 July 2026, your entry stores a
long-lived token in an Authorization header. Those tokens were retired when this
server moved to per-install sign-in, so that entry can only ever answer 401 — and
Claude Code switches the sign-in off whenever that header is set, so
/mcp will never offer you Authenticate while it is there.
Delete the old entry first — it may carry any name you gave it, so list them:
claude mcp list claude mcp remove <the-old-name>
Then follow step B above and sign in with your work email (the address your access was granted to — a personal address matches nothing and is refused).
An entry you added after that date needs no change: it signs in the same
way, the plugin points at the same address, and Claude Code connects once. Remove it with
claude mcp remove worksbydesign only if you want the plugin to manage it.
Signing in on a new install signs out the previous one for the same client — access is personal, one active install per client, and every call is logged under your address.
Read-only access; approved addresses only. Not approved yet, or access revoked? Get in touch →
worksby.design · purpose-built tools that extend HubSpot · contact
© 2025–2026 worksby.design · independent, not affiliated with or endorsed by HubSpot · legal, licences & privacy