Everything you need to connect the Gen4Engage MCP in Claude Code and start pulling social, analytics, inbox, and reputation data. Setup is one command. There are no keys to paste.
Promo Republic, white-labeled as “Gen4 Social / Gen4Engage” for the Gen4 dental practices SGA acquired. Connecting it in Claude Code exposes roughly 30 tools spanning social posting, analytics, inbox, media, reputation/reviews, and AI content generation. It currently covers the ~83 Gen4 practice locations (about a third of the SGA network); the other locations are not on Promo Republic.
Run this once in Claude Code. Claude will open a browser to authorize you.
Uses OAuth 2.0 Authorization Code + PKCE with Dynamic Client Registration. No API keys or secrets to paste. First use opens a browser to log in and approve.
MCP: gen4engage.com/mcp
Discovery is auto: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
Authorize with all scopes on the first login. With narrow scopes you only see ~6 tools; the full ~30 (including review/reputation) only appear after authorizing with the complete set.
Orange dots = write/operate scopes. See the access note below before using them.
| Thing | What to expect |
|---|---|
| Scopes gate the tools | Only ~6 tools show under narrow scopes. Review/reputation tools return Access Denied until you re-authorize with the full scope set. |
| Rate limits are undocumented | No published limit. If you do bulk work, add retry/backoff and serialize calls per location. There are no bulk/all-location report variants yet, so reporting is one call per location. |
| Refresh tokens rotate hard | Rotated tokens invalidate immediately with no grace window, so parallel calls can lose the token. Fine for interactive use; only a concern if you build an automated sync. |
| JSON:API response shape | Location name is nested under attributes, not top-level. location_id comes back as a string but single-location tools want an int. |
SGA's internal stance is that this MCP is system-leveraged and read-only: the SGA Intranet warehouse is the primary consumer, and read/reporting access is the default use. That covers pulling posts, analytics, inbox, and reputation data.
Write / operate scopes (posts:write, inbox:write, media:write) are reserved for Korrine, who runs SGA social operations. If you need to post or manage the inbox rather than just read, loop Korrine and Dakota in first. Publishing and scheduling stay inside Gen4/Promo Republic itself.
claude mcp add command above.