Repliz

English

Bahasa Indonesia

English

Bahasa Indonesia

Appearance

Claude Website ​

Connect Repliz to Claude at claude.ai and manage Repliz from the chat in plain language: ask Claude to list the comments waiting for a reply, answer them, schedule a post, or check an account's stats.

Before you start ​

  • A Standard, Premium, or Gold Repliz plan. On the Free plan the Public API page is locked. The tools Claude can use follow your plan; see Available tools.
  • A Claude account. Custom connectors work on every Claude plan; the Free plan allows one. On Team and Enterprise, an Owner adds the connector; see On Claude Team and Enterprise.

The Claude pictures are illustrations

The pictures of Claude on this page are drawn from Anthropic's own guide, with Claude in English. The dialog looks a little different from one account to another, so look for the same labels even if they sit elsewhere.

1. Copy your Repliz keys ​

  1. Open Settings → Public API in the Repliz dashboard. It's under Integrations in the settings menu.

    The Public API page in Settings, with Public API highlighted in the settings menuThe Public API page in Settings, with Public API highlighted in the settings menu

  2. Copy the Access key and the Secret key with the copy button next to each. You'll paste them into the Repliz sign-in page in step 3.

    The Keys card with the copy buttons next to the access key and the secret key highlightedThe Keys card with the copy buttons next to the access key and the secret key highlighted

Keep the keys private

Anyone with both keys can act on your Repliz workspace. Don't share them or paste them anywhere other than the Repliz sign-in page.

2. Add the connector in Claude ​

  1. In Claude, open Customize → Connectors, click + Add, and choose Add custom connector.

    Illustration: the Connectors page with the Add menu open and Add custom connector highlightedIllustration: the Connectors page with the Add menu open and Add custom connector highlighted

  2. Enter Repliz as the Name and https://mcp.repliz.com/mcp as the Remote MCP server URL, then click Continue.

    Illustration: the Add custom connector dialog with the name and the URL filled in and Continue highlightedIllustration: the Add custom connector dialog with the name and the URL filled in and Continue highlighted

  3. Under Authentication, choose Sign in now. Under OAuth client, keep Use Claude's published identity. Then click Add.

    Illustration: the authentication settings with Sign in now and Use Claude's published identity selected, and the Add button highlightedIllustration: the authentication settings with Sign in now and Use Claude's published identity selected, and the Add button highlighted

A different dialog?

Register automatically works too. If your dialog shows the name, the URL, and Advanced settings on one screen instead, fill in the name and the URL, leave Advanced settings empty, and click Add.

3. Sign in to Repliz ​

  1. Claude opens the Repliz sign-in page in a new window. If it doesn't, click Connect next to Repliz in Customize → Connectors.

  2. Paste your Access Key and Secret Key, and click Connect.

    The Repliz sign-in page for Claude with both keys filled in and Connect highlightedThe Repliz sign-in page for Claude with both keys filled in and Connect highlighted

  3. Repliz checks the keys and sends you back to Claude, where Repliz now shows as connected.

The sign-in page says where it will send you back. For Claude it is claude.ai; if it names any other address, click Cancel.

4. Turn it on in a chat ​

  1. Start a new chat. Click + in the message box, choose Connectors, and turn Repliz on.

    Illustration: the + menu of the message box with Connectors open and Repliz turned onIllustration: the + menu of the message box with Connectors open and Repliz turned on

  2. Ask something, for example "Show my connected Repliz accounts."

  3. Claude asks before it runs a Repliz tool. Check which tool it wants to run, then allow it. Claude then answers with your data.

    Illustration: Claude answering with the list of Repliz accounts after running repliz_list_accountsIllustration: Claude answering with the list of Repliz accounts after running repliz_list_accounts

For more ideas, see the usage examples.

Control what Claude may do ​

Some Repliz tools change things: they reply to comments, send DMs, schedule posts, and delete. In Customize → Connectors, select Repliz to set a permission for each tool. Set the ones you don't need, such as repliz_delete_account or repliz_delete_content, to Blocked.

Choose Always allow only for tools you trust to run without asking, such as the ones that only read. Comments and messages from strangers can carry instructions aimed at Claude, so read what it proposes before you approve a reply, a DM, or a deletion.

On Claude Team and Enterprise ​

On Team and Enterprise, an Owner adds the connector for the whole organization, and each member signs in with their own Repliz keys:

  1. The Owner opens Organization settings → Connectors, clicks Add, and chooses Custom, then Web if Claude asks.
  2. The Owner enters the URL, chooses Sign in now if Claude asks, and clicks Add.
  3. Each member opens Customize → Connectors, finds Repliz with the Custom label, clicks Connect, and signs in as in step 3.

Each member then works in the Repliz workspace of the keys they signed in with. For a team that shares one workspace, everyone signs in with that workspace's keys, or the Owner saves them once as a request header.

Alternative: a request header ​

Instead of a sign-in, Claude can send your keys in an authorization request header on every request. This suits a Team or Enterprise Owner who wants every member to use one key pair. Request headers are in beta and only some Claude accounts have them so far.

  1. Make the header value. It is Basic, a space, and then your AccessKey:SecretKey encoded in base64. Paste both keys below and copy the result.

    Header value
    Paste both keys to get the value.

    Worked out in your browser. Your keys are not sent anywhere.

    Prefer to make it yourself?

    In a terminal on macOS or Linux, put your own keys in place of ACCESS_KEY and SECRET_KEY:

    sh
    echo -n 'ACCESS_KEY:SECRET_KEY' | base64

    Then put Basic (with the space) in front of the result.

  2. Add the connector as in step 2, but under Authentication choose No sign-in.

    Illustration: the authentication settings with No sign-in selected and highlightedIllustration: the authentication settings with No sign-in selected and highlighted

  3. Open Request headers and add one header:

    • Header: choose authorization from the list.
    • Value: paste the value from step 1, starting with Basic .
    • Tick Required.

  4. Click Add.

    Illustration: the request headers with authorization set to a Basic value and Required ticked, and the Add button highlightedIllustration: the request headers with authorization set to a Basic value and Required ticked, and the Add button highlighted

One key pair for everyone

When an Owner saves the header, every member who uses the connector sends the same keys. Everyone therefore works in that one Repliz workspace, with the right to reply, schedule, and delete. Only use keys whose workspace every member may use.

Troubleshooting ​

The sign-in page says Repliz didn't accept the keys. Copy both keys again from Settings → Public API. If the Secret Key was reset, only the new one works.

The sign-in page says the link has expired. The page stays valid for 15 minutes. Go back to Claude and click Connect again.

Claude asks you to sign in to Repliz again. This happens after the Secret Key is reset, or when the connector hasn't been used for 30 days. Sign in again with your current keys.

Claude says a tool isn't on your plan. The tools follow your Repliz plan. See Available tools for which plan each group needs.

With a request header ​

There is no Request headers section. Your Claude account doesn't have the beta yet. Sign in with Repliz instead, as in step 2.

Claude rejects the header name. Claude only sends header names that Anthropic has approved. Choose authorization from the list instead of typing X-Repliz-Access-Key or X-Repliz-Secret-Key.

The connector doesn't connect, or Claude says it is unauthorized. The header value is usually the cause:

  • It must start with Basic and one space. Claude sends the value exactly as you typed it.
  • The encoded text must be AccessKey:SecretKey, joined by a colon with no spaces.
  • If the secret key was reset in Repliz, the old value no longer works.

Claude can't change the header of a saved connector. Remove the connector in Customize → Connectors and add it again with the new value.