Let your agents work safely with your documents

How it works

Your agent provides the model capability for normal document tools. Koinote handles authorization, document tools, revision conflicts, and audit records; GEO summary generation can call the built-in model or your configured BYOK channel. After you bind Feishu, a write token can also call sync_document_to_feishu to create or update a Feishu document.

Before you start

• Activate Lifetime — MCP is a Lifetime benefit.
• Create a personal token — Choose read-only, read/write, or publish-only access and a fixed or permanent lifetime in Dashboard.
• Configure your client — Use the matching setup below for https://koinote.app/mcp.

Connect each agent

A token is an account credential. Keep it in an environment variable or secure client storage, and never commit it to a repository.

• Register the remote MCP in ~/.codex/config.toml, read the token from an environment variable, then restart Codex.
• Use the Claude Code CLI to add an HTTP MCP server with its Bearer authorization header.
• Declare a remote MCP in a global or project opencode.json and inject the header from an environment variable.
• Register the Streamable HTTP server with OpenClaw CLI, then run doctor to probe its tools.
• WorkBuddy and other clients only need Streamable HTTP support and a configurable Authorization header.

Using Koinote from an agent

No special syntax is required. Say that you want to work with Koinote and the agent will select the MCP tools. After binding Feishu, ask it to call sync_document_to_feishu to perform a one-way Koinote-to-Feishu sync; Koinote remains the source of truth. Name the document and desired outcome explicitly for replacement or trash operations. With a publish-only token, you can ask the agent to push a named document to the bound WeChat Official Account draft box or generate and maintain its GEO summary; explicitly request GEO when pushing.

Try these prompts after setup

• List the five documents I edited most recently in Koinote.
• Write an article about remote work and save it to Koinote.
• Find ‘Product launch checklist’ and append a post-launch review section.
• Move ‘Old draft’ to trash, but do not permanently delete it.

Permissions and deletion boundaries

• Read-only tokens can list, search, and read documents and history, but cannot change content.
• Read/write tokens can create, append, update, restore versions, and move documents into or out of trash; after Feishu is bound, they can also call sync_document_to_feishu to create or update a Feishu document.
• Publish-only tokens can read documents and call push_wechat_draft to create an Official Account draft, but cannot modify or delete Koinote documents.
• Read/write and publish-only tokens can generate or maintain a WeChat GEO summary; built-in generation consumes credits, and drafts omit it unless requested.
• Agents cannot permanently delete documents; that requires confirmation in the web trash page.
• Tokens can be revoked individually and stop working when expired or membership becomes inactive.