MCP App Store
by KeenEthics
Audienzes Pro icon

Audienzes Pro MCP Server for Claude and ChatGPT

By Audienzes

Overview

Audienzes Pro adds audience analysis to the Audienzes campaign tools. Describe a segment, such as women 18-24 in Denmark, and Claude shows which interests and themes over-index for it and on which platforms. Compare audience definitions side by side, check whether a segment can be addressed and where, see how interests combine or overlap, read what competitors claim in their ads, follow the direction of trends, see where an audience congregates and what it searches for, and get a behavioural archetype built from the evidence. Results are percentages and indices, never head-counts. Where a platform cannot measure something, the answer says so rather than showing zero, and interpretations are labelled as interpretations. The connector also includes the four campaign tools from Audienzes: list advertising accounts and campaigns, and read impressions, clicks, spend, and daily trends from your connected platforms. It does not change campaign settings.

How to connect

  1. Claude: Open the Audienzes Pro listing in the Claude connectors directory and choose Connect. Claude listing Audienzes Pro exposes 20 tools here.
  2. ChatGPT: Open the Audienzes Pro listing in the ChatGPT app directory and choose Connect. ChatGPT listing Audienzes Pro exposes 21 tools here.

Tools

analyze_overlap

ChatGPT
One audience, nested audiences, or separate territories? A ranked list from profile_segment does not say whether the concepts describe one group of people or several. Three concepts each over-indexing at 140 might be one identity seen from three angles, or three tribes that merely share a demographic. Those lead to different strategies and different buys. It tests whether a set of concepts is one audience. Each pair returns a relation: combine largely the same people; targeting both duplicates nest the smaller sits inside the larger; larger for scale, smaller to concentrate keep_separate different people; separate territories, not one audience undetermined the measurement does not settle it; read why lift is the test, not overlap_pct_of_smaller. A large concept overlaps everything; lift asks whether two concepts co-occur MORE than chance, which is the actual question behind "are these the same people". Two limits are structural and stated in every response. Overlap is measured on ONE source: the one that can measure both interests in the same people reliably. Estimating it where that is not possible would be worse than not measuring it. And a linked group is LINKED, not one identity: A-B plus B-C does not make A-C one audience, so any chain names its unlinked pairs. Pairs too small to measure reliably are held back rather than reported as small numbers, and a lift in the dead zone around 1.0 is reported as undetermined, because rounding there is as large as the signal. Args: country: ISO-2 market. concepts: 2 to 12 canonical concepts. resolve_concepts maps loose wording to them. age_min / age_max / genders: the segment the overlap is measured inside. A different segment can give a different relation for the same pair. for_brand / objective: whose decision this serves, in the user's own words (the user's question works well). The expert reading is written for it. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

brief

ChatGPT
Write a behavioural brief for a segment, directly from the segment and concepts. What it is for: the last step of a positioning or targeting analysis, turning measured evidence into a creative brief a team can work from. Given a segment and concepts, brief measures the audience itself (profile_segment, then analyze_overlap), so no earlier tool results are needed. "Brief for Danish men 18-24 into snowboarding and cycling" is country="DK", age_min=18, age_max=24, genders=["male"], concepts=["snowboarding", "cycling"]. It runs as a background job; get_result returns it. advertisers (two or more) add advertiser positioning to the brief: map_positioning, about 10 minutes for seven. A company or job-role audience (a title such as CISO or IT-chef, a company-size range, B2B) is answered at once with status company_audience and a pointer to Audienzes B2B; nothing is measured. Doubtful wording goes through as a consumer brief. Instead, evidence already gathered, keyed by tool: {"profile": <profile_segment>, "overlap": <analyze_overlap>, "positioning": <map_positioning>, "scope": <scope_market>, "trends": <map_trends>, "listening": <map_listening>} This does NOT summarise. It asks for statements, each carrying the fact it came from, then checks every citation. A statement whose citation does not resolve is DROPPED - it was written from the model's priors rather than from your evidence - and dropped rather than flagged, because a caveat is something a reader can skip. What comes back is a BEHAVIOURAL ARCHETYPE: an addressable group characterised by measured signals. There is no name, no quote, no motivation and no day in the life, because advertising and targeting data cannot evidence any of them. Statements using that language are refused even when correctly cited - a citation does not make a feeling measurable. SET ASIDE 12/10 on David's word (the expert layer): with evidence, the reply is a creative brief (answer_markdown first) whose audience insight and tone are labelled as the strategist's reading, each reason to believe citing the concept and index or ad refs it rests on. Names, portraits and quotes stay out. for_brand / objective (the user's question) set the decision it is written for. background=true still returns the cited-facts brief. Thin evidence returns insufficient_evidence rather than fewer, vaguer sentences. That is not a finding that there is little to say; it means less was gathered than a brief needs. statements_dropped is the most informative part of the output, because it lists what the evidence does not support.

