Wire Up a Meta Muse Connector for Reddit Monitoring

Twelve days after Meta launched Muse, a Meta Muse connector for Reddit monitoring is something you build rather than something you install. Meta ships no Reddit connector, and as of 20 September 2026 Reddit appears in no connector list Meta or its executives have published. The route in is the one Meta documents for every service it has not built for you: a Custom Connector, written by the agent itself, against an API you point it at.

The short version: ask Muse to build a custom connector against RedReplier's public OpenAPI spec at https://redreplier.com/openapi.json, paste a redreplier_ token into the secure credential prompt rather than the chat, and keep it to GET /mentions for the first week. Meta does not review what that connector does.

What is a Meta Muse connector?

A Meta Muse connector is an app or service you link to Muse so the agent gains an ability it did not have, and Meta's help centre describes two kinds. The first is a Connector you pick from a list in Settings. The second is a Custom Connector, which Muse builds itself for a service that is not on that list. Meta's own sentence is worth reading closely: "If you want to connect to a service not yet available in the Connector list, you can ask Muse to create a Custom Connector. Muse will guide you through the process, which can involve retrieving API information from the service."

"Retrieving API information from the service" is the whole mechanism. Credentials go into what Meta calls its Secure Credentials Store. Parallel, which built one on 14 September 2026, watched Muse read the documentation, write the client, test the calls and save the integration as a reusable skill that persists into the next conversation. Meta's help pages stop at the credential store and do not say where a finished custom connector lands.

Then there is the sentence that sets the terms for everything below. Meta's help centre says it "doesn't review custom connectors or how they use your information, so grant access with caution." A custom connector is you vouching for the API, not Meta vouching for it. That one line is why every step below keeps the connector on GET calls until you have watched it read for a week.

Can Muse monitor Reddit on its own today?

Muse has no built-in Reddit connector as of 20 September 2026. Meta publishes no public connector directory page on meta.com, ai.meta.com or muse.ai as of 20 September 2026, though muse.ai/platform says an approved connector appears in a directory inside Muse. The fullest list attributable to Meta is a post by Chief AI Officer Alexandr Wang on 8 September 2026, naming Gmail, Google calendar, Outlook, Plaid, Opentable, Google Docs, Spotify, Function Health, Withings, Tailscale, Peloton "and more", plus Instagram, Threads, Facebook and Messenger. Reddit is not on it, and neither Notion nor Granola, the two connectors Meta announced on 18 September, changes that.

So a reader who wants their agent watching Reddit has two routes. Route one is a custom connector against some API. Route two is letting Muse's browser drive reddit.com the way a person would. Meta's browser sub-agent sees an accessibility tree snapshot of the page rather than the raw DOM and cannot run JavaScript in it, which is good for safety and brittle for monitoring: the integration breaks whenever the site changes.

Before anyone plans route three, the local one: Muse runs on a per-user virtual machine in Meta's cloud. Parallel, testing custom connectors on 14 September 2026, put the consequence plainly, that a server running on your own laptop is not reachable, since the VM is in Meta's cloud and not on your network. An MCP server on your machine, a scraper on your machine, a proxy on your machine: all unreachable. Muse also has no "add an MCP server" field. Meta's help centre never mentions MCP for the consumer agent, and the MCP documentation people find when they search belongs to Muse Code, Meta's terminal coding agent, which is a different product with the same brand.

One more thing nobody has settled. No published source documents how Reddit's API terms and rate limits behave when the caller is an agent running on a Meta-owned VM. Meta states that when Muse browses a site the traffic appears as the user's own activity, which makes the question harder rather than easier. Our notes on Reddit's API terms of service and Reddit API rate limits cover the rules for an ordinary client. An agent on somebody else's infrastructure is not an ordinary client, and that is an open question rather than a solved one.

What do I paste into Muse to build the connector?

One message to Muse builds the RedReplier connector, and that message names three things: the spec URL, the auth style, and the scope you want for the first run. RedReplier publishes an OpenAPI 3.0 document at https://redreplier.com/openapi.json, covering 16 paths and 21 operations. Every operation carries a stable operationId and typed request and response schemas, so the spec imports straight into a tool-use format.

Build a custom connector for RedReplier from the OpenAPI spec at
https://redreplier.com/openapi.json
 
