Marketing
murakumo.cloud
An MCP server for advertising campaign management that validates, reviews, and submits advertiser creatives according to placement specs and automated Bot review policies.
ENDPOINT 1
https://murakumo.cloud/mcp
MCP server metadata
- Name
- murakumo-ads
- Version
- 1.0.0
Advertiser intake only. Validate, submit with authorization, retain private key, check receipt. No automatic charge or publication.
Known tools 6
murakumo_ads_get_specGet available placement, creative limits, automated Bot review/pricing policy and submission workflow.
Inferred read-onlymurakumo_ads_review_policyRead the full public review criteria, model instructions and outcomes.
Inferred read-onlymurakumo_ads_request_reviewRequest Bot re-review of your receipt (once per 24 hours).
Inferred read-onlymurakumo_ads_validateValidate and preview an advertiser campaign without saving or sending anything.
Inferred read-onlymurakumo_ads_statusRead a private intake receipt with its application_id and submission_key.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.murakumo-ads]
url = "https://murakumo.cloud/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"murakumo-ads": {
"type": "http",
"url": "https://murakumo.cloud/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: murakumo-ads
Remote MCP URL: https://murakumo.cloud/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"murakumo-ads": {
"url": "https://murakumo.cloud/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"murakumo-ads": {
"type": "http",
"url": "https://murakumo.cloud/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "murakumo-ads",
"transport": "streamable-http",
"url": "https://murakumo.cloud/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.