Connect Vindex to Claude Code
Claude Code runs in your terminal and writes the files your team ships. Connected to Vindex, it can read your rules before it writes and check the draft against them.
Three steps, about 3 minutes. Open to every registered Vindex user; new users create an account during sign-in, and a new account includes 100 free critique credits.
The walkthrough
Add the Vindex MCP server
In any terminal, register the server once. The --scope user flag makes it available in every project on this machine; leave it off to add it to the current project only.
Claude Code stores the entry in its own settings. Nothing is written to the repository unless you choose project scope, and no key or token is pasted anywhere.
claude mcp add --transport http --scope user vindex https://mcp.vindexgateway.com/mcpSign in with your Vindex account
Start Claude Code and run /mcp. Select vindex and choose Authenticate. Your browser opens the Vindex sign-in; use the same account you use for the Vindex Portal. New users create their account on this screen and start on the free plan.
When the browser says you are signed in, return to the terminal. The /mcp view shows vindex as connected, with its tools and one prompt. Claude Code keeps the session, so you sign in once per machine, not per project.
Run your first critique
Ask your agent to list your rules, then to check a draft against one. Reading your rules is free, and each critique uses one critique credit.
The result comes back in the chat: pass or fail for each rule, with the failing passage quoted.
List my Vindex rules.Check this draft with Vindex against the "Email tone" rule: <paste the draft>What comes back
Each rule gets a pass or fail, and a failure quotes the passage that broke the rule. A rule set also returns one overall result and the names of the rules that failed. The result carries the attempt number and your credits left.
Claude Code does not block anything on its own. It gets the result and decides what to do next: usually, rewrite the quoted passage and run the critique again. Critique results and the loop has every field.
Tell the agent to run the loop
Claude Code reads CLAUDE.md at the start of every session. Put the standing instruction there.
Before you send or save any customer-facing text, check it with the
Vindex validate tool against the rule set named below.
Rule set: <your rule set or rule name>
If a rule fails, rewrite only the passage the result quotes, then run
validate again. Stop when every rule passes, when the attempt limit is
reached, or when credits run out. Then tell the user which rule, if any,
is still failing. Never describe an output as checked unless validate
returned a result for it.An agent that follows it runs the loop on its own, and the server refuses a call over the attempt limit. The standing instructions guide has more.
Troubleshooting
/mcp shows vindex but the tools are missing
The sign-in did not complete. Select vindex in /mcp and choose Authenticate again; the browser step has to finish before tools appear.
The browser opened to a sign-in for a different organization
Vindex uses the organization you pick at sign-in as your company. Sign out in the browser, run Authenticate again, and choose the organization your team scores under.
The agent answered without running a critique
Ask for it in the request: say "check it with Vindex". Put the standing instruction in your client's instructions file so it applies on every task. An agent chooses whether to call a tool, so treat an output as checked only when a result came back.
A critique came back as one sentence with no pass or fail
That sentence is a refusal or an error, such as no credits left, a rule that is not active, or a timeout. Ask your agent to check your credit balance, or try again in a moment.
Using a different client?
Scoring user stories too?
The same connection and the same sign-in also score a story against INVEST. That is part of Integrated Vindex.
Stories in your AI client