compare_audiences

ChatGPT
Measure one territory across several candidate audiences, and report what separates them. What it is for: "which audience is best supported by the evidence?", for a campaign, a launch or a positioning. This is the audience CHOICE, not a profile. profile_segment answers "what over-indexes for this segment", which starts after someone already picked the segment. It fits when the decision is still open: which definition is best supported by the evidence. Every candidate is measured against an IDENTICAL concept universe - compiled once on the first candidate and reused - so the comparison is not polluted by a drifting concept set. What comes back: - discriminators concepts whose index genuinely differs between candidates, sorted by spread, with the strongest candidate named. - common_ground concepts strong everywhere, which therefore CANNOT justify choosing one candidate. Often the most useful section: it tells a planner what not to build a distinction on. - addressability per candidate per platform, a band over that platform's eligible universe (micro / niche / focused / scaled / broad). Bands are not summed across platforms: the universes overlap. - not_comparable candidates measured on too little to compare. - matrix the full concept x candidate grid with per-platform indices, for auditing any headline. Args: country: ISO-2 market, shared by every candidate. candidates: Explicit definitions, each {"label", "country", "age_min", "age_max", "genders"}. Omit to generate a grid from axes. axes: Grid axes when candidates is omitted: ["age"], ["gender"], or both. A grid over age and gender can only ever discover age and gender differences - that limit is returned in caveats. concepts / theme / domain: The territory. theme compiles it live. platforms: Narrows the platform set; cross-platform is the default. max_concepts: Cap on the universe size (default 12). A spread below 25 index points is treated as common ground, not a discriminator, because each platform rounds differently and small gaps are not findings. This ranks the definitions you chose to test; it does not prove they are natural segments of people. for_brand / objective: whose decision this serves, in the user's own words (the user's question works well). The expert reading is written for it. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

compare_positioning

ChatGPT
What the audience cares about, set against what each brand says: the insight behind each audience signal, which brands' messages answer it, the tensions no advertiser in the set answers, and the moves that follow. What it is for: the open-space question in a positioning, answered with the audience in the room. Pass a profile_segment result and a map_positioning result (as returned), for the same market. Returns answer_markdown first. Each insight is the strategist's reading of a measured signal, labelled as such, with the cheapest test that would confirm it. Args: profile: a profile_segment result. positioning: a map_positioning result. bridges: optional {concept: your reason it matters to the category}; yours are kept beside the strategist's reading. for_brand / objective: whose moves, and toward what decision.

explore_theme

ChatGPT
Turn a theme into a measurable candidate universe, without measuring it. What it is for: the category side of a positioning, i.e. what a theme such as "running" breaks into before an audience is profiled against it. It shows what a theme resolves to before measurements are spent on a full profile - which concepts it breaks into, and which platforms can carry each one. profile_segment(theme=...) does the same build and then measures, so this is for inspection and for letting a human approve the universe first. A platform with nothing credible for a concept is absent rather than loosely matched. Args: theme: Free text, e.g. "winter sports", "home cooking", "fintech". platforms: Restrict the build. Omit to try every platform. max_concepts: Cap on proposed concepts (default 12). country: ISO-2, the market the theme is built for. for_brand / objective: whose decision this serves, in the user's own words. Returns: {"ok": true, "theme", "proposed", "usable", "unbuildable", "detail"} where detail[concept] gives source (curated | discovered | unbuildable) and the platforms that carry it. unbuildable means no platform returned a credible interest, which does not mean the audience lacks it. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

get_campaign_performance

ChatGPT
Covers only the user's OWN connected ad accounts and live campaigns. Audience questions (who an audience is, what it is into, whether or where an audience can be tested or bought) are covered by scope_market, profile_segment and compare_audiences. Read impressions, clicks or swipes, and spend live from an ad platform. Covers one connected account over a rolling window of 1 to 90 days (Amazon: up to 31), optionally narrowed to one campaign_id from list_campaigns. Results include the account currency and date range. When next_page or next_cursor is set, the page totals are not account totals. Amazon returns a report cursor while it prepares the result; the result is final when complete is true. For Amazon this creates a report request at Amazon (identical requests are reused), the only side effect of this tool. These are delivery metrics only, with no conversion, ROAS, profit or causal information. No performance data is stored.

get_campaign_trend

ChatGPT
Covers only the user's OWN connected ad accounts and live campaigns. Audience questions (who an audience is, what it is into, whether or where an audience can be tested or bought) are covered by scope_market, profile_segment and compare_audiences. Daily line chart and date table for one campaign. Available for Meta, TikTok and Google Ads. TikTok supports 2–30 days; Meta and Google Ads support 2–90. account_id and campaign_id values come from list_ad_accounts and list_campaigns. Dates absent from the provider response are unknown, not zero. Daily delivery figures carry no causal information.

get_result

ChatGPT
Fetch a background analysis started with background=true. States: pending, running, partial, completed, failed. While it is running there is NO result field. That is deliberate: a half-built table read as an answer is worse than waiting, and nothing in a half-built payload would contradict a caller who quoted it. A ranking over the sources measured so far is not a ranking over the sources requested. progress reports steps done and what is being measured. completeness states in words whether findings are being held back and why. Handles expire after 24 hours and are readable from any session, so the session that polls need not be the one that started the work. A finished analysis returns its figures at once. If the reply carries an advice block, the strategist's reading (verdict, moves, first test) is still being written. The same job_id (or the advice id) returns it from get_result: advice is gone and answer_markdown is there once it is finished. One call waits up to 45 seconds for a pending or running job; done is true when the reply holds the finished answer.

health

ChatGPT
Report which platforms are answering right now, and what each can express. When a profile_segment result is thinner than expected, a platform missing there may be temporarily offline rather than lacking the concept. A platform reported here as offline will return source_unavailable, which is a gap in our access, not a fact about the audience. Returns: {"ok": true, "platforms": {...}} when the engine exposes platform_health, otherwise {"ok": true, "platforms": {}, "note": "..."} — a server that cannot introspect its sources still reports its own transport as up.

list_ad_accounts

ChatGPT
Covers only the user's OWN connected ad accounts and live campaigns. Audience questions (who an audience is, what it is into, whether or where an audience can be tested or bought) are covered by scope_market, profile_segment and compare_audiences. List connected ad accounts from the user's authorized platforms. Returns each account's ID, name and platform; these account IDs are the account_id values the campaign tools accept. platform filters to one platform; query matches account names, IDs and platform names. Results are 20 accounts per page with next_page (null on the last page), total_accounts and platform_counts. In supporting apps an account picker holds the full filtered list. connect_options holds a direct authorization link for each platform with no connected accounts.

list_campaigns

ChatGPT
Covers only the user's OWN connected ad accounts and live campaigns. Audience questions (who an audience is, what it is into, whether or where an audience can be tested or bought) are covered by scope_market, profile_segment and compare_audiences. List live campaigns for one connected ad account. account_id values come from list_ad_accounts. Returns each campaign's name, status and objective, up to 100 campaigns per call; next_page or next_cursor is set when more campaigns exist. Campaign status is not a performance measure. A missing or expired connection returns ok false with a connect_url for that platform.

list_domains

ChatGPT
List the concept universes available for profiling. A domain is a named candidate universe of concepts — e.g. sports, lifestyle. It matters beyond discovery: domain_index in profile_segment is scored against the mean of the domain's universe, so it is SET-DEPENDENT. Adding a 21st sport changes every score with no new measurement. Each domain therefore reports a universe_version that any result quoting a domain_index carries. Returns: {"ok": true, "domains": [{"domain", "universe_version", "size", ...}], "count": n}. The domains feed resolve_concepts and profile_segment.

map_listening

ChatGPT
Where this audience gathers, and what is actually said there. Defaults to background=true, unlike every other tool here: measured 2026-09-22, a listening run exceeded 600 seconds. get_result returns it. sample_posts are OBSERVED and UNREPRESENTATIVE. A retrieved post is evidence a thing was said. It is not evidence of how widely it is held, and a vivid quote is the easiest thing in this system to over-read. sentiment_balance is conservative by design. Without post text at volume a sentiment score is a guess wearing a number. A community's subscriber count is not your audience - members are not necessarily in this market, let alone in this segment. An empty theme list means our sources returned nothing usable, which is a retrieval fact, not an audience with no interests. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

map_positioning

ChatGPT
Competitor positioning, read by a senior brand strategist: who says what to whom, where the category is crowded, where it is open, and what to do. Reads every advertiser's ads across ad libraries (copy, and the words in the picture when an ad has no copy), extracts each claim, and returns: - answer_markdown: the finished reading, written in English. It opens with the verdict, then a message matrix (brands x functional claims, emotional territory, proof points, audience addressed, tone, offers and calls to action, creative format, share of observed ads), each brand's apparent strategy, crowded and open territory, threats and opportunities, two or three recommended positioning moves with rationale, first test and KPI, the basis of the reading, and the questions to ask next. - strategist: the same reading as data; every line cites ads (A1, A2 ...) whose preview pages are in ads. - positioning_assertions and scope: the evidence, for compare_positioning and brief. What it is for. A request to see competitors' ads is usually a means to a decision: a positioning, a campaign brief, a pitch, or a claim to own. A list of ads is not the answer; the answer is the reading and its move. for_brand (the user's own brand) and objective (e.g. "find a territory to own for a spring launch") write the moves for that brand and goal. Args: market: ISO-2 market, e.g. "DK" ("Denmark" works too). advertisers: at least two, up to twelve, all in one call. The map compares them as one set. Past twelve, the first twelve run and the rest are named. platforms: ad libraries to search. Omit for all. for_brand: the user's brand, if they are one of the advertisers or competing with them. Optional. category: what is being compared, e.g. "running shoes". Optional; ads for other categories are read as context. objective: what the user wants to decide. Optional. country / age_min / age_max / genders: an optional audience to read the claims against. background: true returns a handle that get_result resolves. Measured 10/10: the first ads are back after about 3 minutes, the full reading after about 10. creatives: "with" (default) also brings the ads' pictures for the live display; "without" skips them.

