Blowhorn MCP server
OfficialThis server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Blowhorn MCP Server
Blowhorn is an AI-native social media manager. Connect your MCP client to the hosted server at https://mcp.blowhorn.ai/mcp. It is streamable HTTP. You sign in with your Blowhorn account through OAuth, and the client registers itself, so there is no key to copy and nothing to run on your own machine.
The hosted server is read-only today. It has four tools: getConnections,
getEvents, getContentItem and listContentItems. An agent can review
your connected profiles, your activity and your content. Tool results never
carry secrets.
Reference: https://blowhorn.ai/docs/reference/mcp-server/. Setup notes: https://blowhorn.ai/docs/how-to/set-up/connect-mcp-client/.
Connect
Claude Code
claude mcp add --transport http blowhorn https://mcp.blowhorn.ai/mcpOr install it as a Claude Code plugin from this repo, which also adds the Blowhorn skill. The plugin connects to the same hosted server:
/plugin marketplace add blowhorn-ai/blowhorn-mcp
/plugin install blowhorn@blowhornClaude Desktop
In ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"blowhorn": {
"type": "http",
"url": "https://mcp.blowhorn.ai/mcp"
}
}
}Cursor
In ~/.cursor/mcp.json:
{
"mcpServers": {
"blowhorn": {
"url": "https://mcp.blowhorn.ai/mcp"
}
}
}This repo is also a Cursor plugin (.cursor-plugin/plugin.json and
.cursor-plugin/mcp.json), which adds the Blowhorn skill as well. That
MCP file uses the same hosted URL.
GitHub Copilot CLI
Install the plugin from this repo's marketplace. The install bundles the hosted MCP server and the Blowhorn skill:
copilot plugin marketplace add blowhorn-ai/blowhorn-mcp
copilot plugin install blowhorn@blowhornThe catalog is .github/plugin/marketplace.json in this repository.
Enterprise managed settings can block the plugin. The Agent Plugins MCP
config is the repo-root mcp.json, with type streamable-http and the
hosted URL.
To try this repo before publishing it, run copilot plugin install ./ from
the repo root. Copilot CLI caches plugin components, so run that install
again after you edit them. The install to share is the marketplace one above.
VS Code
In your workspace's .vscode/mcp.json:
{
"servers": {
"blowhorn": {
"type": "http",
"url": "https://mcp.blowhorn.ai/mcp"
}
}
}Gemini CLI
gemini extensions install https://github.com/blowhorn-ai/blowhorn-mcpThe extension's MCP entry is the hosted URL. Sign in when Gemini asks.
Cline
Follow llms-install.md. Add the hosted URL, then sign in when Cline asks.
Arcade
Register the hosted server as a Remote MCP server. Arcade cannot proxy the stdio npm launcher, so use the hosted URL only.
Open Arcade servers, choose Add Server, then Remote MCP.
Set the ID to
blowhornand the URI tohttps://mcp.blowhorn.ai/mcp(Streamable HTTP).Under Advanced settings, choose OAuth2 authorization. Leave Client ID, Client Secret, Authorization URL and Token URL empty so Arcade uses dynamic client registration with PKCE, the same pattern as Arcade's Atlassian remote MCP guide.
Save, complete the Blowhorn OAuth sign-in, then pick the tools in an MCP Gateway.
The hosted tools are read-only: getConnections, getEvents, getContentItem and listContentItems. This server offers tools only: no prompts, resources or sampling. This is a connection you add in your Arcade project. It is not a public Arcade catalog listing.
Related MCP server: SocialHive MCP Server
Example prompts
These only read:
"Show my Blowhorn connections."
"List my content items."
"What events do I have?"
"Show one content item and tell me its state."
If the client does not connect
Sign in when the client opens the Blowhorn login. The URL has to be
https://mcp.blowhorn.ai/mcp. Then restart the client and look at its MCP
log.
More help: https://blowhorn.ai/docs/reference/support/
Privacy Policy
You sign in to the hosted server with your Blowhorn account. Tool results never carry secrets, and tool arguments are never logged.
Privacy policy: https://blowhorn.ai/legal/privacy/
Repository layout
Files marked generated are written by make generate from
listing/listing.json and package.json. Never
hand-edit them: change the source and regenerate. make check fails when
they drift.
Path | What it is | Generated |
| The npm launcher | no |
| Launcher core, shared with the private repo's blowhorn-axi launcher | no |
| The one source of truth for listing facts | no (source) |
| MCP Registry entry | yes |
| Claude Code plugin | yes |
| Claude Code marketplace | yes |
| Cursor plugin. The MCP config is the hosted URL | yes |
| Agent Plugins 1.0 MCP config (GitHub Copilot CLI). Streamable HTTP to the hosted server | yes |
| Agent Plugins 1.0 manifest (GitHub Copilot CLI) | yes |
| Copilot CLI marketplace | yes |
| Gemini CLI extension | yes |
| Glama maintainers | yes |
| Agent skill, found by the Claude, Cursor, Copilot and Gemini packages | no |
| Install steps for Cline | no |
| Official Blowhorn app icon, SVG and 400x400 PNG | no |
| Our schemas for listing.json, Cursor, Gemini, the Copilot marketplace and plugin mcp.json files | no |
| Upstream schemas, byte for byte, with | no ( |
| generate, validate, check and schemas-refresh | no |
| Dev tooling package (Ajv), apart from the published package | no |
| An interim MCP transport proxy to Cloud's | no |
The hosted/ folder holds an interim transport proxy for the hosted server's /mcp; see hosted/README.md.
Development
make install # dev tooling into tools/node_modules and hosted/node_modules
make generate # rewrite the generated files
make check # what CI runs: drift, schemas, copy rules, skill, docs facts, logo, tests, tarball, hosted/npm test runs the same tests as make test; npm run check runs
make check. The dev tooling lives in tools/ because the root package's
"os": ["darwin"] makes npm refuse to install anything at the root on any
other platform, and CI runs there too.
Maintainers
Releases, npm publishing and the MCP Registry: see MAINTAINERS.md.
The version in server.json, and in every plugin and extension manifest,
is this package's version from package.json. The registry entry points
clients at the hosted server.
License
Apache-2.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Draft, schedule and publish social media posts from your AI assistant.
Draft, schedule and publish social media posts from AI agents, under workspace approval rules.
Draft, schedule, and publish social posts for your workspace straight from your AI.
Draft, schedule and publish social media posts to 12 networks from your AI assistant.
Related MCP Servers
AlicenseAqualityBmaintenanceEnables AI assistants to manage social media publishing across platforms like LinkedIn, Twitter, Facebook, Instagram, Threads, and Bluesky.736 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to draft, schedule, and publish social media content, generate AI text and image variations, analyze performance, and automate social workflows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage a social media calendar by listing connected channels, checking network rules, drafting, scheduling, or publishing posts, reviewing scheduled content, adjusting pending post settings, and importing or generating media.MIT

Rizamo MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to publish and schedule social posts across Instagram, Facebook, TikTok, YouTube and more, analyze performance and audience metrics, and manage comments and messages with approval safeguards. It also supports short links with click tracking.6MIT