Skip to content

Repository files navigation

Signetry for Cursor

Copyright (c) 2026 Binay Dalai. All rights reserved. This repository is strictly for viewing and contributing to the original project. You may not use, copy, modify, distribute, or commercialize this code for your own personal or commercial projects without explicit written permission. Only the original author retains the right to use and monetize this project.

Two ways to govern coding-agent changes in Cursor with signetry-core.

Prerequisite

pip install "signetry-core @ git+https://github.com/Signetry/core@v0.6.0"

Add a .signetry/admission.yaml to your repo declaring allowed/forbidden paths, diff budget, and required checks (a conservative default applies without one).

1. MCP server (recommended)

Cursor speaks MCP. Add Signetry's server so the agent can run admission / verify / provenance itself. Copy mcp.json to .cursor/mcp.json in your project (or merge into your existing one):

{
  "mcpServers": {
    "signetry": {
      "command": "python",
      "args": ["-m", "signetry_core.mcp_server"],
      "env": { "SIGNETRY_MCP_ROOTS": "${workspaceFolder}" }
    }
  }
}

Then the agent can call signetry_admit, signetry_verify, and signetry_provenance. SIGNETRY_MCP_ROOTS scopes the server to your workspace so it can't be pointed at arbitrary host paths.

2. Project rule (defense in depth)

Drop signetry.mdc into .cursor/rules/ so the agent is told to stay within the contract and to run signetry guard before writing forbidden paths. This is advisory (the model may still err) — the durable guard is running Signetry in CI on the PR via the Signetry Admission GitHub Action.

Note: Cursor has no deterministic pre-write hook like Claude Code, so in Cursor the strong enforcement is the CI check on the PR; the MCP tools + rule give the agent an in-editor way to self-check first.


Part of the Signetry platform. Governance logic lives in signetry-core; this integration never reimplements policy and never auto-merges.

License

Copyright (c) 2026 Binay Dalai. All rights reserved. This code is not open source. You may not use, copy, modify, distribute, or commercialize it for your own personal or commercial purposes without explicit written permission from the author, who alone retains the right to use and monetize this project. See CONTRIBUTING.md.

About

Cursor integration for Umbra: MCP server + project rule to govern coding-agent changes. Split from umbra-plugins.

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors