Janee MCP server
io.github.rsdouglas/janee·v0.8.5·30 starsSecure secrets proxy for AI agents — manages API keys so agents never see raw credentials.
30 stars115 downloads/wk
Reviews
Write oneNobody has reviewed Janee yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Janee tools (5, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
executewrite actionExecute an API request through Janee proxy
janee_execwrite actionExecute a CLI command with credentials injected via environment variables. The agent never sees the actual credential — Janee injects it and scrubs output.
list_servicesList available API capabilities managed by Janee. If you provide your agentId, only credentials you have access to will be shown.
manage_credentialView or manage access policies for agent-scoped credentials. Agents can check who has access, grant access to other agents, or revoke access.
reload_configReload Janee configuration from disk without restarting the server. Use after adding new services or capabilities.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan61 source files scanned15/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 195 days ago4/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: … "packages/*" ], "scripts": { "postinstall": "node scripts/postinstall.js", "bui…
How Janee compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 60/100
- higher than 15% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 40%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 30
- more than 92% of 28,688 servers
- Downloads a week
- 115
- more than 66% of 12,191 servers with a package
What its tools let an agent do: 3 read · 1 change · 1 run or deploy
Install Janee in Claude Code, Cursor or VS Code
Runs npx -y @true-and-useful/janee on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add janee -- npx -y @true-and-useful/janee
What the publisher says
From the Janee repository's README, as published. We do not edit it. Read it on GitHub
Janee 🔐
Secrets management for AI agents via MCP
Your AI agents need API access to be useful. But they shouldn't have your raw API keys.
Janee sits between your agents and your APIs — injecting credentials, enforcing policies, and logging everything.
✨ Features
The Problem
AI agents need API access to be useful. The current approach is to give them your keys and hope they behave.
- 🔓 Agents have full access to Stripe, Gmail, databases
- 📊 No audit trail of what was accessed or why
- 🚫 No kill switch when things go wrong
- 💉 One prompt injection away from disaster
The Solution
Janee is an MCP server that manages API secrets for AI agents:
- Store your API keys — encrypted locally in ~/.janee/
- Run janee serve — starts MCP server
- Agent requests access — via execute MCP tool
- Janee injects the real key — agent never sees it
- Everything is logged — full audit trail
Your keys stay on your machine. Agents never see them. You stay in control.
Configure Once, Use Everywhere
Set up your APIs in Janee once:
services:
stripe:
baseUrl: https://api.stripe.com
auth: { type: bearer, key: sk_live_xxx }
github:
baseUrl: https://api.github.com
auth: { type: bearer, key: ghp_xxx }
openai:
baseUrl: https://api.openai.com
auth: { type: bearer, key: sk-xxx }Now every agent that connects to Janee can use them:
- Claude Desktop — access your APIs
- Cursor — access your APIs
- OpenClaw — access your APIs
- Any MCP client — access your APIs
No more copying keys between tools. No more "which agent has which API configured?" Add a new agent? It already has access to everything. Revoke a key? Update it once in Janee.
One config. Every agent. Full audit trail.
Quick Start
Install
npm install -g @true-and-useful/janeeInitialize
janee initThis creates ~/.janee/config.yaml with example services.
Add Services
Option 1: Interactive (recommended for first-time users)
janee addJanee will guide you through adding a service:
Service name: stripe
Base URL: https://api.stripe.com
Auth type: bearer
API key: sk_live_xxx
✓ Added service "stripe"
Create a capability for this service? (Y/n): y
Capability name (default: stripe):
TTL (e.g., 1h, 30m): 1h
Auto-approve? (Y/n): y
✓ Added capability "stripe"
Done! Run 'janee serve' to start.Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Janee: common questions
- Is Janee MCP server safe?
- With care: it is graded C, so read the findings first (60/100). Read the Janee safety report
- How do I install Janee?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Janee need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Janee maintained?
- The last commit was 232 days ago (2026-03-17). The latest release is v0.8.5.
- How does Janee compare with other MCP servers?
- safety score 60/100 (higher than 15% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.