Groniz MCP

com.gronizPublished by groniz.comOfficial publisherv1.0.1Updated Oct 24, 2026

Post & schedule to 32+ networks: X, Facebook, Instagram, Threads, LinkedIn, TikTok, YouTube, Reddit.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Groniz MCP lets an assistant publish and schedule social media posts across 32+ networks such as X, Facebook, Instagram, LinkedIn, TikTok and YouTube.

What you can do
  • Publish and schedule social posts to 32+ networks, including X, Facebook, Instagram, Threads, LinkedIn, TikTok, YouTube and Reddit.
  • No tool list is published, so the exact operations available to an assistant are not documented here.
When to use it
Useful when you want an assistant to draft, queue or schedule social media content across many networks from one place instead of posting manually on each platform.
Requirements
A remote MCP endpoint at mcp.groniz.com over streamable HTTP. OAuth authentication is required, with an Authorization header carrying a Groniz API key as a Bearer token.
Before you install
The server can publish and schedule public posts on connected social accounts, so review content before it goes out. It requires a Groniz API key sent in the Authorization header; keep that key private and grant only the accounts you intend to post from.

Installation

In SourceWeft

  1. Open Groniz MCP 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.groniz%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": {
    "groniz": {
      "type": "http",
      "url": "https://mcp.groniz.com/mcp"
    }
  }
}

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.1LatestSep 16, 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.