# Ownhand [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/jordan-gibbs/ownhand  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ownhand

## Description
Write in the user's own voice, fitted to the occasion. Learns from the text they actually send.

## Tools
Capabilities this server exposes over MCP:

- **write** — Rewrites a draft so it reads like you wrote it, fitted to the occasion. Keeps every fact. Returns the text and a `request_id`.
- **send_feedback** — Reports what you did with a draft (`approved`, `edited` with the exact sent text, or `rejected`) so your Hand learns.
- **get_hand** — Lists your Hands, or shows what one has learned: style card, rules, sample counts.
- **create_hand** — Creates a Hand from texts you wrote yourself.
- **update_hand** — Adds samples, sets how you describe your writing, pins, rejects or activates a learned rule, adds, edits or removes custom occasions, adds, edits or removes people, or rolls back to an earlier version.
- **delete_hand** — Deletes a Hand and its history, permanently.
- **get_account** — Shows your account, credit balance, recent charges and usage.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Ownhand MCP server does

Ownhand MCP server gives an agent tools for drafting text in a user's learned writing style while adapting the result to a specific occasion. Supported occasions include chat messages, internal and external email, cold and warm proposals, PR descriptions, review comments, documentation, and status updates. The `write` tool preserves the facts in a draft and returns rewritten text with a `request_id`.

The service is intended for text sent under the user's name. It is not described as a tool for generating code, notes, or summaries. Agents can provide recipient details, including a name, email address, and notes, so the draft can account for the person receiving it.

## How it works

A Hand is the user's voice profile. It can be created from text the user wrote, such as pasted email, Slack messages, or PR descriptions. The README suggests starting with roughly five to ten pasted samples or about twenty messages retrieved by an agent after the user gives permission. Fewer samples are supported, but the writing may remain generic until the Hand has more examples or feedback.

The normal workflow keeps the user in control. The agent calls `write`, presents the draft, and waits for the user to approve, edit, or reject it. It then calls `send_feedback`; an edit must include the exact text that was sent. Ownhand uses this feedback to propose learning changes. Proposed rules require confirmation before becoming active, and users can pin or reject rules. Learning affects only the user's own Hand.

## Setup and configuration

Ownhand MCP server is hosted at `https://ownhand.dev/mcp` as a streamable HTTP service. Connection uses OAuth 2.1 with dynamic client registration: add the endpoint in a supported client, sign in through the browser, choose a Hand, and allow access. The documented setup does not require copying an API key for normal browser-based use.

After connecting, ask the agent to set up the Hand. The agent can offer to retrieve the user's messages when it has a suitable email or Slack tool, or the user can paste samples directly. The service starts new accounts with one dollar of credit and then charges for token usage without a subscription or monthly fee.

## Tools and capabilities

- `write` rewrites a draft for the selected occasion and returns a request identifier.
- `send_feedback` records approval, rejection, or the exact edited text that was sent.
- `get_hand` lists Hands or shows a Hand's style card, rules, and sample counts.
- `create_hand` builds a Hand from user-provided writing samples.
- `update_hand` manages samples, writing descriptions, learned rules, custom occasions, people, and earlier versions.
- `delete_hand` permanently removes a Hand and its history.
- `get_account` reports account details, credit balance, charges, and usage.

## Limitations and notes

Ownhand MCP server stores account information, Hands, requests, and submitted feedback. Thread messages passed as context are not stored after the individual request, while tool-call metadata is retained for up to 90 days. The provider processing the writing may use drafts, samples, context, and feedback to improve its models, so the service should not be used for text that must remain outside that provider's processing.

Users can delete a Hand, revoke a key, or disconnect an application. Custom occasions and recipient records are managed through `update_hand`, and the agent can use the `ownhand://guide` and `ownhand://occasions` resources for guidance.

_Full upstream README: https://allmcps.com/mcp/ownhand/readme_