FeedHive

com.feedhivePublished by feedhive.comOfficial publisherv1.0.0Updated Oct 24, 2026

Create, schedule and analyze social media posts across your connected accounts with FeedHive.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

FeedHive's remote MCP server lets an assistant create, schedule and analyze social media posts across the accounts connected to a FeedHive workspace.

What you can do
Create and schedule social media posts for the accounts connected to FeedHive, as described in the registry entry. Review post performance and analytics for those connected accounts. The manifest lists no individual tools, so the exact set of actions is not documented here.
When to use it
Useful when you manage social media through FeedHive and want an assistant to draft, schedule or review posts without switching to the FeedHive interface.
Requirements
A remote MCP endpoint at mcp.feedhive.com over streamable HTTP. Authentication is required: either OAuth sign-in or a FeedHive API key sent in the Authorization header as a Bearer token. A FeedHive account with connected social accounts is implied.
Before you install
The server can create and schedule posts on connected social accounts, which publishes content publicly, so review anything it drafts before it goes out. It requires an API key or OAuth authorization that grants access to your FeedHive workspace; keep the key secret. Post and analytics data is handled by FeedHive as a third party.

Installation

In SourceWeft

  1. Open FeedHive in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.feedhive%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "feedhive": {
      "type": "http",
      "url": "https://mcp.feedhive.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.