Developer Guide

How to install the Questa Anonymizer Plugin for Claude

Connect Questa's redaction engine to Claude so names, organizations, and other identifying details can be masked before a conversation continues — without changing how you use Claude for everything else.

questa · claude chat
/anonymize David is head of sales at Questa
→ redaction applied
“PERSON_NAME_2 is head of sales at ORGANIZATION_1”
Entity map kept on your side — never sent to the model.

Watch the walkthrough

Quick answer

The Questa Anonymizer for Claude is Questa AI’s redaction layer, made available inside Claude through a downloadable plugin and connector. Once installed, running /questa:anonymize on a piece of text returns it with detected entities — names, organizations — replaced by placeholders, before you continue working with it in Claude.

People search for this as the “Questa Anonymizer Plugin for Claude,” and that’s a fair way to describe it. Questa ’s own documentation calls it the Questa Connector — installed as a plugin file, then linked through Claude’s Connectors settings.

Why use an anonymization layer with Claude?

Claude is good at synthesizing long documents, spotting patterns, and drafting text — but a lot of the material people want that help with contains information they’d rather not paste into any AI system unmodified. Customer names tied to a complaint history. Salary figures in a compensation review. A vendor’s banking details in a contract.

An anonymization layer sits between the raw document and the model. Instead of manually redacting before every prompt, you trigger a discrete step: text goes in, identifying details come back masked, and you keep working from there.

What you need before installing

  • A Questa Developer Platform account at developer.questa-ai.com
  • A project set up inside that account
  • Enterprise accounts: confirmation from your domain admin that API integration permissions are approved
  • The Claude desktop app — the plugin and connector are set up through Claude's Customize settings, not the browser version
  • Sufficient role permissions in Questa — some slash commands are role-gated

How to install the connector

Sign into the Developer Platform, open Integrations, find Questa Claude, download the plugin, upload it into Claude, connect it, and test it. Here’s the full sequence.

1

Open the Questa Developer Platform

Sign in at developer.questa-ai.com. You’ll land on the platform overview, showing your active project and credit balance.

2

Open the Integrations section

In the left-hand navigation, under Develop, click Integrations. The page splits into general integrations (Slack, ChatGPT) and an “AI interfaces” group that includes Questa Claude and OpenWebUI.

3

Find the Claude connector

Under AI interfaces, click the Questa Claude tile — it should show “Ready to Connect” with an “Open Setup” option — to reach its dedicated setup page.

4

Download the connector

Click Download plugin. If an older Questa plugin is already installed, remove it from Integrations → Questa Claude first — Questa’s own instructions call this out specifically to avoid a broken install. The file you download is questa.plugin.

5

Install it in Claude

In Claude, go to Customize → Plugins → Upload plugin and select the file. Then go to Customize → Connectors, find questa, and connect it — this starts an OAuth flow to authorize the link to your Questa account.

6

Start using Questa within Claude

Type /questa/help to see available commands, then run /questa:anonymize on some sample text. Keep the returned entity map on your side — it’s not meant to be shared with the model.

What happens to sensitive data before AI processing?

Questa is designed to detect and anonymize sensitive information — names and organizations, in Questa’s own examples — when you run the anonymize command on a piece of text. It’s not a blanket setting that rewrites everything you type into Claude; it applies to what you specifically pass to it.

Questa’s own documentation includes a caveat worth repeating: the published example is short, low-ambiguity text, and for higher-stakes use, the guidance is to double-check that masking is complete before relying on it.

Common issues when setting up the connector

  • Plugin won’t update — remove the older version from Integrations → Questa Claude first.
  • Connector doesn’t appear — check Customize → Connectors, not just Plugins; they’re separate steps.
  • Generic access message on a slash command — usually a role/permission issue on the Questa side; contact your admin.
  • Anonymizer status looks off — check the status indicator on the Questa Claude setup page; that’s a Questa-side signal, not a Claude issue.

Frequently asked questions

Questa AI's redaction tool made available inside Claude through a plugin and connector, letting you mask names and organizations in text before working with it further in Claude.
The authenticated integration linking your Questa account to Claude — installed by uploading questa.plugin, then connecting it via OAuth under Claude's Connectors settings.
Download the plugin from Integrations → Questa Claude, upload it via Customize → Plugins, then connect and authenticate via Customize → Connectors.
From the Developer Platform: Integrations → Questa Claude → Download plugin.
No. It adds the anonymize command as something you run on specific text — it doesn't apply automatically to everything you type.
Confirm you completed both parts of setup — uploading under Plugins, and separately connecting under Connectors — using the Claude desktop app.
Yes — the Developer Platform provides a redaction API and an API Playground for testing text and file redaction independent of the Claude integration.
At developer.questa-ai.com, including the API reference, SDK docs, and the Integrations section covering this Claude connector setup.
The Questa Developer Plugin is pay-as-you-go, starting with 100 free credits (roughly 50 pages) that don't expire, with no monthly charge. For on-premise deployments, there's a one-time setup fee plus ongoing maintenance support.

Ready to try it in your own workflow?

If you're evaluating a safer way to work with sensitive information in AI workflows, the next step is to explore the Questa Developer Platform and see how its anonymization layer fits in.

Open the Developer Platform