@helloaigent-dev/publisher
This server enables an AI agent to manage and operate a publisher's feed on the Hello Aigent platform—the producer-side counterpart to the subscriber server.
Feed Management: Create feeds with signing keypairs and publisher tokens, list owned feeds, and generate
hello-aigent.jsondiscovery files for hosting at/.well-known/hello-aigent.json.Publishing: Broadcast signed updates (offers, announcements, restocks, content) with structured data, markdown bodies, and callable actions.
Analytics & Insights: Access KPI overview (subscribers, fetch rates, recent activity), funnel analysis (subscribed → returned → acted over 7/30/90 days), and filterable event logs.
Audience: View consent-aware subscriber lists with agent identities, topics, scope, status, and last fetch time.
Event Reporting: Report action outcomes to power analytics and populate the funnel.
Authentication: Works with workspace API keys, admin tokens, or per-feed publish tokens for scoped publishing operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@helloaigent-dev/publisherCreate a feed for my newsletter and publish a signed update"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@helloaigent-dev/publisher
Hello Aigent publisher MCP — an MCP server that lets an agent run a publisher's feed: create feeds, publish signed updates, and read analytics. The producer-side counterpart to @helloaigent-dev/subscriber (which lets an agent subscribe/fetch/act).
A marketer operates their owned agent audience by telling their agent — no CLI, console, or developer.
Tools
Tool | Auth | What it does |
| workspace key or admin | Mint a feed + Ed25519 keypair + publisher token; returns the discovery file |
| workspace key or admin | List feeds you own |
| publish token, workspace key, or admin | Build + server-sign an update; delivered to subscribers |
| publish token, workspace key, or admin | Report an action outcome (the "acted" analytics signal) |
| workspace key or admin | KPI tiles, fetch sparkline, recent activity |
| workspace key or admin | subscribed → returned → acted funnel |
| workspace key or admin | Filterable, attributed audit log |
| workspace key or admin | The owned-audience list (consent-aware) |
| public | Generated |
"workspace key" means a hak_... workspace API key — mint one from the Hello Aigent console (Settings → API keys) once you've signed up. It scopes every tool above to your own workspace: create_feed creates in your workspace, list_feeds/analytics/subscribers only ever see feeds your workspace owns, and publish/report_event only work on feeds your workspace owns. It is not admin-equivalent — it cannot create, list, or revoke API keys (that requires signing in to the console itself).
The admin token is a separate, unrestricted, ops-only credential (not something a self-serve signup ever receives) — it still works everywhere a workspace key does, for every feed, not just your own.
Related MCP server: Paragraph MCP
Configure
Set in your MCP client config (env vars):
HELLOAIGENT_API— API base (defaulthttps://api.helloaigent.dev)HELLOAIGENT_API_KEY— your workspace API key (hak_...); required for feed management + analytics unless using the admin token. Preferred overHELLOAIGENT_ADMIN_TOKENwhen both are set.HELLOAIGENT_ADMIN_TOKEN— admin token; alternative toHELLOAIGENT_API_KEY(ops/dogfood use only)HELLOAIGENT_TOKEN— publish token (a feed's own publisher token); falls back toHELLOAIGENT_API_KEY, thenHELLOAIGENT_ADMIN_TOKEN
Example (Claude Desktop / any MCP client) — the common case, a self-serve workspace key:
{
"mcpServers": {
"hello-aigent-publisher": {
"command": "npx",
"args": ["-y", "@helloaigent-dev/publisher"],
"env": { "HELLOAIGENT_API_KEY": "hak_…" }
}
}
}Then just ask your agent: "Create a feed for my coffee shop and publish a restock update," or "How many agents subscribed this week, and what's the return rate?"
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceLocal-first MCP server for per-agent key management, generating and using signing keys without external KMS.8121MIT

Paragraph MCPofficial
Alicense-qualityAmaintenanceMCP server that connects AI agents to your Paragraph publication, enabling post management, subscriber analytics, and search across posts and publications.321MIT- AlicenseAqualityCmaintenanceMCP server for the Post for Me API, enabling publishing, scheduling, editing, deleting, and analyzing social media posts across 9 platforms from any MCP client.27301MIT
- Alicense-qualityDmaintenanceMCP server for the FreeFeed social network API. Enables reading timelines, posts, comments, and attachments, as well as writing posts, comments, and managing subscriptions.MIT
Related MCP Connectors
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
MCP server for Appcircle mobile CI/CD platform.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/helloaigent-dev/helloaigent-publisher'
If you have feedback or need assistance with the MCP directory API, please join our Discord server