Skip to main content
Glama
Lawrence's Personal MCP Server

Lawrence's Personal MCP Server

by MyLightIsOn

Lawrence's Personal MCP Server

A Model Context Protocol (MCP) server providing development tools for Figma integration, accessibility checking, and code generation.

Features

🎨 Figma Tools

  • figma_get_file - Fetch Figma file structure and metadata

  • figma_get_component - Get detailed component information

  • figma_extract_design_tokens - Extract colors, typography, and spacing

  • figma_search_components - Search for components by name

♿ Accessibility Tools

  • a11y_audit_component - Audit components for WCAG compliance

  • a11y_suggest_improvements - Get accessibility improvement suggestions

🔧 Code Generation Tools

  • codegen_react_component - Generate React components from Figma

  • codegen_design_tokens - Generate CSS/TypeScript design tokens

Related MCP server: Figma MCP Server

Setup

1. Install Dependencies

npm install

2. Configure Environment

Copy .env.example to .env and add your Figma access token:

cp .env.example .env

Edit .env:

FIGMA_ACCESS_TOKEN=your_figma_personal_access_token

3. Build

npm run build

Usage with Claude Desktop

Add this to your Claude Desktop configuration file:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "lawrence-mcp": {
      "command": "node",
      "args": ["/Users/lawrence/dev/mcp-server/dist/index.js"]
    }
  }
}

Then restart Claude Desktop.

Development

Run in watch mode

npm run watch

Run directly with tsx

npm run dev

Adding New Tools

  1. Create a new tool file in src/tools/

  2. Define your tools array and handler function

  3. Import and add to src/index.ts

Example:

// src/tools/my-tools.ts
export const myTools: Tool[] = [
  {
    name: 'my_tool',
    description: 'Does something cool',
    inputSchema: { /* ... */ }
  }
];

export async function handleMyTool(name: string, args: any) {
  // Implementation
}

License

MIT

Available Tools

8 tools
a11y_audit_componentB

Audit a React/HTML component for accessibility issues. Checks for WCAG compliance, ARIA attributes, semantic HTML, keyboard navigation, and color contrast.

Inputs: code (required), componentName.

a11y_suggest_improvementsC

Get specific accessibility improvement suggestions for a component, with code examples.

Inputs: code (required), issues.

codegen_design_tokensA

Generate CSS variables or TypeScript design tokens from Figma design system.

Inputs: tokens (required), format.

codegen_react_componentB

Generate a React component from Figma component data. Creates accessible, production-ready code with TypeScript support.

Inputs: componentData (required), componentName (required), includeTypes.

figma_extract_design_tokensB

Extract design tokens (colors, typography, spacing, etc.) from a Figma file. Useful for generating CSS variables or theme files.

Inputs: fileKey (required).

figma_get_componentA

Get detailed information about a specific component in a Figma file, including its properties, variants, and styling.

Inputs: nodeId (required), fileKey (required).

figma_get_fileA

Fetch a Figma file structure and metadata. Returns the full file tree including all pages, frames, and components.

Inputs: fileKey (required).

figma_search_componentsB

Search for components in a Figma file by name or type (e.g., "button", "input", "form").

Inputs: query (required), fileKey (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct step in a design-to-code workflow, and the Figma, a11y, and codegen prefixes help separate concerns. However, figma_extract_design_tokens vs codegen_design_tokens and a11y_audit_component vs a11y_suggest_improvements are close enough that an agent might occasionally pick the wrong one.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun naming pattern within their respective domains, such as figma_get_file, a11y_audit_component, and codegen_react_component. The prefixes are predictable and group related functionality clearly.

    Tool Count5/5

    Eight tools is a well-scoped count for a server covering Figma access, accessibility auditing, and code generation. Each tool serves a distinct purpose, and the set feels neither bloated nor thin.

    Completeness5/5

    The tool surface covers the full intended workflow: fetching and searching Figma data, extracting design tokens, auditing components, generating components, and producing design token output. There are no obvious dead ends or critical missing operations for the apparent design-to-code purpose.

    Related MCP Connectors

    Related MCP Servers