pi-figma-remote-auth

Pi extension that authenticates and configures Figma Remote MCP for pi-mcp-adapter.

Packages

Package details

extension

Install pi-figma-remote-auth from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:pi-figma-remote-auth
Package
pi-figma-remote-auth
Version
0.1.1
Published
May 8, 2026
Downloads
245/mo · 245/wk
Author
diantama
License
MIT
Types
extension
Size
34.7 KB
Dependencies
0 dependencies · 2 peers
Pi manifest JSON
{
  "extensions": [
    "./index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-figma-remote-auth

A Pi extension that handles OAuth authentication and MCP config for Figma's hosted Remote MCP server (https://mcp.figma.com/mcp), so that an existing pi-mcp-adapter install can expose Figma tools inside Pi.

What this does

In short, it does two things:

  1. Writes the MCP server config (mcpServers.figma) into Pi's MCP config file, pointing at Figma's remote endpoint with auth: "oauth".
  2. Runs the OAuth flow against Figma and saves the resulting tokens in pi-mcp-adapter's auth store, so the adapter can connect without re-prompting.

The OAuth step uses a workaround for Figma's MCP client allowlist: the dynamic client registration registers as client_name: "Codex" (which Figma allows), then the credentials are stored in the format pi-mcp-adapter expects. Same idea as mcp-auth-helper, but writing into the Pi adapter's storage instead of OpenCode's.

This is not the local Figma desktop MCP bridge — it only configures the remote endpoint.

Prerequisite

Install pi-mcp-adapter first:

pi install npm:pi-mcp-adapter

Restart Pi.

Install this package

From npm:

pi install npm:pi-figma-remote-auth

Or from a local checkout:

pi install /absolute/path/to/pi-figma-remote-auth

Or for one run, without installing:

pi -e npm:pi-figma-remote-auth

Usage

Inside Pi:

/figma-remote-auth setup
/figma-remote-auth login

During login, Pi prints the Figma authorization URL. Copy it from the notification and open it in your browser — the extension does not auto-open and Pi's TUI may not render the URL as clickable. After authorizing, restart Pi (or /mcp reconnect figma) so pi-mcp-adapter reloads MCP config.

Use Figma tools through the adapter proxy:

mcp({ search: "figma" });
mcp({ connect: "figma" });
mcp({ tool: "figma_TOOL_NAME", args: "{}" });

Commands

/figma-remote-auth help
/figma-remote-auth status [--server figma]
/figma-remote-auth setup  [--global|--project|--shared] [--server figma] [--url https://mcp.figma.com/mcp] [--direct-tools] [--keep-alive]
/figma-remote-auth login  [--server figma] [--url https://mcp.figma.com/mcp] [--client-name Codex] [--port <port>]
/figma-remote-auth logout [--server figma]

setup and login first check that pi-mcp-adapter exists. If missing, install it before continuing.

By default, login uses a random free localhost callback port so it does not collide with pi-mcp-adapter's own OAuth callback server. Use --port only when you need a fixed callback URL.

Config targets:

  • --global (default): writes ~/.pi/agent/mcp.json or $PI_CODING_AGENT_DIR/mcp.json
  • --project: writes .pi/mcp.json
  • --shared: writes .mcp.json

Token store (written by login, removed by logout):

  • $MCP_OAUTH_DIR/figma/tokens.json when $MCP_OAUTH_DIR is set
  • otherwise ~/.pi/agent/mcp-oauth/figma/tokens.json or $PI_CODING_AGENT_DIR/mcp-oauth/figma/tokens.json

Security

Tokens are written with file mode 0600. Pi packages execute code with local system access; review before installing.