Bloom for Creators

com.bloomforcreatorsPublished by bloomforcreators.comOfficial publisherv1.0.0Updated Oct 25, 2026

Save and edit social post drafts in Bloom for Creators. Draft-only; cannot publish or delete.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant save and edit social post drafts in Bloom for Creators, without publishing or deleting anything.

What you can do
Save social post drafts to Bloom for Creators from a conversation with the assistant. Edit existing drafts. Draft-only scope: the server cannot publish or delete posts. Access is through a remote endpoint with OAuth sign-in.
When to use it
Useful when you plan social content with an assistant and want the drafts kept in Bloom for Creators for later review, rather than copying text out by hand. It fits a draft-first workflow where a person still reviews and publishes.
Requirements
A Bloom for Creators account, connected through OAuth to the remote endpoint. No local runtime, packages, environment variables or headers are needed. Network access to the provider's endpoint is required.
Before you install
The assistant can create and change draft content in your Bloom for Creators account, so review drafts before they go further. The server states it cannot publish or delete, so publishing stays a manual step. Draft text is sent to the provider's service.

Installation

In SourceWeft

  1. Open Bloom for Creators 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.bloomforcreators%2Fbloom/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": {
    "bloom-for-creators": {
      "type": "http",
      "url": "https://www.bloomforcreators.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.0LatestOct 25, 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.