- Home
- MCP servers
- Get MCP Keys
Get MCP Keys
- typescript
10
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"stumason-get-mcp-keys": {
"command": "npx",
"args": [
"@masonator/get-mcp-keys",
"npx",
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "YOUR_API_KEY"
}
}
}
}You can securely run an MCP server with your own API keys by loading them from a private file and injecting them into the MCP process at runtime. This avoids storing secrets in your repository while keeping your MCP workflows simple and repeatable.
How to use
To run a FireCrawl MCP server (or any MCP server) without exposing keys in git, you load keys from a secure file and have the MCP wrapper inject them as environment variables when you start the server. You’ll configure the MCP to use the get-mcp-keys wrapper, which reads your private file, sets the necessary environment variables, and then launches your server command with those keys in place.
How to install
# Prerequisites: Node.js installed
# Install the MCP wrapper globally or per-project as needed via npm/yarn/pnpm
# Example using npm to install the wrapper locally in your project
npm init -y
npm install --save-dev @masonator/get-mcp-keys
# If you plan to run from a script, you can invoke npx as shown in the config
Additional configuration and usage notes
Create a local, private file in your home directory to store API keys. This keeps keys out of your codebase and version history.
# ~/.mcprc
FIRECRAWL_API_KEY="YOUR_FIRECRAWL_API_KEY"
BRAVE_API_KEY="YOUR_BRAVE_API_KEY"
# Add any other MCP server keys you use
Available tools
get-mcp-keys
Utility that loads API keys from a private file in your home directory, injects them into the environment, and runs your MCP server command with the keys available.