VenueMindBrowser WebMCP
The open Studio registers native tools. The browser agent host invokes them; the published harness captures the same registrations for deterministic local execution.
javascript
// The browser host invokes tools registered by the open VenueMind page.
const result = await harness.invoke("venue.preview_revision", {
goal: "Protect the west accessible route",
idempotencyKey: "browser-example-preview-001",
correlationId: "browser-example-001",
});
if (result.isError) throw new Error(result.structuredContent.error.code);
Generic stdio client
json
{
"transport": "stdio",
"command": "node",
"args": [
"<VENUE_MIND_ROOT>/packages/mcp-server/dist/index.js"
],
"env": {
"VENUEMIND_DATA_DIR": "<WRITABLE_DATA_DIR>",
"VENUEMIND_ORGANIZATION_ID": "<ORGANIZATION_ID>"
}
}- Replace <VENUE_MIND_ROOT> with the absolute repository path.
- Replace <WRITABLE_DATA_DIR> with a dedicated writable directory.
- The host launches one local server process per stdio session.
- Standard output is protocol-only; structured diagnostics use standard error.
Codex
bash
codex mcp add venuemind --env VENUEMIND_DATA_DIR=<WRITABLE_DATA_DIR> -- node <VENUE_MIND_ROOT>/packages/mcp-server/dist/index.js
codex mcp get venuemindtoml
[mcp_servers.venuemind]
command = "node"
args = ["<VENUE_MIND_ROOT>/packages/mcp-server/dist/index.js"]
env = { VENUEMIND_DATA_DIR = "<WRITABLE_DATA_DIR>", VENUEMIND_ORGANIZATION_ID = "<ORGANIZATION_ID>" }
text
Use VenueMind to inspect Project project-summit-forward, prepare one access-first Proposal, validate it, report stable Change and Constraint IDs, export JSON, and stop for human Approval in the Studio.Claude Desktop
- 1Open Claude Desktop developer settings and edit the local MCP configuration.
- 2Merge the venuemind entry under mcpServers.
- 3Replace both path placeholders and restart Claude Desktop.
- 4Confirm VenueMind tools are available before running the supervised prompt.
json
{
"mcpServers": {
"venuemind": {
"command": "node",
"args": [
"<VENUE_MIND_ROOT>/packages/mcp-server/dist/index.js"
],
"env": {
"VENUEMIND_DATA_DIR": "<WRITABLE_DATA_DIR>",
"VENUEMIND_ORGANIZATION_ID": "<ORGANIZATION_ID>"
}
}
}
}text
Open project-summit-forward in VenueMind. Inspect accepted truth, preview a revision that protects the west accessible route, validate it, explain every non-pass result, and stop for human Approval.Cursor
- 1Create .cursor/mcp.json for Project scope or ~/.cursor/mcp.json for global scope.
- 2Copy the configuration and replace both path placeholders.
- 3Open Cursor MCP settings and confirm venuemind is enabled.
- 4Keep tool approval enabled for the supervised workflow.
json
{
"mcpServers": {
"venuemind": {
"command": "node",
"args": [
"<VENUE_MIND_ROOT>/packages/mcp-server/dist/index.js"
],
"env": {
"VENUEMIND_DATA_DIR": "<WRITABLE_DATA_DIR>",
"VENUEMIND_ORGANIZATION_ID": "<ORGANIZATION_ID>"
}
}
}
}text
Using the VenueMind MCP tools, audit the current Plan, create a separate circulation-first Proposal Branch, validate it, compare it with the active Branch, and leave the decision to a human reviewer.Retry and failure workflows
- Exact retry — reuse one idempotency key only for byte-equivalent intent; VenueMind returns the original receipt.
- Stale base — retain PLAN_VERSION_CONFLICT details, inspect current truth, detect conflicts, then rebase the Proposal.
- Validation failure — use affected stable IDs and remediation evidence; create another Proposal revision and validate again.
- Export — export only the currently evaluated Plan or Proposal and retain its version, Validation ID, and evidence fingerprints.
Raw request and response fixtures
Generation uses the production planner, error catalog, export implementation, and shared tool contracts. CI compiles and executes both code examples and contract-validates every configuration and fixture.