A side-by-side look at the Adrails and Opus Growth MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Adrails for marketing work over a hosted endpoint; choose Opus Growth for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Adrails when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Opus Growth tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Adrails is categorized under Marketing and uses a remote HTTP/SSE transport. Opus Growth belongs to Marketing and uses a remote HTTP/SSE transport. Pick Adrails for marketing work and Opus Growth for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Adrails has no declared pricing — check the project's own site. Opus Growth is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add adrails and opus-growth as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adrails has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Opus Growth has 75/100 (Great) with 5 views, 0 installs and 0 GitHub stars.