What does this MCP actually do?

It acts as a decision engine that evaluates reproduction requests against your business rules and rights metadata.

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 restricted items?

The engine checks the item's rights status and can flag requests that require explicit external permission.

Does it help with the actual delivery of files?

It calculates the logistical steps needed for fulfillment, such as sending an invoice or a download link.

Do I need to host the MCP myself?

No, Vinkius hosts and manages the MCP for you, so it is ready to use immediately after connection.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Collection Reproduction Request Engine 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. Automate rights evaluation and reproduction request decisions.

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 Reproduction Request Engine.

01
Calculate fulfillment requirements
This capability outlines the logistical steps needed to complete a request once it is approved or made conditional.
02
Check rights compatibility
This capability validates if a specific intended use aligns with the rights status of an item.
03
Evaluate reproduction request
This is the primary decision engine used to determine the final outcome of a reproduction request.
04
Validate request completeness
This capability checks that all necessary information is present before a decision is made.

Real work

What teams actually run

Commercial Use Approval

An institution uses the MCP to quickly approve public domain requests for commercial publishers.

Restricted Access Control

The AI flags requests for restricted items that require additional permissions.

Fulfillment Automation

A user gets a list of required actions, like invoicing, immediately after a request is approved.

Data Validation

The agent catches incomplete requests before they reach a human reviewer.

One connector, every AI

Reproduction Request Engine 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 Reproduction Request Engine 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 Reproduction Request Engine, so you can see the experience inside your AI.

It does not authenticate your account with Reproduction Request Engine. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Reproduction Request Engine Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_nf5hbFCQncvWZZwVaya6KqTEgIT6zwXyFsPEkXQR/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 — Reproduction Request Engine capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "collection-reproduction-request-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_nf5hbFCQncvWZZwVaya6KqTEgIT6zwXyFsPEkXQR/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 Reproduction Request Engine in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Reproduction Request Engine owners hand off.

This MCP is built for institutions managing large digital or physical collections that receive frequent reproduction inquiries.

01
Rights Managers
They hand off complex rule-checking and decision-making tasks to the AI.
02
Archivists
They use the capability to verify if metadata supports a specific user request.
03
Collection Administrators
They rely on the capability to automate the workflow of approving and fulfilling requests.

FAQ

Questions Reproduction Request Engine owners ask.

01
What does this MCP actually do?
It acts as a decision engine that evaluates reproduction requests against your business rules and rights metadata.
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 restricted items?
The engine checks the item's rights status and can flag requests that require explicit external permission.
04
Does it help with the actual delivery of files?
It calculates the logistical steps needed for fulfillment, such as sending an invoice or a download link.
05
Do I need to host the MCP myself?
No, Vinkius hosts and manages the MCP for you, so it is ready to use immediately after connection.

Explore

More in Rights Management

Connect Reproduction Request Engine to Claude, Cursor, ChatGPT & more

Connect Collection Reproduction Request Engine to your AI

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