Styleforge

io.styleforgePublished by styleforge.ioOfficial publisherv1.1.0Updated Oct 24, 2026

Brand-aware creative studio for Claude: 200+ tools for on-brand ads, video, email and campaigns.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

A remote, OAuth-protected creative studio that gives an assistant over 200 tools for producing on-brand ads, video, email and campaigns.

What you can do
Styleforge connects an assistant to a brand-aware creative studio. According to its description, it exposes more than 200 tools for creating on-brand ads, video, email and campaigns. It runs as a hosted remote endpoint rather than a local package. No individual tools are listed in the supplied material.
When to use it
Relevant when an assistant needs to produce marketing creative such as ads, video, email or campaign assets while staying consistent with a brand. Less useful for tasks outside creative and campaign production.
Requirements
A remote MCP connection to the hosted endpoint at app.styleforge.io over streamable HTTP. Authentication is OAuth and is required, so a Styleforge account and an OAuth authorization flow are needed. No environment variables, headers or packages are declared.
Before you install
Access is granted through OAuth to a hosted third-party service, so brand and campaign material is handled on that provider's platform. The material does not say which tools write, publish, send or delete content, or whether any action costs money; check this before granting access.

Installation

In SourceWeft

  1. Open Styleforge 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/io.styleforge%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": {
    "styleforge": {
      "type": "http",
      "url": "https://app.styleforge.io/api/mcp/v1"
    }
  }
}

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.1.0LatestSep 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.

Other Styleforge integrations