Skip to content
Trove

Official Toolkits

These official toolkits ship today. They run on Trove’s infrastructure — authenticated, always-on, and reachable from Claude on desktop, web, and mobile — and they surface inside the single Trove connection Claude already has, right next to trove_search and the other core tools. There’s nothing to install and no new client config.

All of them are open source in the toolkit catalog repo (mcp/), each a manifest.json + server.ts built on the @ontrove/mcp SDK. Most are read-only; resend is the one send-email toolkit. Every toolkit reaches only the public HTTP/JSON APIs listed in its manifest egress allowlist — never your local machine.

  • Connect them: add Trove to Claude once — see the quickstart. Tools appear namespaced as toolkit__tool (e.g. arxiv__search_papers).
  • Deploy your own: every toolkit here is a worked example you can copy. See the toolkit quickstart and Deploying.

Browse the full catalog → ontrove.sh/catalog — the complete, always-current list, grouped by category, with each toolkit’s tools, upstream API, and whether it needs a key.

Notes on a few toolkits

Section titled “Notes on a few toolkits”
  • resend is the one mutating toolkit (send_email is not read-only, so the host confirms before sending). The recipient is fixed to your RECIPIENT_EMAIL secret and CC/BCC are disallowed — it can only ever email that one address. Built for automated digests and notifications to yourself.
  • gutenberg goes beyond discovery: search_inside does legal full-text search within any public-domain book — useful for locating or verifying a quotation, catching misquotes, and term-frequency checks. get_excerpt then pages through the text from any offset.
  • hathitrust covers the public Bibliographic API only: given an ISBN/OCLC/LCCN/HathiTrust id it reports holdings and per-copy access rights (full view vs. search-only) — an exact-identifier lookup, not a fuzzy search.
  • Toolkits marked as needing a key in the catalog declare a secret and return a clear “not set” error until you set it with trove secret set. Keys are redeemed at call time from the encrypted vault via ctx.secret(...) — never bundled or logged.

Build your own

Section titled “Build your own”

Every official toolkit is a copy-pasteable starting point. To author one, see the toolkit quickstart, the manifest.json reference, and Secrets and Auth. Scaffold a fresh toolkit with trove mcp init <name> and ship it with trove mcp deploy.