Custom MCP and plugins
Add a trusted custom MCP connection or plugin through the supported controls in Growthub, Codex or Claude.
Explore this guide
Choose where to install it
A Growthub plugin is managed in Growthub’s Plugins library. An external Codex or Claude plugin is installed through that provider’s supported plugin or MCP settings.
Read the full sectionChoose where to install it
A Growthub plugin is managed in Growthub’s Plugins library. An external Codex or Claude plugin is installed through that provider’s supported plugin or MCP settings.
Use the intended account and installation scope. A connection on one surface is not proof it is configured on another.
Connect it in Growthub
- Open Plugins and choose the existing add or create-plugin action for your connection.
- Use the trusted server URL or supported plugin package and its documented authentication method.
- Review the tools and their permissions in Manage.
- Check the selected connected accounts and each device’s sync result.
- Try one bounded read and inspect its actual result before relying on writes.
Use the provider’s native setup
For an external installation, follow the current Codex or Claude MCP instructions and the plugin author’s setup guide. Remote HTTP and local command servers have different configuration and trust requirements.
Store credentials in the supported private settings. Approve only the account, server and scope you intend to use.
Verify the tool, not just installation
Ask for a small useful read, then open the returned source or record. Check a write only when you explicitly intend that effect, and reopen the actual destination afterward.
An unavailable tool should lead to the relevant connection or permission check. Keep the rest of the task moving through the tools already available.