Connect Vindex to Cursor
Cursor's Agent edits files across a project. Connected to Vindex, it can read your rules and check what it writes before you accept the change.
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
Open Cursor Settings, go to Tools and MCP (labelled MCP and Integrations in some versions), and choose New MCP Server. Cursor opens mcp.json; add the entry below and save.
Use ~/.cursor/mcp.json to make Vindex available in every project, or .cursor/mcp.json inside a repository to share it with the team through version control. The file holds only the URL.
{
"mcpServers": {
"vindex": {
"url": "https://mcp.vindexgateway.com/mcp"
}
}
}Sign in with your Vindex account
Back in the MCP settings, the Vindex row shows that it needs login. Click it; Cursor opens your browser on the Vindex sign-in. Use the account you use for the Vindex Portal, or create one to start on the free plan.
When the browser confirms, the row turns green and lists the Vindex tools. Cursor keeps the session, so this is a one-time step per machine.
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.
Cursor 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
A rule file in .cursor/rules with alwaysApply set to true is read on every Agent request in the project. 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
The Vindex row shows an error instead of needs login
Check that the URL in mcp.json is exactly the server endpoint and that the entry uses url, not command. Save the file and toggle the server off and on.
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