token-keeper

Automate OAuth token refreshing for QuickBooks, Xero, Mercury, and Plaid.

Updated May 30, 2026
One-click install
npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill token-keeper-innerscopehearing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-keeper
Source: https://github.com/InnerScopeHearing/otchealth-claude-tools/tree/main/skills/token-keeper
Command: npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill token-keeper-innerscopehearing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, https://www.googleapis.com/auth/cloud-platform, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages and refreshes OAuth tokens for various providers like QuickBooks, Xero, Mercury, and Plaid, ensuring long-term connectivity without re-authentication.

Core Features & Use Cases

  • Token Refreshing: Automatically refreshes rotating tokens to prevent expiry.
  • Token Rotation: Manages and rotates refresh tokens on a schedule.
  • Provider Support: Validates and maintains tokens for QuickBooks, Xero, Mercury, and Plaid.
  • Use Case: Ensures continuous service access for financial services without manual intervention or re-authentication.

Quick Start

Run node skills/token-keeper/keeper.mjs refresh --provider xero to refresh Xero tokens.

Frequently Asked Questions about token-keeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically refresh OAuth tokens for QuickBooks and Xero to prevent expiry?

You can automatically refresh OAuth tokens for QuickBooks and Xero by running a scheduled script that calls the provider's token endpoint. This Skill automates that refresh process, ensuring continuous service connectivity without manual re-authentication.

Why do my Plaid and Mercury API connections keep losing authentication after a few days?

Your Plaid and Mercury API connections lose authentication because rotating OAuth tokens expire periodically. This Skill solves the problem by validating and automatically refreshing tokens on a schedule to maintain long-term connectivity.

Do I need Google Cloud Platform and Azure to manage rotating OAuth tokens?

Yes, you need Google Cloud Platform for Secret Manager token storage and Azure Container Apps for scheduling the automated token rotation. These services provide the required secure storage and execution environment for continuous operation.

What's the best way to store and rotate refresh tokens for financial service APIs?

The best way to store and rotate refresh tokens for financial service APIs is using GCP Secret Manager for secure storage combined with a scheduling service like Azure Container Apps to automate the rotation process. This prevents service interruptions.

Can I use this token management approach for providers other than QuickBooks, Xero, Mercury, and Plaid?

This specific token management approach is configured to validate and maintain tokens exclusively for QuickBooks, Xero, Mercury, and Plaid. Using it for other financial service providers would require modifying the underlying token validation logic.

How do I manually trigger an OAuth token refresh for a specific provider like Xero?

You can manually trigger an OAuth token refresh for Xero by running the command `node skills/token-keeper/keeper.mjs refresh --provider xero`. This executes the refresh logic directly to re-establish connectivity.