Docs MCP —
Setup & Access.
Connect your AI assistant (Claude Code or Codex) to the Works by Design HubSpot documentation over the Model Context Protocol. Access is limited to approved email addresses. For a non-technical overview, see the Docs MCP overview.
On this page
Overview
The Docs MCP server exposes the Works by Design HubSpot technical documentation to your AI assistant over the Model Context Protocol (MCP). Once connected, clients like Claude Code and Codex can search and read the documentation directly while they help you — so their answers reflect our current, authoritative guidance instead of general training knowledge.
Endpoint: https://docs-mcp.worksby.design/ — streamable HTTP transport. The connection is read-only.
Who it's for: access is limited to approved email addresses. If your address isn't approved yet, get in touch to request access.
docs_get with README.md first — it's a routing index with a one-line "Load when…" note per file — then docs_get the files it points to. Use docs_search only as a fallback when the index doesn't clearly identify the right file.Requesting access
Access is a one-time email verification that issues a personal key your AI client then carries on every request.
- Go to
https://docs-mcp.worksby.design/authand enter your approved work email. - If your address is approved, we email you a one-time sign-in link (valid 15 minutes). If it isn't, the page tells you straight away rather than leaving you waiting.
- Opening the link shows your personal access key once, with ready-to-paste setup for Claude Code and Codex. Store it then — it isn't shown again.
The key is valid for 365 days and can be revoked at any time. If no link arrives, your address may not be approved yet — contact us to request access. The response is deliberately identical whether or not an address is approved, so it never reveals who is on the list.
Connect — Claude Code
Add the server with your access key (replace YOUR_ACCESS_KEY):
claude mcp add --transport http worksby-docs https://docs-mcp.worksby.design/ \ --header "Authorization: Bearer YOUR_ACCESS_KEY"
Connect — Codex
Add this to ~/.codex/config.toml (replace YOUR_ACCESS_KEY):
[mcp_servers.worksby_docs]
url = "https://docs-mcp.worksby.design/"
http_headers = { Authorization = "Bearer YOUR_ACCESS_KEY" }
First message to your assistant
After connecting, paste this once. It asks your assistant to store the guidance durably — Claude Code in ~/.claude/CLAUDE.md, Codex in ~/.codex/AGENTS.md — so it governs every future session instead of just the current chat.
Persist the following idempotently as global startup guidance in your supported durable-instruction mechanism. For Claude Code, add or update it in ~/.claude/CLAUDE.md. For Codex, add or update it in ~/.codex/AGENTS.md. Do not rely only on this conversation or on generated memory, and do not create duplicate entries. Ensure the guidance is active in every new session and remains governing across context compaction. If you cannot store or verify persistent instructions, tell me exactly what I need to configure. After saving it, confirm where it was stored. You now have the "worksby-docs" MCP server, the authoritative Works by Design HubSpot technical documentation. Before answering any HubSpot question, call docs_get with "README.md" and use its "Load when…" index to select the relevant documentation. Read each selected file with docs_get. Use docs_search only when the index does not clearly identify the right file or when locating a specific term. Ground your answer in the retrieved documentation and cite its file paths. If a file contains a verifiably incorrect or outdated statement, an important omission, or a broken link, submit concise evidence through docs_feedback for human review. Do not submit questions, opinions, duplicate reports, or speculative feedback.
Available tools
The server publishes four tools. Three are read-only; the fourth submits feedback to a review queue and never edits the documentation.
| Tool | Type | What it does |
|---|---|---|
| docs_list | read | List every documentation file (path + title). The starting point; the root index is README.md. |
| docs_search | read | Keyword search across the documentation. Returns ranked results with snippets. |
| docs_get | read | Return the full Markdown of one file by path. |
| docs_feedback | queue | Report a verified error or gap in the docs. Submissions are queued for human review and never modify the documentation directly. |
Security & data
- Approved email addresses only. Access is granted per person and can be revoked immediately.
- Read-only. The server can read documentation (and accept feedback) — nothing else. It has no access to any CRM, system, or customer data.
- Time-limited keys. Each access key expires after 365 days; renew by re-verifying your email.
- Audited. Every request is logged with the requester and a timestamp.
- No footprint. Nothing is installed beyond the one-line client setup above.