@arpproject/vibearp-mcp 1.3.0 → 1.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -150,6 +150,8 @@ engedélyezett hozzáféréssel rendelkezik.
150
150
  This package is maintained by SZTAKI, Department of Distributed Systems
151
151
  (<https://dsd.sztaki.hu>).
152
152
 
153
+ Contact: [rockit@dsd.sztaki.hu](mailto:rockit@dsd.sztaki.hu).
154
+
153
155
  Individual contributors are listed in `package.json`.
154
156
 
155
157
  ## License
package/lib/server.js CHANGED
@@ -52752,6 +52752,11 @@ You are editing an RO-Crate as a data steward.
52752
52752
 
52753
52753
  ## Mandatory Startup
52754
52754
 
52755
+ The configured RO-Crate MCP server's call names are "RO-Crate MCP" and
52756
+ "VibeARP". When a user says either name, use the configured server's tools even
52757
+ if the harness displays a different server label (commonly \`rocrate\` or
52758
+ \`rocrate-mcp-server\`).
52759
+
52755
52760
  Before advising on or editing RO-Crate metadata, read this top-level workflow doc
52756
52761
  with \`read_agent_workflow_doc\`. Then read the step-specific workflow doc before
52757
52762
  each step.
@@ -69242,8 +69247,9 @@ async function startServerWithTransports(options) {
69242
69247
  const mcpServer = new McpServer(
69243
69248
  {
69244
69249
  name: "rocrate-mcp-server",
69250
+ title: "RO-Crate MCP / VibeARP",
69245
69251
  version: getBuildInfo().version,
69246
- description: "RO-Crate metadata tools. The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file."
69252
+ description: "RO-Crate metadata tools, also known as RO-Crate MCP or VibeARP. These names refer to this same server. The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file."
69247
69253
  },
69248
69254
  {
69249
69255
  capabilities: {
@@ -69983,6 +69989,7 @@ function getDashboardUrl() {
69983
69989
  }
69984
69990
  function getMcpServerInstructions() {
69985
69991
  return `RO-CRATE TOOL ROUTING
69992
+ This MCP server is known by the call names "RO-Crate MCP" and "VibeARP". When a user mentions either name, use this configured RO-Crate MCP server's tools, regardless of the server label shown by the harness (commonly "rocrate" or "rocrate-mcp-server"). Do not search for or select a different MCP server based on these names.
69986
69993
  The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file.
69987
69994
  For a direct request to open, view, show, inspect, or launch a dataset in AROMA\u2014including the exact request "open dataset in AROMA"\u2014call open_aroma_for_local_file immediately as the first tool. Treat "dataset" as the RO-Crate in the current working directory and pass "ro-crate-metadata.json"; otherwise pass the dataset's ro-crate-metadata.json path.
69988
69995
  Before RO-Crate editing/advice, call read_agent_workflow_doc with name "rocrate_workflow.md" and follow it.