map_search_intent

ChatGPT
What this audience actually looks up. What it is for: the category side of a positioning, i.e. what people in the market search for around the category, in their own words. Seeds are PLANNED, not built from the brand name. Seeding on a brand measures the brand's own search footprint, which says nothing about these people. include_brand=true is available when the brand's own footprint is the question. query_plan goes with the results: the expansion starts from OUR seeds, so a keyword absent from the output was very likely not asked for. Unasked is not unsearched. Search volume is EVENTS, not people, and the people searching are not necessarily your segment. High volume mixes research, comparison, support and idle curiosity, and is not intent to buy. Each keyword's intent is OUR keyword-rule label (English trigger words), not a measure from the source: a query our rule cannot place (another language, or no trigger word) has intent null, which is unknown, and intent_breakdown counts the placed rows only (see intent_coverage). intent_breakdown holds shares of the keyword rows (1 means every row carries that label), not counts. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

plan_analysis

ChatGPT
Shows the plan for a multi-step audience question as a checklist, and fills in each step's state and headline as the analyses run. steps lists the audience tools the answer will use, each with what it is for.

profile_segment

ChatGPT
Profile a segment against a set of concepts, across platforms. What it is for: the audience half of a positioning or a campaign. It shows what a segment cares about, which a map of advertisers' claims cannot. The analytical call. "What kind of sports are women 18-25 in Denmark interested in?" is country="DK", age_min=18, age_max=25, genders=["female"], domain="sports". CROSS-PLATFORM IS THE DEFAULT. Omit platforms and every platform that can answer honestly is measured. platforms NARROWS that set; it does not enable a platform. No head-counts are returned. Percentages and indices are the product. Three metrics, three names, and only one may be called affinity: - penetration_pct — the share of the segment on that platform that shows the concept. Descriptive, and NOT comparable across platforms: the platforms see different populations and each rounds differently. It is not an average across platforms. - domain_index — concept penetration vs the mean of the candidate universe. SET-DEPENDENT: it moves when the universe changes, with no new measurement. Only meaningful alongside the result's universe_version. - affinity_index — [segment ∩ concept / segment] / [country ∩ concept / country] × 100, same platform. 100 = PARITY with the country's adults; above 100 over-indexes, below 100 under-indexes. The definition is identical on every platform; the measurement error is not. Args: country: ISO-2 market, e.g. "DK". Required — every benchmark is same-country, same-platform. age_min: Inclusive lower age bound. Omit for all ages. age_max: Inclusive upper age bound. Omit for all ages. genders: ["female"] | ["male"] | omit for all. Platform-reported gender. theme: Free text such as "winter sports" or "sustainable fashion". The universe is built on request. It covers themes no curated domain fits, which is the normal path for strategic planning. Rows built this way are flagged in notes. domain: Profile a whole universe from list_domains (e.g. "sports"). concepts: Explicit canonical concepts instead of, or narrowing, a domain. resolve_concepts maps loose wording to them. platforms: Narrow the platform set, e.g. ["meta", "tiktok"]. At most 15 known platforms; unknown names are rejected. max_concepts: Cap on concepts measured (default 20). Each concept costs measurements on every platform. At most 25. for_brand / objective: whose decision this serves, in the user's own words (the user's question works well). The expert reading is written for it. industries / company_sizes / job_functions / seniorities: a B2B segment, in plain words ("construction", "ejer", "marketing") or LinkedIn URNs; company_sizes like ["11-200"]. Only LinkedIn can express them: every other platform answers segment_unsupported, which is not 0. The reply is the segment's share of the country's LinkedIn members; concepts are not measured on a B2B segment yet. A name that matches nothing returns invalid_input with the names listed. Returns a ProfileResult: rows (one ConceptRow per concept, ranked, each with consensus_percentile, direction, agreement, evidence_grade, caveats and the per-platform platform_evidence it was synthesised from), plus platform_status, effective_segment_by_platform, universe_version, concepts_omitted, notes and partial. platform_status and effective_segment_by_platform describe how far each number can be read. They are the honesty of the result, not boilerplate: - A platform cell is neither 0 nor []. It is measured, suppressed (measured but the metric is an artifact — e.g. a floor-pinned audience), concept_unavailable, segment_unsupported, different_lens (audience scale or search intent, not affinity), source_unavailable, measurement_unreliable, rate_limited or failed. - ABSENCE IS NOT ZERO. "Reddit cannot express an age segment" is not "young Danes are not on Reddit for sport". - effective_segment_by_platform reports what each platform could actually express. 18-25 is an unlucky boundary: Meta is exact, most others group ages as 18-24 and carry age_distortion_years: -1. A platf…

resolve_concepts

ChatGPT
Turn loose language into canonical concepts, before spending any measurements. It maps free wording to concepts that platforms can express: "skiing" resolves to the skiing concepts, and a compound such as "skisport" (ski + sport) resolves to every concept carrying "ski", marked compound. The result says which platforms can carry each concept. Args: query: Free text — a concept, a synonym, a foreign-language term, or a broad ask such as "sports". Omit to list a whole domain's universe. domain: Restrict to one domain from list_domains (e.g. "sports"). Omit to search every domain. Returns: {"ok": true, "matches": [ConceptMatch], "count": n}, where each match has concept (canonical name), domain, match (exact | alias | fuzzy | compound | ambiguous | unresolved), platforms_available, platform_availability (per platform: available | not offered) and suggestions. An ambiguous or unresolved match is a real answer, not an error: it is returned with suggestions instead of a silent fuzzy match to something else. An unresolved concept has no measurement in profile_segment. platforms_available is a capability list, not a result — a platform missing from it will come back concept_unavailable, which is not zero interest. An unresolved phrase is not a dead end: pass it as theme to profile_segment, which builds a concept universe for it on request. A Danish word can be unresolved where the English term resolves (løbesko: Running shoes).

scope_market

ChatGPT
Is there a credible, executable way to TEST this audience in this market? It answers "can we test / run / buy this audience, and where?" and needs nothing connected. NOT "is this audience good?" - addressability is not desirability. A broad cheap audience may be strategically useless; a niche expensive one may be exactly right. This is an adversarial check on whether an audience hypothesis survives contact with buying reality. It applies early, before a strategy rests on something commercially fictional, and again after profile_segment or compare_audiences, because richer analysis changes the definition and therefore its executability. verdict is CATEGORICAL, not a number: testable | testable_with_material_constraints | not_presently_testable | indeterminate indeterminate means evidence is missing, NOT that feasibility is poor. evaluated_audience comes before the verdict. Each source states the requested definition, the definition it can actually execute, and whether the difference is acceptable, material or disqualifying. The worst way to misread this tool is to take a low cost and a wide band from a source that cannot express the audience that was asked about - every fact correct, the conclusion wrong, because the measured object changed. Environments are grouped by audience_role. Search intent, household audiences and demographic-interest audiences are NOT interchangeable inventory because they share a theme; they may be compared only inside one role. Cost: a class, not a budget. CPM x impressions estimates exposure spend, not the cost of learning, so a range appears only when test_spec supplies a real specification, and is then labelled "estimated media required under stated test assumptions", which is not a recommended budget. interpretation_contract states machine-readable permitted and prohibited inferences. Notably: inventory cost may price inventory and may NOT support CPA or ROAS claims; concentration may describe where people are and may NOT support response propensity. Deliberately absent, because they are too quotable and erase the conditions underneath: feasibility_score, best_platform, cheapest_audience, recommended_budget. Args: country: ISO-2 market. age_min / age_max / genders: the audience hypothesis. concepts / theme: optional territory. Without one, it runs in provisional scoping mode and says so. platforms: narrows the sources considered. test_spec: a real test specification, if you have one. industries / company_sizes / job_functions / seniorities: a B2B segment (plain words or LinkedIn URNs; company_sizes like ["11-200"]). Only LinkedIn can run it; other platforms answer segment_unsupported. for_brand / objective: whose decision this serves, in the user's own words (the user's question works well). The expert reading is written for it. The figures come back at once; the strategist's reading is written afterwards. A reply with an advice block has final figures and a reading still being written; get_result with the job_id in advice.next returns it, and advice is gone and answer_markdown is present once it is finished.

