Skillget

authsome

mcp
Security Audit
Pass
Health Pass
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 27 GitHub stars
Code Pass
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Local auth cli for AI agents. Log in once via Oauth2/API Key. Every agent stays authenticated — headless, no SaaS, credentials never leave your machine.

README.md

authsome

PyPI version
Python 3.13+
License: MIT
PyPI downloads
Tests
codecov

               __  __
  ____ ___  __/ /_/ /_  _________  ____ ___  ___
 / __ `/ / / / __/ __ \/ ___/ __ \/ __ `__ \/ _ \
/ /_/ / /_/ / /_/ / / (__  ) /_/ / / / / / /  __/
\__,_/\__,_/\__/_/ /_/____/\____/_/ /_/ /_/\___/

Local-first credential broker and vault for AI Agents

An open-source credential broker that sits between your agents and the services they call. Instead of sharing credentials with every agent, log in once via OAuth2 or API keys. Authsome stores credentials securely and injects them via an HTTP proxy. You get one place to manage access, rotate keys, and see what every agent is doing.

Demo

https://github.com/user-attachments/assets/27f9b229-baf4-4889-be9a-378a133654dc

Why Agents need Authsome

Agents run beyond interactive sessions. They live in CI, over SSH, in cron jobs, in background workers, and in parallel pipelines. They need API access that survives without a human in the loop.

Hardcoded environment tokens leak or go stale, and building auth flow logic, token storage, refresh handling, and per-provider config into every project rebuilds the same plumbing every time.

Authsome is the local credential layer agents call at runtime.

  • No credential sprawl. One encrypted store — every provider, every agent, one place.
  • No SaaS, no privacy trade-off. Credentials never leave your machine. Eliminates credential exfiltration risks as agents never see them.
  • No browser required at runtime. Setup can use browser PKCE, device code, or a browser bridge for secure API key entry. After that, agents run headlessly.

How It Works

The CLI is the agent's interface: setup once, then inject fresh credentials whenever a tool runs.

Authsome Architecture

Authenticate once:

uvx authsome login github

Then agents get valid credentials on demand:

uvx authsome get github --field access_token --show-secret
# → ghu_...

export $(uvx authsome export github)
# → sets GITHUB_ACCESS_TOKEN in current shell

uvx authsome run python my_agent.py
# runs behind a local auth proxy that injects headers at request time
# without exposing secrets in the child process environment.
# matched automatically via provider host_url (e.g. api.openai.com)

Credentials are stored locally, encrypted at rest, and refreshed before expiry. No server. No account. No cloud.

Why Authsome

authsome Hardcoded env tokens DIY
Automatic token refresh ✅ ❌ build it
OAuth2 + API keys ✅ ❌ build it
Runtime headless use ✅ ✅ varies
Local — no SaaS dependency ✅ ✅ ✅
Built-in providers, zero config ✅ ❌ ❌
Multi-account per provider ✅ ❌ build it

Authsome gives agents one command for a valid token, without scattering long-lived secrets across every project.

Quick Start

uvx authsome login github                  # opens browser, completes PKCE flow
uvx authsome login github --flow device_code  # headless: Device Code, works over SSH and CI
uvx authsome login openai                  # secure API key entry via browser bridge
uvx authsome list                          # all connections + token status

Docs

The full documentation site lives in docs/site/

To preview locally:

cd docs/site
npm i -g mint   # requires Node.js >= 20.17.0
mint dev

Specs

License

MIT — see LICENSE.

Reviews (0)

No results found