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. That's it.
No invitation needed. If your work address is on the approved list, signing in is all it takes — nothing to request first. If it isn't, the sign-in page says so and tells you who to ask, so it costs you nothing to try.
Pick the client you use — A, B or C, not all three. The whole thing takes about a minute.
The simplest route — no terminal, nothing to install, and the
same on Windows, macOS and in the browser. In Claude, open
Settings → Connectors and look for worksbydesign in the
list: if it is already there, just click Connect. Otherwise choose
Add custom connector, give it any name you will recognise
(worksbydesign works), and paste this as the server URL:
https://mcp.worksby.design/
Leave OAuth Client ID and Client Secret empty — the connector registers itself. Click Connect and Claude opens the sign-in page; enter your approved work email and click the link we send you.
No "Connectors" section, or no "Add custom connector" button? 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 below, which is unaffected.
1. Add the server. Run this in a normal terminal
— PowerShell or Windows Terminal on Windows, Terminal on macOS, or the one built into VS Code.
Not inside a Claude Code session: Claude Code cannot add a server to itself,
because its tool shell often can't see the claude command and a running session
has already loaded its server list.
claude mcp add --scope user --transport http worksbydesign https://mcp.worksby.design/
Keep --scope user. Without it Claude Code defaults
to local scope and registers the server only for the folder you ran the command in —
it then silently disappears in every other project. This is the most common setup mistake.
claude not found? On macOS, open
Claude Code and run /install-cli, then close and reopen your terminal. On
Windows the CLI is installed with Claude Code — reopen the terminal so it
picks up PATH, or reinstall Claude Code. Check with claude --version.
2. Authenticate — adding is not signing in. The command above
only registers the address and reports success while the server is still unauthenticated.
Open Claude Code, run /mcp and choose Authenticate next to
worksbydesign (it also prompts on first use). /mcp is a command
inside Claude Code — the VS Code chat panel, the desktop app's Claude Code, or
claude in a terminal all work; typed into a plain terminal it just says "command
not found". It takes effect immediately, with no restart needed — confirm with
claude mcp get worksbydesign (✓ Connected). One setup covers
VS Code, the desktop app's Claude Code and the terminal:
they share one configuration.
Also a normal terminal, same as B. The second command opens the
browser sign-in. If your Codex version reports an unknown command, check
codex mcp --help — the CLI is moving quickly and the sign-in step may be named
differently in your build.
codex mcp add worksbydesign --url https://mcp.worksby.design/ codex mcp login worksbydesign
Codex reads the same documentation. The optional demo-builder toolkit is a
Claude Code plugin with no Codex equivalent — on Codex, point the assistant
at the methodology specs directly (business/skills/specs/) when your grant
includes them.
Ready-made skills for presales work — demo pages, demo workspaces, customer context, brand capture, and turning a quote PDF into a HubSpot quote. They read their instructions from this server, so they stay current on their own.
/plugin marketplace add https://worksby.design/git/plugins.git /plugin install demo-toolkit@worksby-design
Then turn on auto-update: /plugin →
Marketplaces → worksby-design →
Enable auto-update. Claude Code leaves this off for
marketplaces outside Anthropic's own, so without it you won't receive new skills we add.
(Updates land on your next session, or run /reload-plugins to pick them up
straight away.)
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