Hinoki Concierge logo
Agent/MCP distribution

Hinoki Concierge MCP for Codex, Claude, and OpenClaw

Codex、Claude、OpenClaw などの agent client から、Hinoki Concierge workspace を安全な local stdio MCP 経由で操作するための install guide と owner credential 発行導線です。

Open GitHub install docsActivate paid workspaceOwner console

Public install path

Local MCP, owner-issued access, backend-controlled tools

local stdio
  • Hinoki Concierge MCP is a local stdio MCP server, not a hosted autonomous agent.
  • A paid Hinoki workspace unlocks MCP entitlement, then the owner issues one credential per client.
  • Codex, Claude, and OpenClaw launch the same local `hinoki-concierge-mcp` command with partner-specific environment variables.

Install

Install from GitHub source or a pinned release

Python 3.10+

The package lives in the public GitHub repository. For production installs, prefer a pinned tag, commit, or release artifact once published.

git clone https://github.com/Oranquelui/Hinoki_Concierge.git
cd Hinoki_Concierge/hinoki_concierge_mcp
python3 -m pip install .

Activation flow

Payment first, credential second, local registration third

Step

1. Activate a paid workspace

MCP is included in active paid Hinoki plans. Downloading the package alone does not connect to a workspace.

Step

2. Issue an owner credential

The workspace owner creates a tenant-scoped token for Codex, Claude, or OpenClaw from the owner console below.

Step

3. Install and register locally

Install the package on the same machine that runs the agent client, then register the stdio command in that client's MCP settings.

Client registration

Use one credential per agent client

Codex / Claude / OpenClaw
Client

Codex

Use a Codex-scoped token and register `hinoki-concierge-mcp` as a local MCP server for operator workflows.

Client

Claude

Use a Claude-scoped token with the same local command and environment block in Claude's MCP configuration.

Client

OpenClaw

Use an OpenClaw-scoped token for partner or agency workflows that operate the Hinoki workspace from OpenClaw.

export HINOKI_MCP_API_BASE=https://api.hinokiconcierge.com
export HINOKI_MCP_TOKEN=<paste owner-issued token>
export HINOKI_MCP_PARTNER=codex
hinoki-concierge-mcp

Security boundary

MCP does not bypass Hinoki authorization

Hinoki Concierge MCP is intentionally thin. It forwards approved tool calls to Hinoki backend over HTTPS, where tenant entitlement, credential status, partner allowlist, Desk handoff, readiness, and audit attribution are enforced.

  • Tokens are issued by the workspace owner and shown only once.
  • Use a separate token for each client and revoke tokens that move machines.
  • Voice and realtime media remain outside the MCP surface in the first release.

FAQ

Common MCP install questions

Is Hinoki Concierge MCP a hosted remote MCP server?

No. The first release is a local stdio MCP package installed on the machine that runs Codex, Claude, or OpenClaw.

Can anyone install the package and access a workspace?

No. The package also needs an active paid workspace and an owner-issued tenant-scoped MCP credential.

Does MCP bypass the Hinoki backend?

No. The local MCP server is a thin adapter over Hinoki backend APIs. Authorization, audit logs, readiness, Desk, and Ledger behavior remain in the backend.

MCP

Hinoki Concierge MCP

Issue tenant-scoped MCP credentials for approved agent clients, then hand the operator the exact install and launch steps for Hinoki Concierge MCP.

TenantNot attached
RoleNone
AccessSetup ChatAI PreviewDeskLedgerMCPContact