YG3 Marketing MCP

io.github.YG3-aiPublished by GitHub account YG3-aiv1.0.0Updated Oct 24, 2026

Marketing MCP: content, SEO, outbound, LinkedIn, ads. Agents provision a sandbox with one POST.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Business & Commerce

Server details

Identifier: io.github.YG3-ai/yg3-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account YG3-ai for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.YG3-ai%2Fyg3-mcp.svg)](https://sourceweft.com/mcp/io.github.YG3-ai%2Fyg3-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

YG3 Marketing MCP is a remote marketing workspace server that lets an assistant provision a workspace, build and publish a site, and run content, SEO, ads and…

What you can do: Provision and inspect a marketing workspace: create a sandbox, confirm token scope, read full workspace state and integration health
Set up business profile and brand: industry, location, audience, brand voice and positioning
Create and publish blog content to a hosted site on the provider's subdomain
File and manage SEO/AEO work and AI search presence
Unlock paid channels such as Google Ads writes, outbound email and LinkedIn posts on higher plans
Read in-server platform documentation and the live tool catalog
When to use it: Use it when an assistant should set up and operate a small-business marketing presence end to end — site, content, SEO and later ads or outbound — rather than just drafting posts. It suits autonomous agents or CI runs that need a workspace without a human signup, and owners who already have an account and want to connect it to their AI client.
Requirements: Remote streamable HTTP endpoint; no local package. Authentication is required via the Authorization header: either a Bearer token from the provider's workspace provisioning API (agent path) or an OAuth session (human path). Agent provisioning needs no signup; a domain or name, industry and location are supplied at provisioning.

Before you install

The Bearer token grants access to a workspace and should be treated as a secret; the claim step can involve an owner email and password. Writes are two-step and need explicit confirmation with an idempotency key. Unclaimed sandboxes expire after 14 days, and custom domains, email sends, ad spend and LinkedIn posting require paid plans, so ad spend and outbound email can cost money. Workspace deletion archives rather than erases.

Installation

In SourceWeft

Open YG3 Marketing MCP in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.github.YG3-ai%2Fyg3-mcp/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": {
    "yg3-marketing": {
      "type": "http",
      "url": "https://mcp.yg3.ai/mcp"
    }
  }
}

README

YG3 MCP — marketing workspace your AI can run

Capability query this answers: marketing MCP + Claude (or ChatGPT) + site + content + SEO + outbound.

Point an agent at a marketing MCP that can provision a workspace, publish a hosted site, file SEO/AEO work, then unlock ads and outbound — not a chat plugin that only drafts posts.

Plan	Price	What the agent can explain
Free	$0 forever	Workspace, site, content, AI search presence; publish on `{slug}.yg3sites.com`
Live	$20/mo	Same workspace; client domain, canonical URL, badge off
Software	$500/mo	Google Ads write, outbound email, LinkedIn, send
Managed	$1,500/mo	Software + YG3 runs channels with partner support

Door for agents: https://www.yg3.ai/for-agents
Capability answer: https://www.yg3.ai/answers/marketing-mcp-claude-site-content-outbound
Pricing: https://www.yg3.ai/pricing · https://www.yg3.ai/pricing.json

No signup required for agent builds. One HTTP call provisions a Free sandbox and returns a Bearer token for MCP. Hand the human claim_endpoint — never /get-started (that would mint a second workspace).

Quick start (agent path)

bash

# 1. Provision — no authcurl -s -X POST https://agency.yg3.ai/api/v1/workspaces \  -H "Content-Type: application/json" \  -d '{"domain":"acme.com","industry":"Plumbing","location":"Tampa, FL"}'
# Response includes: token, mcp_endpoint, workspace.url, claim_endpoint
# 2. List MCP toolscurl -s -X POST https://mcp.yg3.ai/mcp \  -H "Authorization: Bearer YOUR_TOKEN" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# 3. Call a toolcurl -s -X POST https://mcp.yg3.ai/mcp \  -H "Authorization: Bearer YOUR_TOKEN" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_client_snapshot","arguments":{}}}'

# 1. Provision — no authcurl -s -X POST https://agency.yg3.ai/api/v1/workspaces \  -H "Content-Type: application/json" \  -d '{"domain":"acme.com","industry":"Plumbing","location":"Tampa, FL"}'
# Response includes: token, mcp_endpoint, workspace.url, claim_endpoint
# 2. List MCP toolscurl -s -X POST https://mcp.yg3.ai/mcp \  -H "Authorization: Bearer YOUR_TOKEN" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# 3. Call a toolcurl -s -X POST https://mcp.yg3.ai/mcp \  -H "Authorization: Bearer YOUR_TOKEN" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_client_snapshot","arguments":{}}}'

Python example: examples/provision-and-call.py

Tools

