Get Shouting

app.getshoutingPublished by getshouting.appOfficial publisherv1.0.0Updated Oct 30, 2026

Marketing MCP: social, email, SMS, CRM, paid ads, analytics. OAuth; confirm before send/spend.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote marketing MCP server that lets an assistant work across social, email, SMS, CRM, paid ads and analytics through one OAuth-connected endpoint.

What you can do
  • Manage social, email and SMS marketing channels
  • Work with CRM records and customer data
  • Handle paid advertising campaigns
  • Review marketing analytics and performance data
  • Connect via a hosted remote endpoint with OAuth sign-in
When to use it
Useful when you want an assistant to help run or review marketing work — campaigns, outreach, customer records and performance reporting — from a single connected account instead of switching between tools.
Requirements
A remote MCP endpoint at the provider's hosted address; no local package or runtime is needed. OAuth authentication is required, so a Get Shouting account with the relevant marketing integrations connected is expected. Network access to the provider's endpoint.
Before you install
The server can send messages and spend money on ads; the provider advises confirming before any send or spend action. It reaches customer data in your CRM and marketing channels, and OAuth grants broad access to those accounts. Review what each action will do before approving it.

Installation

In SourceWeft

  1. Open Get Shouting 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/app.getshouting%2Fget-shouting/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": {
    "get-shouting": {
      "type": "http",
      "url": "https://www.getshouting.app/api/mcp"
    }
  }
}

README

This repository has no README.

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 30, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.