🔐 get-mcp-keys

Created By
StuMasona year ago
A lightweight utility that securely loads API keys for Cursor MCP servers from your home directory, preventing accidental exposure of secrets in repositories. Keep your credentials safe while maintaining seamless integration with AI coding assistants.
Overview

What is get-mcp-keys?

get-mcp-keys is a lightweight utility designed to securely load API keys for Cursor MCP servers from your home directory, preventing accidental exposure of secrets in repositories.

How to use get-mcp-keys?

To use get-mcp-keys, create a .mcprc file in your home directory, add your API keys to this file, and update your MCP configuration to use the utility for loading keys.

Key features of get-mcp-keys?

  • Securely loads API keys from a hidden file in your home directory.
  • Prevents accidental commits of sensitive information to repositories.
  • Supports multiple MCP servers by injecting environment variables.

Use cases of get-mcp-keys?

  1. Safeguarding API keys while using AI coding assistants.
  2. Ensuring secure integration with various MCP servers.
  3. Simplifying the management of sensitive credentials in development environments.

FAQ from get-mcp-keys?

  • Can get-mcp-keys be used with any MCP server?

Yes! It works with any MCP server that requires environment variables.

  • Is it safe to store my API keys in the .mcprc file?

Yes, as long as you set the correct permissions to restrict access to the file.

  • How does get-mcp-keys enhance security?

It keeps your API keys out of your repositories and loads them only when needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
StuMason
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago