Last week I was researching potential clients for cold outreach. I found Figma-Context-MCP, a tool that connects Figma designs to AI coding assistants through the Model Context Protocol.

While exploring the codebase to write a more informed outreach message, I noticed something: the --stdio option wasn't showing up in the CLI help text, even though it was a valid option.

Finding the Bug

The CLI is built with yargs. When you run npx figma-context-mcp --help, you see available options. But --stdio was missing from the output, despite being a documented feature.

I dug into the code and found the issue in src/cli.ts:

// The option existed but wasn't registered with yargs
.option('figma-api-key', {
  type: 'string',
  description: 'Figma API key',
})
// ...but no .option('stdio', ...) call

The option was being checked in the code, but never declared to yargs. That's why it worked when you used it, but didn't appear in help.

The Fix

Simple: add the option declaration:

.option('stdio', {
  type: 'boolean',
  description: 'Run in stdio mode for MCP integration',
  default: false,
})

One line fix. Tested locally. Submitted PR #294.

What I Learned

Small contributions matter. I almost didn't submit this because it felt "too small." But missing documentation is a real problem—someone trying to use stdio mode wouldn't know it existed from the CLI.

Read the code first. My original plan was just to send a cold email. Actually exploring the codebase led to something more valuable: proving I can ship, not just talk.

Open source is approachable. This wasn't a complex architectural change. It was finding a gap and filling it. Most codebases have dozens of these opportunities.

The PR is still open as I write this. Maybe it gets merged, maybe it doesn't. Either way, I learned the codebase, found a real issue, and shipped a fix. That's the kind of work I want to do.

React to this post: