The Big Orange Edition

The Story

Grok asked for MCP on a URL. We built it.

That was November 2025. grok-faf-mcp shipped as the first MCP server specifically built for Grok/xAI, deployed on Vercel with URL-based access. No installation required. Point your integration at the endpoint, get instant access to 21 MCP tools using the IANA-registered .faf format.

Four months later, it was time for a refresh. Not a rewrite. A refresh.

What Changed

21 Tools, Not 17

The landing page and README were showing 17 tools. The server actually had 21. Fixed everywhere: landing page stats, OG meta tags, README, deploy section. What you see is what you get.

The Fresh Landing Page

Fresh Inter typography, stats bar (21 / 0 config / 19ms), endpoint cards, Three Ways to Deploy grid. The Big Orange still pulses. The dedication stays. The squeeze stays.

Dependencies Refreshed

• MCP SDK 1.26.0 → 1.27.1
• faf-cli 4.5.0 → 5.0.1
• CI actions updated (setup-node v6, artifacts v7/v8)

Tarball Trimmed

874 KB → 306 KB. 65% smaller. Removed a 438KB thumbnail (GitHub-only, for OG tags), five discord-sync scripts (dev tooling), and oversized icons. Nothing users need was removed.

Three Ways to Deploy

1. Hosted (Instant)

Point your MCP client to this endpoint. All 21 tools available instantly.

2. Self-Deploy (Your Own Vercel)

Click the Deploy with Vercel button in the README. Zero config — your own instance in 30 seconds.

3. Local (npx)

The Landing Page

Visit grok-faf-mcp.vercel.app and see for yourself. The Big Orange pulses. The endpoints glow. The footer says what everyone's thinking:

Try It

Or add to your MCP config:

{
  "mcpServers": {
    "grok-faf": {
      "command": "npx",
      "args": ["-y", "grok-faf-mcp"]
    }
  }
}

The Numbers

• v1.1.1 - Released March 4, 2026
• 57/57 - Tests passing
• 21 - MCP tools (+ Grok-exclusive)
• 306 KB - npm tarball (was 874 KB)
• 19ms - Average execution
• 950+ - npm downloads