Other Apps

Any app that connects to remote MCP servers can use Repliz. This page covers Cursor and VS Code, then what to look for in any other app.

Before you start

• A Standard, Premium, or Gold Repliz plan. The tools your app can use follow your plan; see Available tools.
• Your Access key and Secret key from Settings → Public API in the Repliz dashboard.

Sign in, or send a header

Every app connects to https://mcp.repliz.com/mcp in one of two ways:

• Sign in with Repliz. If the app can sign in to MCP servers (with OAuth), give it only the URL. It opens the Repliz sign-in page, where you paste your keys once. See Sign in with Repliz.

• Send a header. Otherwise, set an Authorization header: Basic, a space, and your AccessKey:SecretKey encoded in base64. Paste both keys below and copy the result.

  Access KeySecret Key

  Header value

  Paste both keys to get the value.

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

Cursor

Add Repliz to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "repliz": {
      "url": "https://mcp.repliz.com/mcp"
    }
  }
}

Cursor sees that Repliz needs a sign-in. Open Customize in the sidebar, find Repliz among your MCP servers, and click Connect. Your browser opens the Repliz sign-in page; paste your keys and click Connect there too.

To send the header instead, read it from an environment variable rather than writing the key into the file:

{
  "mcpServers": {
    "repliz": {
      "url": "https://mcp.repliz.com/mcp",
      "headers": {
        "Authorization": "${env:REPLIZ_AUTHORIZATION}"
      }
    }
  }
}

Set the variable in your shell profile, for example export REPLIZ_AUTHORIZATION="Basic YOUR_VALUE", then restart Cursor.

VS Code

In VS Code with GitHub Copilot, run MCP: Add Server from the Command Palette, choose HTTP, enter https://mcp.repliz.com/mcp, and name it repliz. Or add it yourself, to .vscode/mcp.json in a workspace or to your user configuration (run MCP: Open User Configuration):

{
  "servers": {
    "repliz": {
      "type": "http",
      "url": "https://mcp.repliz.com/mcp"
    }
  }
}

The first time Repliz starts, VS Code asks to sign in to it. Allow it, and your browser opens the Repliz sign-in page.

To send the header instead, let VS Code ask for the value once and keep it out of the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "repliz-authorization",
      "description": "Repliz Authorization header (Basic …)",
      "password": true
    }
  ],
  "servers": {
    "repliz": {
      "type": "http",
      "url": "https://mcp.repliz.com/mcp",
      "headers": {
        "Authorization": "${input:repliz-authorization}"
      }
    }
  }
}

Any other app

Look in the app's settings for a remote MCP server, a custom connector, or a Streamable HTTP server, and enter https://mcp.repliz.com/mcp. If it offers a sign-in or OAuth, choose that. If it only takes headers, add the Authorization header with the value from above.

An app that can only start MCP servers on your own computer can still reach Repliz through mcp-remote, the same way as the local config in Claude Desktop.

Troubleshooting

The app says Repliz needs a sign-in but never opens the sign-in page. Some apps can't sign in to MCP servers yet, and in some versions of Cursor the Connect button does nothing. Send the header instead.

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 app reports 401 Unauthorized with the header. Check that the value starts with Basic and a space, and that the secret key hasn't been reset since you copied it. Writing Bearer in place of Basic doesn't work.

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