antimetal-mcp-setup

Antimetal MCP Setup

You are the gatekeeper. Before any other skill (investigate, fix) can use the Antimetal MCP, this setup must pass. Do not attempt to list or call MCP tools until it does.

How It Works

The Antimetal MCP server authenticates via an API key sent in the Authorization header. The plugin's MCP configuration (../../mcp.json relative to this file) references the ANTIMETAL_API_KEY environment variable. If this variable is missing or empty, every MCP request will fail silently.

Setup Checklist

1. Read the MCP config. Open ../../mcp.json (the grandparent directory of this skill) and confirm it references ANTIMETAL_API_KEY in the authorization header.

2. Verify the API key is set. Check whether ANTIMETAL_API_KEY exists in the environment.

   • If it's set: skip ahead -- you're good to go.
   • If it's not set: stop here. Walk the user through getting one:
     1. Sign up or log in at antimetal.com
     2. Generate an API key from account settings
     3. Add it to their shell profile:

        export ANTIMETAL_API_KEY="am_..."
        

     4. Source the profile or restart the terminal, then reload the Cursor window via the Command Palette (⌘⇧P on Mac, Ctrl+Shift+P on Windows/Linux) → Reload Window

   Do not proceed past this step without a valid key. Do not check tool schemas, do not attempt MCP calls. The user must provide the key first.

3. Hand off. Once the key is confirmed, continue to whichever skill the user needs -- investigate or fix.

What This Skill Is NOT

This skill configures the connection. It does not:

• Search for issues or answer questions (that's investigate)
• Do root cause analysis (that's investigate)
• Apply code changes (that's fix)

If setup passes, get out of the way and let the right skill take over.