Base URL: https://ai.redreplier.com/ai-app/api/v1
Auth: an Authorization: Bearer header. I will paste the token into the
secure credential prompt. Do not ask for it in the chat.
 
For now, use only GET endpoints. Do not call anything that creates,
updates or deletes. Start by listing my monitored websites, then show
me today's new mentions from Reddit sorted by relevance score.

An unauthenticated spec is what makes that a one-message job. Parallel's finding from the same write-up is the reason to check yours before you start: gated docs turn a one-message setup into a browser session. Bearer tokens and API-key headers fit the credential flow directly, which is the other half of why this particular API is an easy target. OAuth-only services need more back and forth.

What can the connector read?

The connector reads monitored websites, tracked keywords, matched mentions and alert settings, which is everything a Reddit monitoring routine needs. A mention carries a relevanceScore from 0 to 100 or null and a source, and GET /mentions returns Reddit, Hacker News, X and Bluesky, so one call answers "what happened on Reddit today" and "what happened across all four sources today" with a filter change.

POST /mentions/{id}/explain changes no mention status and no billing, but the first call generates and stores the explanation, which is why it is a POST. Say so in your setup message, because an agent told "GET only" will skip the single most useful call on the list.

Which calls change state and should need a human?

Eleven operations change state, and PATCH /mentions/{id}/status is the one to worry about. It approves or rejects a mention. An agent with that call available can clear your queue on its own reading, and a rejected mention leaves the queue, so you never see the lead it misjudged and you never learn that it happened.

RedReplier's workflow is human-reviewed on purpose. The product drafts a reply and a person sends it, because unreviewed replies get accounts banned on Reddit faster than they get leads. That rule survives the move into an agent only if you write it down. Meta helps here: by default Muse asks for approval before it sends an email or takes another important action, and Meta says a Connector can be set up so that Muse retrieves data and takes no actions. Set yours that way, then widen it one call at a time once you have watched the agent read for a week.

There is a second reason to hold the line, and it comes from outside Meta. Parallel's 14 September 2026 write-up found that custom connector code runs inside the agent's own runtime cell and does not get the extra privilege separation Meta applies to built-in connectors. Meta documents that separation for the connectors it wrote and says nothing about custom ones either way, so treat this as a third-party finding rather than Meta's position. It still argues for a narrow token.

Where does the RedReplier token go?

The token goes into Muse's secure credential prompt, never into the conversation. Create it at redreplier.com/api-tokens, where it comes back prefixed with redreplier_. API access is included on all three RedReplier plans, so a 401 on the first call means the token is missing, malformed, expired, revoked, or does not start with redreplier_.

Meta's engineering post describes where it lands: credentials and auth tokens for connected services are "stored in a separate isolated container in your VM, not in other Meta services." The agent itself only ever handles a surrogate. Sentinel, a separate approval component on the same VM, swaps in the real credential at the network boundary after the request is authorised. A token pasted into the chat skips every part of that and sits in the conversation instead.

What is the relevance score, and how do I ask Muse about it?

A RedReplier mention carries a relevanceScore from 0 to 100, and POST /mentions/{id}/explain returns the reasoning behind the number. That pair is what makes an agent worth the setup: scoreBuckets cuts the queue before you read it, and the explanation makes a borderline thread judgeable without opening Reddit.

Ask for both in one sentence. "Show me today's high and very high Reddit mentions, and explain the top three" is a GET /mentions with sources and scoreBuckets, plus three explain calls that generate the reasoning the first time. A digest built that way gives you a thread, a score, a reason and a link, which is the entire reading half of triage. The deciding half stays yours.

What does a Meta Muse connector for Reddit monitoring cost?

The connector costs nothing beyond the two subscriptions underneath it. Meta's connectors documentation publishes no fee for custom connectors. As of 20 September 2026 Muse is free up to a weekly usage limit, with a Power plan at USD 20 a month for 500 million Muse tokens a week and a Max plan at USD 100 a month for 3 billion. Parallel reports that custom connector work draws on that same weekly meter rather than a separate one, and Meta's connectors documentation never mentions usage or limits at all.

RedReplier has three paid plans and the API is included on all of them. Starter is $19 a month for 15 keywords, 2 websites, 2 team members and hourly alerts. Pro is $39 a month for 30 keywords, 5 websites, 5 members and alerts every 30 minutes. Business is $79 a month for 50 keywords, unlimited websites, 10 members and alerts every 15 minutes. AI replies and leads are unlimited on every plan, so the plan choice is about keyword count and alert speed rather than volume.

