Your agent can read the business before it writes.Mora gives it the brand, catalog, plans, and performance behind the brief.

Cannot post, schedule or change adsOAuth 2.1 + PKCENo API keys to paste
~/Dev/your-storeCannot publish
❯
claude plugin marketplace add https://github.com/Mora-AI-Content-Studio/mora-claude-plugin
claude plugin install mora

Preview the supported install. This does not run a command on your device.

read
The card being readOne tray each for 10 of the mora.read toolsThe stamp, pinned up: no tool can publish34 tools on the live server card: 30 read the account and 4 write to its knowledge library behind the separate mora.write.knowledge scope. The trays draw ten of the mora.read tools; the ad tools need mora.read.ads. No tool can post, schedule or change ads. The tour replays the context trace below: get_brand_profile, list_products, get_post_performance, list_projects.

The first draft starts with evidence.

An agent can check the brand profile, product catalog, current plan, and recorded performance before it suggests the next piece of content.

Explore the tools
Agent context trace
1
get_brand_profile

Load the account’s voice, audience, offerings, and content pillars.

2
list_products

Confirm the products and names that are actually in the connected catalog.

3
get_post_performance

Check recorded post performance before choosing an angle.

4
list_projects

See what is already planned before adding more work.

34 tools, grouped by what an agent checks.

Listed from the live server card: 30 read, and 4 write to the knowledge library behind mora.write.knowledge. Each response stays inside the authenticated Mora account.

Know the brand

Start with what the business sells, who it serves, and how it sounds.

get_brand_profile

What this business is: name, what it sells, who it sells to, voice, and its offerings, led by the workspace's voice canon (governing documents, rules, banned terms) when it has one.

list_products

This account's Shopify catalogue.

list_audiences

This account's defined audiences: who they're for, what they want, and their exact pain language.

list_workspaces

This account's workspaces (brand kits): one Mora client/brand each.

See the work

Check what is published, planned, and already in motion before proposing more.

list_posts

List this account's social posts, newest first, optionally filtered by status.

list_projects

This account's content projects and their scheduled slots.

get_brief_workspace

A bounded, redacted workspace snapshot for one authenticated account Brief: its objective, safe research state, products, personas, concepts, delivery intents, evidence decision, and blockers.

list_brief_runs

This account's brief-order runs and every step's research finding.

list_content_angles

This account's content angle bank, ranked by reach x urgency x durability.

Use the evidence

Bring recorded organic and store performance into the conversation.

get_post_performance

This account's best-performing published posts with engagement metrics.

get_revenue_attribution

This account's Shopify revenue attributed to marketing channels, first- and last-touch.

get_workspace_insights

This workspace's own /insights conclusions in one call: classified business model, business-health pillars, and the headline figures that model actually opens on.

Read the ads

Provider-reported delivery from the connected Google, Meta and LinkedIn ad accounts. Read only; no tool changes a budget, bid or status.

get_paid_campaign_performance

This account's Google Ads, Meta Ads and LinkedIn Ads campaign delivery: provider-reported spend, impressions, clicks, conversions and conversion value, never summed across currencies. Needs the separate mora.read.ads scope.

get_paid_delivery_status

For this workspace's connected ad accounts, what Mora actually has stored, the real synced calendar range and connection health, before trusting any other paid tool's numbers.

get_paid_trend

A daily, weekly, or monthly time series of paid delivery, spend, impressions, clicks, leads and purchases, per provider and per currency, with the prior window's totals and delta.

get_paid_audience_delivery

Who a paid campaign (or the whole connected ad account) actually reached on LinkedIn Ads and Meta Ads: seniority, industry, job function, company size, age, gender, country/region.

get_creative_performance

Per-ad/creative delivery for one named campaign on one provider: which specific creative is carrying or dragging a campaign's numbers.

get_google_search_terms

The search terms that triggered this workspace's Google Ads, as Google stores them: spend, clicks and conversions per term, the hidden-terms remainder Google withholds, and spend-without-conversion review candidates.

get_conversion_setup

This workspace's conversion-tracking readiness across LinkedIn Ads, Meta Ads and Google Ads: not how many conversions happened, whether tracking is actually wired to convert.

audit_paid_account

A deterministic health scorecard for this workspace's connected ad account(s): data freshness, delivery, conversion signal, Google auction, and structure, each with a status and evidence.

estimate_linkedin_audience

Estimate a LinkedIn Ads audience size before a campaign exists, from free-text targeting terms (locations required; job functions, seniorities, industries, job titles and companies optional). Needs the separate mora.read.ads scope.

get_linkedin_campaign_setup

Read how one named LinkedIn Ads campaign was built: targeting facets (raw URNs), schedule, format, budgets, and creative copy: setup, not delivery. Needs the separate mora.read.ads scope.

list_linkedin_matched_audiences

This LinkedIn Ads account's synced matched-audience segments and account/contact lists, with real member-count sizes: not the same object as list_audiences (hand-authored personas). Needs the separate mora.read.ads scope.

get_linkedin_conversion_tracking

This LinkedIn Ads account's Insight Tag status and synced conversion rules, so conversion-tracking readiness can be checked before crediting or ruling it out. Needs the separate mora.read.ads scope.

Search the knowledge library

Read the saved sources and check a draft against them. All six are read only.

search_sources

Search the workspace's saved knowledge library and get cited passages (document, page, heading, exact span) with source-authority labels.

read_source

Read the full extracted text of one saved source, with its note and governance labels.

list_sources

List saved knowledge sources with their note, status and governance labels.

verify_draft

Check a draft against the library sources it cites: figures and quotations not found in them, and text copied from internal sources into external copy.

review_draft

An independent second opinion on a draft from Claude Opus 5.5, run by Mora on its own API key: claims against the cited sources, internal material in external copy, inference stated as fact, dated facts, unapproved results, the ask and the workspace voice.

check_copy

Check a draft against the workspace's voice rules: banned terms with replacements, em dashes, stock AI phrasing, and quantified claims that must be confirmed as approved proof.

Write to the knowledge library

The four tools that write, all behind the separately consented mora.write.knowledge scope. They add or relabel sources and never delete.

save_source

Add a link, document text or note to the workspace's knowledge library. Needs mora.write.knowledge.

upload_attached_file

Save a file the person attached in the chat to the workspace's knowledge library, original kept. Needs mora.write.knowledge.

request_upload_link

Get a one-time, 30-minute link where the person uploads an original file (PDF, Word, text, email) to the workspace's knowledge library. Needs mora.write.knowledge.

update_source

Change one saved source's labels, note or status (superseded, archived), or record who approved it as proof. Needs mora.write.knowledge.

It can read. It cannot publish.

An agent can gather context and prepare work, and the 4 knowledge-library write tools can save, upload and relabel sources, but it cannot post, schedule or change ads.

  • Publish or schedule a post
  • Change connected social accounts
  • Change a budget, bid, or status in an ad account
  • Edit your brand kit or brand voice
  • Change billing or plan settings
  • Redistribute the licensed Discover feed

How clients connect, and what the server returns.

Read the architecture guide

Connect your Mora account to Claude.

The Claude Code plugin installs now. It connects to your Mora account once your waitlist access opens.

Join waitlistInstall the plugin