# Parse Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Parse

See how ChatGPT and Google AI Mode name, recommend and cite your brand

- Record: https://musedirectory.ai/connector/parse
- Category: Marketing & Ads
- Developer: Parse (https://parse.gl/docs/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 469ms, checked 2026-11-13T10:30:59Z
- Endpoint: https://agent.parse.gl/mcp
- Auth: Sign in with your account; Pricing: unknown
- Screening: Screened, no issues found (2026-11-12T15:26:25Z)
- Source: Found in the official MCP Registry (gl.parse/mcp) https://registry.modelcontextprotocol.io/v0/servers?search=gl.parse%2Fmcp

Connects to Parse, which tracks how AI assistants such as ChatGPT and Google AI Mode describe, recommend and cite brands. Muse can pull visibility reports, compare your brand against competitors and show which sources the models quote.

Example request: "How does ChatGPT describe my bakery compared with the shop down the street?"

How to connect: Parse is not in Muse's Connectors list yet, and it needs you to sign in with your Parse account. Apps that need this kind of sign-in usually cannot be used from a Muse chat yet. Follow it here and we will tell you when it reaches Muse.

Tools:
- check_brand: First question about one brand: how often AI mentions it and who is picked instead. Takes the brand's website (best), its name or a brd_ id, and answers in one call. For a brand Parse knows well: its share named and recommended in each of its markets, the brands named most in the
- resolve_ids: Turn brand names, domains, URLs, topic, market or place names ("Austin, TX"), or question wordings into Parse's typed ids (brd_, top_, mkt_, plc_, qst_, pg_, site:), up to 25 at once. Each match says why it matched, its score, and whether you track it; brands say whether Parse ha
- list_facets: The fields you can filter (filter.facet) and group by (by: facet:<key>): each judgment's definition, values, source, judges, measured quality (labels by Claude annotators, not humans) with its tier, and coverage in your scope over the last 28 days (on the counted engines); the en
- query_metrics: Count, share, trend: answers, share named / recommended / first, position, tone and treatment mix, citations, pages and sites cited, comparisons won and lost (one brand: subject), search_reach (a brand's sites in retrieved result lists; no by), memory_gap (a brand named with sear
- search_answers: Search AI answers by brand (named, recommended, first, not named, warned), topic, market, question, engine, place the question is about (plc_ ids) or country asked from, site or page cited, keywords or phrases (filter.text), or any facet from list_facets. Compact rows with ids; o
- search_cited_pages: Pages AI answers cite, by brand, topic, market, question, engine, site or facet. For outreach pass pages = third_party: most cited pages are brands' own sites, and this leaves them out. Each row: citations, answers and questions citing it (over the whole filter), weeks cited, ans
- get_brief: Needs a free Parse sign-in, which this call asks the person for: the person's own brand's brief (what changed, what to do next) and their work record. Call it only when the person wants their own brand, tracking or their record, or says yes to an offer; for any public question us

Screening checks:
- MCP handshake: pass (Requires sign-in (publishes OAuth metadata))
- Domain against threat feeds (Cloudflare security DNS): pass (agent.parse.gl, parse.gl not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: n/a (Tools are behind sign-in)
- Inputs asking for passwords, card numbers or seed phrases: n/a (Tools are behind sign-in)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)