How do I revoke a Muse custom connector?

Revoking has two halves, and the token is the half that actually stops the data. Delete the token at redreplier.com/api-tokens and every call the connector makes returns 401 from that moment, whatever state Muse is in. Then open Settings, then Connectors in Muse and disconnect.

Two caveats worth knowing before you set this up rather than after. Meta says disconnecting stops the data exchange but does not erase what Muse already learned from the connector, and Meta documents a reset that deletes all your Muse data as the way to start from scratch. And Meta's help pages cover disconnecting listed Connectors without documenting how to delete a custom connector the agent built for you. As of 20 September 2026 the connectors, approvals and privacy help pages answer that nowhere. Revoke the token first and the answer matters less.

Frequently Asked Questions

Does Meta Muse support MCP servers?

Parallel's hands-on test found no setting for adding an MCP server in the Muse consumer agent, and Meta's help centre never mentions MCP in its documentation for it. Meta does document MCP in detail, but for Muse Code, its terminal coding agent, which reads an mcp_servers block from a config file. Two products, one brand name. For MCP-capable clients such as Claude, Cursor and Codex, RedReplier runs a hosted server at https://mcp.redreplier.com/mcp with six tools.

Can Muse reply to a Reddit thread for me?

No. RedReplier's public API has no endpoint that posts a reply, so the connector drafts and surfaces rather than publishes. That is deliberate: unreviewed automated replies get Reddit accounts banned, and a reply written in your name is a decision rather than a task.

Will Meta review the connector before it runs?

Meta does not review custom connectors. Its help centre states that it "doesn't review custom connectors or how they use your information, so grant access with caution." The review process Meta published on 18 September 2026 applies to connectors developers submit for the directory, not to one Muse writes for a single user on request.

What happens to my API token if the connector misbehaves?

The token stays in Muse's Secure Credentials Store inside your own virtual machine, in a separate isolated container rather than in other Meta services, and the agent handles only a surrogate for it. Deleting the token at redreplier.com/api-tokens ends every call immediately, which is the fastest kill switch available to you.

Is a custom connector as safe as a built-in one?

Parallel reported on 14 September 2026 that custom connector code runs inside the agent's runtime cell without the extra privilege separation Meta applies to built-in connectors. Meta has not addressed the comparison. Two protections still apply to both: Sentinel governs every outbound request, and the connector code sees only a surrogate credential.

Which other agents can read the same RedReplier data?

Any client that speaks REST or plain markdown reads the same 21 operations behind the same redreplier_ token, and the hosted MCP server exposes six tools against the same account. The Grok bot template for Reddit monitoring covers the Grok Bot route, and the social listening template covers all four sources in one bot.

Is Meta Muse available outside the United States?

Muse launched in the United States on 8 September 2026 and added Canada on 18 September on iOS and web, with Android pending. Subscribing needs a Meta account and an age of 18 or the age of majority where you live. Those are the dates as of 20 September 2026.

Can I run the RedReplier connector from a server on my laptop?

Muse runs on a per-user virtual machine in Meta's cloud, so a server on your own laptop is not reachable. The same goes for an MCP server, a scraper or a proxy on your machine. Point the connector at a public API instead, such as RedReplier's spec at https://redreplier.com/openapi.json.

How do I get a RedReplier API token for Muse?

Create it at redreplier.com/api-tokens, where it comes back prefixed with redreplier_. API access is included on all three RedReplier plans. Paste the token into Muse's secure credential prompt, not the chat. A 401 on the first call means the token is missing, malformed, expired, revoked, or does not start with redreplier_.

Can Muse approve or reject mentions on its own?

Only if the connector is allowed to call PATCH /mentions/{id}/status, which approves or rejects a mention. A rejected mention leaves the queue, so you never see a lead it misjudged. Keep the connector to GET calls for the first week and widen it one call at a time.

Create a RedReplier API token and give Muse a read-only Reddit feed today, or read the agent docs first.

Sources: Meta's Muse connectors help article, Meta's safety engineering post, Parallel's custom integrations write-up (14 September 2026), and the RedReplier OpenAPI spec. Checked 20 September 2026.