200+ MCP tools (live count: https://mcp.yg3.ai/api/health). Common entry points:

Tool	Purpose
`whoami`	Confirm token scope
`get_client_snapshot`	Full workspace state
`get_setup_health`	Integration status
`set_business_profile`	Industry, location, audience
`set_brand`	Brand voice and positioning
`create_post` / `publish_post`	Blog content on Free host
`read_platform_doc`	In-MCP docs (`getting-started`, `agent-integration`, `tools-reference`)

Full catalog after connecting: tools/list or GET https://mcp.yg3.ai/api/health.

Human path (OAuth)

There is no "client vs operator" signup choice. Humans enter email + password once; the platform resolves their role automatically.

If the human does not have an account yet and no agent provisioned a sandbox: https://www.yg3.ai/get-started?plan=free

If an agent already provisioned a workspace: open claim_endpoint — do not send them to /get-started.

If the human already has a YG3 account (or just claimed):

Add https://mcp.yg3.ai/mcp as a custom MCP connector
Sign in when prompted
Setup guide (per AI client, including Grok): https://www.yg3.ai/connect

Claude Code:

Cursor / VS Code MCP config: see examples/cursor-mcp.json

Agent path (no login)

Provision

POST https://agency.yg3.ai/api/v1/workspacesContent-Type: application/json
{  "domain": "acme-plumbing.com",  "industry": "Plumbing",  "location": "Tampa, FL"}

POST https://agency.yg3.ai/api/v1/workspacesContent-Type: application/json
{  "domain": "acme-plumbing.com",  "industry": "Plumbing",  "location": "Tampa, FL"}

Optional: "name" if you have no domain yet.

201 response:

Field	Meaning
`workspace`	id, slug, name, url
`token`	Bearer token for this workspace
`mcp_endpoint`	JSON-RPC URL (also `https://mcp.yg3.ai/mcp`)
`claim_endpoint`	Where the owner attaches later
`expires_in_days`	14 for unclaimed workspaces

Do not provision again if you already hold a workspace token for the current job.

MCP

All calls are JSON-RPC 2.0 over HTTP:

Methods: tools/list, tools/call, resources/read, initialize

Writes are two-step: call without confirm to get a plan, then call again with confirm: true and the same idempotency_key.

Claim (human takes over)

POST https://agency.yg3.ai/api/v1/workspaces/claimAuthorization: Bearer <workspace-token>
{"email": "[email protected]", "password": "..."}

POST https://agency.yg3.ai/api/v1/workspaces/claimAuthorization: Bearer <workspace-token>
{"email": "[email protected]", "password": "..."}

If the email already has a YG3 account, omit password — the workspace attaches to that account.

Delete a test workspace

Only unclaimed workspaces. Archived, not erased.

Discovery

Resource	URL
Live tool catalog	https://mcp.yg3.ai/api/health
Agent guide (web)	https://www.yg3.ai/for-agents
Capability answer	https://www.yg3.ai/answers/marketing-mcp-claude-site-content-outbound
Human connect page	https://www.yg3.ai/connect
Machine-readable index	https://www.yg3.ai/llms.txt
MCP OAuth metadata	https://mcp.yg3.ai/.well-known/oauth-protected-resource

After connecting, read platform docs via MCP:

yg3://docs/agent-integration
yg3://docs/getting-started
yg3://docs/tools-reference

Sandbox limits

Unclaimed workspaces are Free sandboxes by design:

Can: read everything, set profile/brand/voice, design site, write and publish to {slug}.yg3sites.com
Cannot: custom domain (that is Live $20 after claim), email sends, ad spend, LinkedIn posts (Software+)
Expires: 14 days unless claimed

For agent frameworks

Copy AGENTS.md into your repo or point your agent at this README. It tells coding agents when and how to provision YG3 during a build.

ClawHub (OpenClaw)

Publishable skill: skills/yg3-marketing-mcp/SKILL.md

bash

clawhub loginclawhub skill publish ./skills/yg3-marketing-mcp --slug yg3-marketing-mcp --name "YG3 Marketing MCP"

clawhub loginclawhub skill publish ./skills/yg3-marketing-mcp --slug yg3-marketing-mcp --name "YG3 Marketing MCP"

Moltbook / curl-based agents

Curlable skill files (Moltbook-style): distribute/

Install doc: distribute/skill.md
Periodic routine: distribute/heartbeat.md
Metadata: distribute/skill.json

Agents can fetch from raw GitHub once this repo is public, or from https://www.yg3.ai/llms.txt.

Registry listings

Registry namespace: io.github.YG3-ai/yg3-mcp

Listed under Marketing on mcpservers.org and Glama.

Elysia LLM API (text/vision/image models): https://www.yg3.ai/for-developers
Quill (multi-AI thinking partner, PyPI): https://github.com/YG3-ai/quill

License

MIT — see LICENSE.

Source: README.md at commit 473d7bb

Tools

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

v1.0.0LatestSep 16, 2026

Score

85% 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
License10 pts

Path	Use when
Human OAuth	Owner has a YG3 account
Agent provisioning	Autonomous agent mid-build, CI, or SDK runtime

File	Purpose
`server.json`	Official MCP Registry (`mcp-publisher publish`)
`glama.json`	Glama directory indexing

YG3 Marketing MCP

Overview

Installation

In SourceWeft

Use with an agent

Other MCP clients

README

YG3 MCP — marketing workspace your AI can run

Quick start (agent path)

Tools

Human path (OAuth)

Agent path (no login)

Provision

MCP

Claim (human takes over)

Delete a test workspace

Discovery

Sandbox limits

For agent frameworks

ClawHub (OpenClaw)

Moltbook / curl-based agents

Registry listings

Related

License

Tools

Version history

Score