Skip to main content
MCP servers · mcp · 16 picks

MCP servers for developer workflows

Useful MCP servers for files, browsers, APIs, repositories, databases, and developer automation.

Curated by @heyclaude-editors Updated 2026-07-18

Useful MCP servers for files, browsers, APIs, repositories, databases, and developer automation.

Compared at a glance

The top 5 picks side by side on trust, install, platform support, and disclosed notes — full rationale for each below.

Field

Read and write records, manage bases and tables in Airtable directly from Claude

Open dossier

Access designs, export assets, and interact with Figma files through Claude

Open dossier

Official MCP server providing read-only access to PostgreSQL databases with schema inspection and query capabilities

Open dossier

Official Redis MCP server providing natural language interface for Redis data management and operations

Open dossier

Configure and manage Stytch authentication services and workspace settings

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceNo submission linkNo submission linkNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAirtable logoAirtableFigma logoFigmaAnthropic logoAnthropicRedis logoRedisStytch logoStytch
Categorymcpmcpmcpmcpmcp
SourceFirst-partyFirst-partyFirst-partyFirst-partyFirst-party
AuthordomdomeggFigmaAnthropicRedisStytch
Added2025-09-182025-09-182025-09-162025-09-202025-09-18
Platforms
Harness
Source repo
Safety notesRestrict the Airtable API key to the bases and write scopes Claude is allowed to use before enabling record or schema changes.Use a scoped Figma token and review export or edit permissions before granting access to shared design files.Use a read-only database user with restricted schemas unless write access is explicitly needed and reviewed.Use a restricted Redis user or database because commands can expose, mutate, or delete cache, queue, and session data.Restrict Stytch workspace and admin permissions because auth configuration changes can affect sign-in and account security.
Privacy notesAirtable records, field values, attachments, and base metadata may be sent through the MCP client and model context.Figma designs, comments, components, prototypes, team names, and file metadata may be sent through model context.Queried schemas, table names, rows, connection details, and application data may be exposed through tool calls.Keys, values, connection URLs, database metadata, and application data stored in Redis may be exposed through tool calls.User identities, authentication logs, session details, workspace settings, and security configuration may be sent through tool calls.
Prerequisites
  • Node.js 18+ installed for running npx commands and MCP server packages
  • Airtable Personal Access Token (PAT) from https://airtable.com/account
  • Required API scopes: data.records:read (minimum), data.records:write (for updates), schema.bases:read (for schema operations)
  • Base ID for the Airtable base you want to access (starts with 'app' prefix)
  • Figma Desktop application installed and running (download from https://www.figma.com/downloads/)
  • Figma Desktop Dev Mode MCP Server enabled (check Figma Desktop preferences/settings to enable)
  • Figma Desktop running with MCP Server active on local port 3845 (http://127.0.0.1:3845/mcp)
  • Internet connection (for initial Figma Desktop installation, though MCP server operates locally)
  • PostgreSQL database (local or remote PostgreSQL server)
  • PostgreSQL connection string (PostgreSQL connection URI with user, password, host, port, and database format)
  • Node.js and npx (for running @modelcontextprotocol/server-postgres package)
  • Network access (if connecting to remote PostgreSQL server)
  • Redis server running and accessible (local or remote)
  • Python 3.8+ and uvx package runner (for executing redis-mcp-server)
  • Redis connection URL (format: redis://[username]:[password]@host:port/db)
  • Network access to Redis server (default port 6379, or custom port)
  • Stytch account (free or paid plan)
  • Stytch API key authentication (for mcp.stytch.dev MCP connection)
  • Stytch project_id and secret from Dashboard (test or live environment)
  • Network access to mcp.stytch.dev (HTTP transport, not HTTPS)
Install
claude mcp add airtable --env AIRTABLE_API_KEY=YOUR_KEY -- npx -y airtable-mcp-server && claude mcp list
claude mcp list && claude mcp status figma
claude mcp list && claude mcp status postgres
uvx --from git+https://github.com/redis/mcp-redis.git redis-mcp-server --url redis://localhost:6379/0 && claude mcp list
claude mcp add --transport http stytch http://mcp.stytch.dev/mcp && claude mcp list
Config
{
  "mcpServers": {
    "airtable": {
      "env": {
        "AIRTABLE_API_KEY": "${AIRTABLE_API_KEY}"
      },
      "args": [
        "-y",
        "airtable-mcp-server"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "figma": {
      "url": "http://127.0.0.1:3845/mcp",
      "type": "http"
    }
  }
}
Manual-only setup:
{
  "postgres": {
    "args": [
      "-y",
      "@modelcontextprotocol/server-postgres",
      "postgresql://localhost/mydb"
    ],
    "command": "npx"
  }
}
{
  "mcpServers": {
    "redis": {
      "args": [
        "--from",
        "git+https://github.com/redis/mcp-redis.git",
        "redis-mcp-server",
        "--url",
        "redis://localhost:6379/0"
      ],
      "command": "uvx",
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "stytch": {
      "url": "http://mcp.stytch.dev/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool
  1. 01
    Why it made the cut

    Airtable MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  2. 02
    Why it made the cut

    Figma MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  3. 03
    Why it made the cut

    Postgresql MCP Server - MCP Servers is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  4. 04
    Why it made the cut

    Redis MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  5. 05
    Why it made the cut

    Stytch MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  6. 06
    Why it made the cut

    Workato MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  7. 07
    Why it made the cut

    Zapier MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  8. 08
    Why it made the cut

    bb-browser MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  9. 09
    Why it made the cut

    Browserbase MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  10. 10
    Why it made the cut

    BrowserMCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  11. 11
    Why it made the cut

    Chrome MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  12. 12
    Why it made the cut

    WebDriverIO MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  13. 13
    Why it made the cut

    Laravel Boost MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

  14. 14
    Why it made the cut

    Canva MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  15. 15
    Why it made the cut

    Discord MCP Server for Claude is included because it has maintainer-built package, safety notes present, privacy notes present, first-party source posture.

  16. 16
    Why it made the cut

    AI Game Developer Unity MCP Server is included because it has safety notes present, privacy notes present, source-backed source posture.

    Reach for instead

    If this will touch credentials, local files, or production systems, inspect the upstream source first.

Missing a pick? Propose an edit to this list — every change goes through the same review queue as new entries.

Suggest a pick
Weekly · Sundays

Get the weekly brief

One calm read on Claude workflows. Sundays. No tracking pixels.

Unsubscribe any time. No tracking pixels. No partner blasts.