What does this MCP actually do?

It converts complex legal rights and access data into plain-language statements that people can actually understand.

Can I use this with Claude or Cursor?

Yes, you can connect this MCP to any MCP-compatible client like Claude, Cursor, or Windsurf.

How does it handle conflicting permissions?

The validate_clause_library capability checks your library to ensure it is free of internal conflicts.

Does it help with web publishing?

Yes, the get_publication_checklist capability provides specific steps for moving a draft to web, print, or digital use.

How does it find errors in my statements?

The analyze_statement_ambiguity capability looks for logical gaps between your input facts and the final text.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Collection Rights Statement Builder to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn messy rights data into clear, actionable access statements.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Collection Rights Statement Builder.

01
Analyze statement ambiguity
This capability performs a deep dive into the relationship between your raw facts and the final statement to find logical gaps.
02
Generate rights statement
Use this to transform raw input data into a structured document covering rights and access.
03
Get publication checklist
This capability provides a standardized list of steps to move a draft from its initial state to a live publication.
04
Validate clause library
This capability checks your library of approved clauses to ensure it is complete and free of internal conflicts.

Real work

What teams actually run

Digital Archive Access

Create clear permission statements for online collections based on specific rights-holder data.

Compliance Auditing

Run the clause library validation to ensure no conflicting permissions exist in your system.

Metadata Preparation

Use the publication checklist to ensure web metadata statements meet all technical requirements.

Rights Documentation

Turn raw restriction data into structured documents for users.

One connector, every AI

Collection Rights Statement Builder works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Collection Rights Statement Builder to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Collection Rights Statement Builder, so you can see the experience inside your AI.

It does not authenticate your account with Collection Rights Statement Builder. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Collection Rights Statement Builder Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_J2GcGRRC8TbRPCmnVsnL8egyOIhayGOxq0BnhdtR/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Collection Rights Statement Builder capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "collection-rights-statement-builder-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_J2GcGRRC8TbRPCmnVsnL8egyOIhayGOxq0BnhdtR/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Collection Rights Statement Builder in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Collection Rights Statement Builder owners hand off.

This MCP is designed for professionals managing digital collections and legal permissions.

01
Digital Archivists
They hand off raw metadata and permission sets to generate public-facing statements.
02
Rights Managers
They use the capability to validate clause libraries and ensure compliance.
03
Library Metadata Specialists
They use the publication checklists to prepare statements for web deployment.

FAQ

Questions Collection Rights Statement Builder owners ask.

01
What does this MCP actually do?
It converts complex legal rights and access data into plain-language statements that people can actually understand.
02
Can I use this with Claude or Cursor?
Yes, you can connect this MCP to any MCP-compatible client like Claude, Cursor, or Windsurf.
03
How does it handle conflicting permissions?
The validate_clause_library capability checks your library to ensure it is free of internal conflicts.
04
Does it help with web publishing?
Yes, the get_publication_checklist capability provides specific steps for moving a draft to web, print, or digital use.
05
How does it find errors in my statements?
The analyze_statement_ambiguity capability looks for logical gaps between your input facts and the final text.

Explore

More in Legal

Connect Collection Rights Statement Builder to Claude, Cursor, ChatGPT & more

Connect Collection Rights Statement Builder to your AI

Your AI does the work. We keep it safe and sound.