Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @millwork/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add millwork-solver-mcp -- npx -y @millwork/solver-mcp@0.2.17รันในเทอร์มินัล
{ "mcpServers": { "millwork-solver-mcp": { "command": "npx", "args": [ "-y", "@millwork/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
@millwork/solver-mcp is the Millwork Solver execution MCP server. It gives an
approved assistant 28 tenant-authenticated solver_* tools over stdio. Some
tools read state. Others connect model sources, submit work, cancel a run, or
decide a proposal, so the server is write-capable.
Millwork Solver execution MCP server -- the solver_* tools over stdio.
Requires Node 20 or Node 22.
npm install @millwork/solver-mcp
solver-mcp --help
npm install @millwork/solver-mcp resolves the latest dist-tag. Pin an exact
version for reproducible application builds.
Or run it directly:
npx --yes @millwork/solver-mcp --help
Discover solver_list_verifiers first. An empty page without next_cursor
returns a typed scaffold_output_check next action. Install
@millwork/[email protected] or later to scaffold and test an output check locally,
then deploy its HTTPS endpoint.
The build-and-connect guide
starts with Recipe 0 and shows the local test, deployment, and recovery path.
Register a credential-less endpoint with solver_connect_verifier and retest with
solver_test_verifier:
solver_connect_verifier({ access: "public", endpoint: "<https-url>",
name: "<name>", version: "<version>", idempotency_key: "<caller-owned-id>" })
For a protected endpoint, connect with access: "managed", then use
solver_start_verifier_connection to obtain the private browser handoff.
Give its continue_url only to the intended person, and use
solver_inspect_verifier_connection and
solver_continue_verifier_connection to resume the same operation after
private key entry. Never put the endpoint key in chat or a tool argument.
Disconnecting requires separate host confirmation and
confirm_disconnect: true; it stops Millwork's use of the key but does not
revoke the key at the endpoint. Pass the returned verifier_id into
solver_submit only after choosing the check. Connecting a check is not
approval to run a task.
Point the MCP client at the solver-mcp binary with no arguments. Supply
these environment variables through the client's secret-aware environment
configuration. Do not paste their values into a prompt, log, screenshot, or
support report.
The transport contract is exact:
command: solver-mcp
arguments: none
transport: stdio
stdout: MCP JSON-RPC only
stderr: diagnostics
Any MCP-capable assistant can use the same tool surface. Start with a read-only request:
Use solver_list_sources and solver_list_source_connections to show what this
organization can see. Do not call a tool that requires human confirmation.
Return tool names and safe counts only. Do not print credentials or customer
content.
For a write-capable request, make the stop explicit:
Prepare a solver_submit call but do not run it yet. Show the exact budget,
verifier, data classes, and caller-owned idempotency key. Wait for my explicit
confirmation before one call. If the outcome is uncertain, inspect status with
a read tool; do not submit again under a new key unless I confirm that new
intent.
Human confirmation is a client-side stop. The tenant API key still carries the server-side permissions assigned to it. Confirmation does not turn a tenant-wide machine key into a narrower credential.
A live solver_submit also requires the supported host-isolation profile. The
host, not the prompt or launch environment, owns the fixed attestation,
read-only admission ledger, and exact one-run approval channel. The first call
can return host_approval_required; after the host writes the returned approval
document to the named host-owned file, retry the exact same tool arguments and
idempotency key. Echo submissions remain free and do not require this approval.
The server registers exactly 28 solver_* tools; tools/list over stdio is
the authoritative surface, and every tool description states what the tool
maps to and whether it writes. No tool ever accepts or returns raw credential
material. Provider and protected-verifier setup use private browser handoffs;
the tools return short-lived continuation URLs and opaque operation references,
never raw keys.
The 28 tools divide into:
solver_submit and
solver_disconnect_verifier_connection, which may retry
only with the same caller-owned, non-empty idempotency key and the same
request bytes; andFor those eight tools, a network or 5xx failure is a failure, not an automatic
retry. The write might have applied before the response was lost. Inspect
state with a safe read or your existing dashboard recovery path, then ask for
explicit human intent before another write-capable tool call. Raising
SOLVERAPI_MAX_RETRIES does not make those writes replay-safe.
Backend failures use RFC 7807. The MCP error result keeps the parsed Problem
in structuredContent.problem; transport failures use network_error.
Report problems on this repository's
issue tracker. Useful
evidence includes the tool name, retry boundary, attempt count, package and
Node versions, and the Problem type, title, status, instance, and
retry_after_s fields. Never include credentials or customer content: omit
your tenant API key, your provider key/account details, authorization
headers, task content, and tenant or resource identifiers.
This package is tenant-authenticated and write-capable. It is not a documentation-retrieval service and receives no tenant key from any other package. The Millwork documentation assistant is a separate, retrieval-only service with no execution authority.
Millwork Solver execution MCP server -- the solver_* tools over stdio.
{ "mcpServers": { "millwork-solver-mcp": { "command": "npx", "args": [ "-y", "@millwork/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@millwork/solver ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-10 Millwork Solver execution MCP server -- the solver_* tools over stdio.