Helloaigent Publisher vs Posthog
A side-by-side look at the Helloaigent Publisher and Posthog MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Helloaigent Publisher for developer tools work as a local process; choose Posthog for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Helloaigent Publisher when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HELLOAIGENT_API, HELLOAIGENT_API_KEY, HELLOAIGENT_ADMIN_TOKEN, HELLOAIGENT_TOKEN. - You want tools like
hello_aigent_create_feed, hello_aigent_list_feeds, hello_aigent_publish.
Choose Posthog when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
POSTHOG_AUTH_HEADER, MCP_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | HELLOAIGENT_APIHELLOAIGENT_API_KEYHELLOAIGENT_ADMIN_TOKENHELLOAIGENT_TOKEN | POSTHOG_AUTH_HEADERMCP_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 40,388 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Helloaigent Publisher | View Posthog |
Tools & capabilities
Helloaigent Publisher tools 9
hello_aigent_create_feedMint a feed + Ed25519 keypair + publisher token; returns the discovery filehello_aigent_list_feedsList feeds you ownhello_aigent_publishBuild + server-sign an update; delivered to subscribershello_aigent_report_eventReport an action outcome (the "acted" analytics signal)hello_aigent_overviewKPI tiles, fetch sparkline, recent activityhello_aigent_funnelsubscribed → returned → acted funnelhello_aigent_event_logFilterable, attributed audit loghello_aigent_subscribersThe owned-audience list (consent-aware)hello_aigent_discovery_fileGenerated `hello-aigent.json` to host at `/.well-known/
Posthog 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.
Helloaigent Publisher
{
"mcpServers": {
"helloaigent-publisher": {
"command": "npx",
"args": [
"-y",
"@helloaigent-dev/publisher"
],
"env": {
"HELLOAIGENT_API": "YOUR_HELLOAIGENT_API_HERE",
"HELLOAIGENT_API_KEY": "YOUR_HELLOAIGENT_API_KEY_HERE",
"HELLOAIGENT_ADMIN_TOKEN": "YOUR_HELLOAIGENT_ADMIN_TOKEN_HERE",
"HELLOAIGENT_TOKEN": "YOUR_HELLOAIGENT_TOKEN_HERE"
}
}
}
}
Posthog
No confirmed install command for Posthog yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Helloaigent Publisher is categorized under Developer Tools and uses a local stdio subprocess. Posthog belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Helloaigent Publisher for developer tools work and Posthog for developer tools.
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. Posthog has no confirmed install command yet — follow its own setup instructions.
Helloaigent Publisher has no declared pricing — check the project's own site. Posthog has no declared pricing — check the project's own site. 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 helloaigent-publisher and posthog-posthog as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Helloaigent Publisher has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Posthog has 43/100 (Fair) with 0 views, 0 installs and 40,388 GitHub stars.