コンテンツにスキップ

MCP for AI clients

このコンテンツはまだ日本語訳がありません。

HarperHarbor exposes a Model Context Protocol server backed by the same services as Open API v1. An AI client uses OAuth to act on behalf of the signed-in user. Tools cover card authoring, usage queries and lane status, subject to the user’s permissions.

The server speaks streamable HTTP and uses OAuth 2.1 with dynamic client registration, so most clients need only the URL.

Terminal window
claude mcp add --transport http harperharbor https://api.harperharbor.com/mcp

The first tool call opens the browser for sign-in and consent.

Group Examples Notes
Cards create a private card, patch profile / document / welcome, validate, submit for review same ownership rules and quotas as the HTTP authoring endpoints
Worldbooks create, add and update entries, bind to a card keyword fields are arrays
Themes and previews render a preview, validate a theme output is a preview page the client can open
Conversation start, send, read status for testing a card the way a player would
Account read usage and balance, read lane status read-only

The exact tool list is discoverable from the server (tools/list) and is versioned with the platform, not with this page.

  • Never invent identifiers. Card, worldbook and conversation ids come from tool results.
  • Do not paste secrets into tool arguments. The server already knows who you are from the token.
  • Read before write. Fetch the current document before patching; patches merge with the existing document. Send only the fields you intend to change.
  • Costs apply. Conversation tools debit the signed-in user’s wallet like any other call.

If your client supports skills (Claude Code, Codex), install the HarperHarbor skills so the model knows the workflow, the field limits and the review rules before it edits a card. See Skills.