ProvelyCursor connects to Provely through the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. Cursor never holds the verifier credentials.
A person verified the Cursor capabilities on 2026-09-05. Agent products change monthly. Re-verify before you build.
Source: integration profile cursor · retrieved 2026-09-05
Which surfaces does Cursor use?
| Surface | Support | Detail |
|---|---|---|
| MCP server | Verify at implementation | transport stdio |
| CLI | Supported | Runs through the shell tool of the agent. |
| SDK | Not supported | |
| REST API | Supported | Any HTTP call reaches the control plane. |
Which guidance files does Cursor read?
The renderer writes Cursor rules file from one source. A new agent needs a profile, not core code.
| Format | Path | Mode |
|---|---|---|
| Cursor rules file | .cursor/rules/provely.mdc | write |
| CI gate workflow | .provely/ci/github-actions.yml | fragment |
How is a false completion claim blocked?
| Enforcement | Support | Detail |
|---|---|---|
| Advisory guidance | Supported | The instruction files state the rules for every agent. |
| Lifecycle hooks | Verify at implementation | No hook events stated. |
| CI gate | Supported | provely verify --wait fails the pipeline unless the verdict is VERIFIED. |
How do I connect Cursor?
Connect Cursor to Provely
- Install the CLI.Run
npx provely --version, or download the static binary. - Check the MCP support of the host.The profile marks MCP as verify at implementation. When the host runs MCP, register
provely mcp. If not, use the CLI through the shell tool. - Write the guidance files.Run
provely init --agent cursor. It writes.cursor/rules/provely.mdc(write),.provely/ci/github-actions.yml(fragment). The guidance carries one rule: a successful tool call is not completion. - Add the CI gate.Run
provely verify --wait <duration>in the pipeline. The step fails unless the verdict is VERIFIED. Exit codes: 0 VERIFIED, 2 PENDING, 3 FAILED, 4 CONTRADICTED, 5 UNVERIFIABLE. - Report the verdict exactly as returned.VERIFIED: "The action is verified complete. Receipt: <id>." PENDING: "The action is accepted but not yet verified. Operation: <id>."
What else does the profile state?
- Checked 2026-09-05: the network policy of the build host blocks cursor.com. No reachable primary source confirmed the rules format, the MCP config file, the hooks, or the host version. The claims below come from the team knowledge of 2026-06.
- Rules: .cursor/rules/*.mdc with description, globs, alwaysApply. MCP: .cursor/mcp.json with mcpServers. Both are verify_at_implementation until a person reads https://cursor.com/docs. Add the provely entry to .cursor/mcp.json by hand after that check.
- Cursor hooks: not verified on 2026-09-05. Keep verify_at_implementation. Until then, use the rules file and the CI gate.
- The CI gate covers background and cloud agents. Verdicts land in pull request checks.
Cursor keeps its action credentials, and no surface returns the verifier credentials to it. Read the credential boundary. An operation outlives the session that opened it. Read the API reference.
Which host versions does the profile cover?
>=1.0.0. The integrations team last verified the profile with not verified on 2026-09-05: cursor.com is blocked. The range names the Cursor 1.x line..