visualize

ChatGPT
Draw a finished result as a picture: PNG image(s) plus a short caption. Pass EITHER job_id (a completed background job) OR result (the object a previous call returned). For the archetype card, result may also be {"brief": <brief>, "profile": <profile_segment>} to draw both together. kind (omit to choose from the result's shape): profile - both charts below, from profile_segment affinity - concepts as bars around 100 (parity), one dot per source heatmap - concept x source index grid; high 150+, medium 100-149, low under 100. A cell that was not measured shows WHY ("no match", "offline", ...): it is not drawn as 0. overlap - analyze_overlap pairs by lift and shared share compare - compare_audiences concepts that separate the candidates scope - scope_market verdict per source card - behavioural archetype card from brief and/or profile_segment matrix - map_positioning's message matrix (brands x message dimensions) and its recommended moves The picture carries the same limits as the result: no head-counts, and absence is labelled and not shown as zero.

analyze_overlap

Claude

brief

Claude

compare_audiences

Claude

compare_positioning

Claude

explore_theme

Claude

get_campaign_performance

Claude

get_campaign_trend

Claude

get_result

Claude

health

Claude

list_ad_accounts

Claude

list_campaigns

Claude

list_domains

Claude

map_listening

Claude

map_positioning

Claude

map_search_intent

Claude

profile_segment

Claude

resolve_concepts

Claude

scope_market

Claude

visualize

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/audienzes-pro"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/audienzes-pro)