Local Agent-Q server package that exposes MCP tools, a local HTTP API/Admin Page, and the `agent-q-sui-signer` executable for using an Agent-Q hardware device as a Sui external signer. It relays connection, capability, account, policy, and signing requests to device firmware, which remains the signing and policy authority.
From the registry: Local MCP server for requesting signatures from Agent-Q Firmware.
Please install the `agent-q` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js and npm** — Install Node.js and npm so you can run the package with npx.
- **Agent-Q hardware device** — An Agent-Q device is required. The server requests a connection when it starts, and the connection must be approved on the device firmware.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@stelis/agent-q@latest","serve","--request-connect"]
Note: The README's MCP configuration uses stdio via npx. No environment variables are documented for MCP setup. The package also exposes a local HTTP API and Admin Page, but the README does not provide MCP-over-HTTP client configuration, so the canonical MCP install path is stdio.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Dead code, security, secrets detection and code quality for Python, TypeScript, Go.