2 posts tagged with "Integration"

Figma is where product teams live — design files, component libraries, design tokens, comments, dev resources, webhook events, activity logs. But AI agents can't see inside Figma unless you give them structured access to the right surface at the right granularity.

MCP (Model Context Protocol) solves this by letting agents call Figma as a set of typed tools. Instead of pasting screenshots into ChatGPT or describing your component hierarchy by hand, the AI reads your files, inspects components, mutates variables in transactional batches, posts comments, attaches dev resources, and debugs webhook delivery — programmatically.

The MCPBundles Figma bundle exposes Figma's REST API as 30 MCP tools built around how design teams actually work. This post walks through what's there.

Most APIs weren't built for AI agents. Stripe has 300+ endpoints. GitHub's API returns paginated results that change between requests. Slack rate-limits you after 20 calls per minute. None of them were designed for Claude to use directly.

We wrapped dozens of REST APIs into MCP tools and learned that a thin wrapper doesn't work. You need to rethink the interface completely—actions instead of CRUD, consolidated search instead of endless list endpoints, and server-side resilience for pagination and rate limits.

Here's what actually works.