ooter":"$9:props:messages:footer"}]]}]}] 13:[["$","meta","0",{"name":"viewport","content":"width=device-width, initial-scale=1"}]] 11:[["$","meta","0",{"charSet":"utf-8"}],["$","title","1",{"children":"MCP Server Categories | MCP Servers"}],["$","meta","2",{"name":"description","content":"Explore diverse MCP Server categories including data integration, API tools, document processing, and more. Find the perfect Model Context Protocol solution for your needs."}],["$","meta","3",{"name":"keywords","content":"MCP Categories, MCP Server Types, Model Context Protocol Categories, Claude Integration Solutions, AI Tool Categories, MCP Toolkit, Data Integration Tools, API Integration Tools"}],["$","meta","4",{"name":"name=\"google-adsense-account\"","content":"ca-pub-9486334752310533"}],["$","link","5",{"rel":"canonical","href":"https://mcp.ad/categories"}]] f:null 8:E{"digest":"NEXT_REDIRECT;replace;/;307;"} 1b:I[40533,["7374","static/chunks/7374-3d45d9728b4c7a58.js","3612","static/chunks/3612-66a9492c59acfe17.js","6585","static/chunks/6585-c1bc043b2493ff06.js","909","static/chunks/909-63c127a841bfbdd9.js","9665","static/chunks/9665-b274c6a6f1fd7aae.js","6269","static/chunks/6269-acf7eb4d801487db.js","9411","static/chunks/app/%5Blocale%5D/(default)/categories/page-ab399fb789661555.js"],"default"] 1c:Tba9,

🔐 get-mcp-keys

Stop accidentally committing API keys to your repos!

The Problem

When using Cursor AI (and other AI coding assistants) with MCP servers, you need API keys in your ./cursor/mcp.json file:

{
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "sk_live_ohno-this-should-NOT-be-in-git" // 💀
      }
    }
  }
}

This is a security nightmare waiting to happen. One accidental commit and your keys are exposed in your Git history.

💯 The Solution

get-mcp-keys loads your API keys from a secure file in your home directory, keeping them out of your repositories entirely.

⚡ Quick Start

1. Create a `.mcprc` file in your home directory

touch ~/.mcprc
chmod 600 ~/.mcprc  # Make it readable only by you

3. Add your API keys to the file

# ~/.mcprc
FIRECRAWL_API_KEY="your_actual_api_key_here"
BRAVE_API_KEY="another_secret_key_here"
# Add any other MCP server keys you use

4. Update your MCP configuration to use get-mcp-keys

{
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "@masonator/get-mcp-keys", // 🔐
        "npx",
        "-y",
        "firecrawl-mcp"
      ]
    }
  }
}

That's it! The get-mcp-keys utility will:

Load your API keys from ~/.mcprc
Inject them as environment variables
Run your MCP server command with the keys available

🛡️ Security

Your API keys stay in your home directory
Keys are never committed to repositories
Keys are loaded only when needed
Debug output shows only first/last few characters of keys

🧰 Supported MCP Servers

Works with any MCP server that needs environment variables, including:

FireCrawl
Brave Search
Supabase
And any other MCP servers you configure!

🔍 How It Works

get-mcp-keys reads your .mcprc file, adds those environment variables to the current environment, and then executes whatever command you specify after it in the args list. It's s

Categories

Current Category: credential-

get-mcp-keys