Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@tinhead-mcp list the items in my inbox branch"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The published source of tinhead-mcp v0.1.5,
the local MCP server that gives an agent access to branches of your Tinhead tree.
Why this repository exists. The Tinhead app is closed source. This package is not, because it is the part that holds your key: it unwraps your account key on your own machine, talks to Tinhead's server, and enforces the branch you granted. Every claim the package makes about what leaves your machine is either true in this code or false in it.
This tree is generated — please open an issue, not a pull request
It is produced from the private Tinhead repository at each release, so it carries exactly the source that compiled into the published package rather than a re-typed copy. A pull request here cannot be merged in any lasting way — the next release would overwrite it.
That is not a brush-off, and we would rather say it plainly than let you find out after an evening on a patch. Open an issue with the fix or the finding; it gets applied upstream and ships in the next release, and you are credited in the release notes. If a claim in this code is false, that is the single most valuable thing you can tell us.
| the server itself — the grant protocol, the tools, the keychain |
| the primitives. This is the claim — key wrapping, node encryption |
| both sides of the grant protocol: what is sent, what never is |
| the thought format and its lenses, including the private-field seal |
| the wire format — observable on the network anyway |
| what the read tools emit, and the write rules |
Related MCP server: local-kms-mcp-server
The app: its interface, motion, theme, store, screens, and the sync engine. None of it can affect the claims above, and it is the product rather than the format.
npm ci --prefix packages/tinhead-mcp
npm run build --prefix packages/tinhead-mcpThat installs at the ROOT deliberately: the modules under src/ resolve their dependencies by
walking up from themselves, so they can only ever find a node_modules here. The generator
derives its file list from the package's own tsconfig.json, so a module the server imports
cannot be missing from this repository and still build.
Issues: https://github.com/Tinhead-app/tinhead-mcp/issues
Security findings are welcome in the open — this package exists to be checked, and a private disclosure of a flaw in code anyone can already read helps nobody.
Apache-2.0. See LICENSE and NOTICE at the root of this repository — they cover the
whole published tree, src/ included, not just the package directory.
This server cannot be deployed
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
MCP server for OnceAsk, the AI-native current-address layer for people and agents.
