Skip to content

blowhorn-ai/blowhorn

v1.1.0Apache-2.0

Not a bot. It's you. Social media and marketing management that grows replies, comments and real conversation, and posts, reposts and amplifies, on LinkedIn, X (Twitter), Reddit, Bluesky, Threads, Mastodon, Facebook, Instagram, TikTok, YouTube, Discord, Slack, GitHub and Hacker News.

Changelog

All notable changes to this repo. Versions are the blowhorn-mcp npm launcher's, which every listing file follows.

Unreleased

1.1.0

  • GitHub Copilot CLI plugin: Agent Plugins 1.0 plugin.json, a self-hosted marketplace at .github/plugin/marketplace.json (copilot plugin marketplace add blowhorn-ai/blowhorn-mcp, then copilot plugin install blowhorn@blowhorn). Root mcp.json is the Agent Plugins config ($schema, "type": "stdio", command node, args ${PLUGIN_ROOT}/bin/blowhorn-mcp.js). Cursor's MCP config is .cursor-plugin/mcp.json and keeps ${userHome}/.local/bin/blowhorn-mcp. Claude Code's .mcp.json keeps ${HOME}/.local/bin/blowhorn-mcp (#33).
  • hosted/: every request forwarded to Cloud's /mcp includes X-Forwarded-Mcp-Resource: https://mcp.blowhorn.ai/mcp (the public resource). A client-supplied value is overwritten (blowhorn-ai/blowhorn#1509, layer5io/meshery-cloud#6452).
  • hosted/README.md: Cloud dynamic client registration is on (layer5io/meshery-cloud#6402, Cloud v1.0.367). POST /oauth2/register returns 400 asking for redirect_uris, not 403. End-to-end sign-in is still waiting on Cloud accepting tokens for https://mcp.blowhorn.ai/mcp.
  • hosted/: an unauthenticated GET /mcp (no usable Bearer token) is answered here with the 401 challenge, so a browser Accept: text/html is not forwarded and turned into blowhorn-mcp-1013 (#38).
  • hosted/: make hosted-smoke (npm run smoke:hosted) is an opt-in live smoke of https://mcp.blowhorn.ai, run by hand after a release and never by make check or CI. See hosted/README.md, Post-release smoke.
  • hosted/: with BLOWHORN_MCP_TEST_EMAIL and BLOWHORN_MCP_TEST_PASSWORD set, the live smoke signs the test account in without a browser (authorization code + PKCE, resource=https://mcp.blowhorn.ai/mcp, code caught on the loopback redirect) and runs the signed-in checks with that token. It reads Cloud's wrapped login flow, and when the consent page is a JavaScript widget it accepts through POST /api/identity/oauth/consent-requests/accept. It skips, naming the step a person must do, while the account's email is unverified or a hop still needs a browser. When the test account is set and SMOKE_HOSTED_WRONG_AUD_TOKEN is not, it also mints a token for another audience and checks that /mcp refuses it.

1.0.2

  • Round-2 listing copy names social media management and the supported platforms (#5).
  • server.json gains a remotes entry for the hosted server (https://mcp.blowhorn.ai/mcp), generated from listing.remotes.
  • Copy rules now allow naming the hosted server and OAuth; Cloud's origin hostname stays confined to hosted/.

1.0.0

  • First stable release. The version jumps from 0.1.4 to 1.0.0; there are no launcher feature changes in this cut.
  • Relicensed first-party code under Apache License 2.0 (#29). npm blowhorn-mcp and the MCP Registry entry io.github.blowhorn-ai/blowhorn now publish as Apache-2.0 (0.1.4 on npm still carried AGPL-3.0-only).
  • hosted/: /mcp rate limits are a strict fixed-window Durable Object (RateLimiter, bound as RATE_LIMITER) instead of Cloudflare's simple ratelimits bindings, which do not enforce on a live worker (cloudflare/workers-sdk#16097). Counts stay 1200 requests / 60 s per address and 60 tool calls / 60 s per caller, in the RATE_LIMITS var. A missing binding or a limiter error fails closed with 503. Retry-After is the seconds left in the window (#13).

0.1.4

  • README: the "npm launcher (coming)" section is now "npm": blowhorn-mcp is on npm and in the official MCP Registry, with the npx -y blowhorn-mcp install for JSON configs and Claude Code. llms-install.md and AGENTS.md say the same, and make check no longer requires npm and MCP Registry availability to be future tense.

0.1.3

  • The README, the long description and the Blowhorn skill name the risky tools hidden by default without a count, and add the two that Blowhorn hides after 1.84.0: service_adopt and chrome_attach_chrome_uninstall_agent (blowhorn-ai/blowhorn#1513).

0.1.2

  • Listing copy, the README and the Blowhorn skill no longer say every Blowhorn command is a tool or quote a tool count. From Blowhorn 1.62.0 five risky tools are hidden by default (uninstall, service_uninstall, auth_logout, desktop_build, desktop_install); the README and the long description say how to opt in with --allow-hidden-tool or BLOWHORN_MCP_ALLOW_HIDDEN_TOOLS (blowhorn-ai/blowhorn#1514).
  • hosted/: an interim read-only gateway, a Cloudflare Worker with its own package, until Cloud serves /mcp itself (#8). Its tools are generated from vendored meshery/schemas and checked by make check. It is not part of the npm package. See hosted/README.md.
  • hosted/: every tool call is recorded as a tool_called event in the caller's Cloud activity (POST /api/events, with the caller's own token), posted with ctx.waitUntil and validated against the vendored event schemas (#11). See "What the gateway records" in hosted/README.md.
  • hosted/: wrangler 4.156.0 is a locked devDependency, and make hosted-deploy runs it from hosted/node_modules instead of npx --yes wrangler@4.156.0. Deploying needs Node 22 (hosted/.nvmrc); on an older Node the Makefile stops with one sentence naming the version (hosted/scripts/require-node.js). Every deploy reinstalls from the lockfile first, so a stale node_modules never deploys another wrangler. The Worker tests still run on Node 20 (#12).
  • hosted/: rate limits on /mcp with Cloudflare's Workers Rate Limiting bindings in wrangler.jsonc: 1200 requests a minute per network address, every /mcp request counted, checked before authentication and shared by every client behind one egress address (the only bound on a client that rotates made-up tokens, so one address can still send that many requests a minute that reach Cloud and are refused there with 401), and 60 tool calls a minute per caller, keyed by the hex SHA-256 of the bearer token, checked before any Cloud call. Only a tools/call message counts per caller, one each; initialize, notifications, tools/list and ping never do. The body is parsed once and a JSON-RPC batch is refused with 400 before the caller limit, so it counts nothing, and a body that does not parse is not counted. Over a limit, HTTP 429 with Retry-After and a JSON-RPC error carrying the new code blowhorn-mcp-1010 (ErrRateLimited), whose data is the code's ErrorDefinition with only the refusing limit's cause, and whose id is the refused tools/call's for the caller limit and null for the address limit, which refuses before the body is read; the request is not sent to Cloud, records no activity event, and logs one rate_limited line without the token. A binding missing from env lets requests through and logs one ratelimit_unbound line per isolate naming it (#13).
  • hosted/: the gateway's error codes moved out of src/events.js into a registry file, hosted/errors/mcp.json, in the shape of blowhorn-ai/blowhorn's registry. Every definition gains a moniker, severity, short and long description and reference URL, and is validated by make hosted-check against blowhorn-ai/blowhorn's ErrorDefinition construct, now vendored in hosted/schemas/vendor/blowhorn/, and by the gateway's own rules: unique codes and monikers, nextErrorCode one past the highest code, at least one cause per definition and one remediation per cause. Events send the same metadata.error as before; a failed call's event description now gives its code's shortDescription as the reason, the only copy of that text. hosted/schemas/vendor/SOURCES.json lists one entry per pinned repo (#13).

0.1.1

  • The publish workflow now also publishes server.json to the MCP Registry with GitHub OIDC (mcp-publisher, pinned and checksum-verified), right after the npm publish.
  • The workflow waits for npm to serve the new version before the registry publish, and a rerun for a version already on npm publishes only to the registry.
  • First version published through npm trusted publishing, with provenance.

0.1.0

  • Moved the blowhorn-mcp npm launcher and its shared core (lib/launcher-common.js) here from the private Blowhorn repo, which now mounts this repo as a submodule for its blowhorn-axi launcher. The launcher requires ../lib/launcher-common.js directly; the prepack copy step is gone.
  • Listing files generated from one source, listing/listing.json, and validated against their schemas: server.json for the MCP Registry, now versioned with the npm launcher.
  • Claude Code plugin (.claude-plugin/plugin.json, .mcp.json) and a self-hosted Claude Code marketplace (.claude-plugin/marketplace.json).
  • Cursor plugin (.cursor-plugin/plugin.json, mcp.json).
  • Gemini CLI extension (gemini-extension.json).
  • Glama maintainers (glama.json).
  • Cline install steps (llms-install.md).
  • Agent skill skills/blowhorn/SKILL.md.