A side-by-side look at the Nexly Analytics and Hitkeep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Hitkeep 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.
Nexly Analytics
No confirmed install command for Nexly Analytics yet — follow the setup steps linked from its listing page rather than a guessed package name.
Hitkeep
No confirmed install command for Hitkeep yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Nexly Analytics is categorized under Marketing and uses an install path we have not confirmed yet. Hitkeep belongs to Marketing and uses an install path we have not confirmed yet. Pick Nexly Analytics for marketing work and Hitkeep for marketing.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Nexly Analytics has no declared pricing — check the project's own site. Hitkeep is listed as free. Auth: api key required. 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 nexly-analytics and pascalebeier-hitkeep as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nexly Analytics has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Hitkeep has 49/100 (Fair) with 2 views, 0 installs and 93 GitHub stars.