Skip to main content
Parlance — home

Extensions

Parlance extensions bring your UI contracts into the tools your team already uses — the design canvas, the browser, your editor, native development, shipped apps and your AI agents. Every extension consumes the Parlance client SDK and connects to your workspace, so each one audits against the very same contracts, glossaries and tokens. One source of truth, in every tool you reach for.

For how audits and issues work, see audits. To browse the extensions with feature detail, see the extensions showcase.

How extensions fit together

Each extension is a different lens on the same contract:

  • It connects to your workspace, so it sees your projects, contracts and glossaries.
  • It runs audits against the same contracts the platform uses — no separate rules per tool.
  • It reports issues by severity and flags drift in context, then can push those issues back to your workspace.
  • It consumes the client SDK, which is the single way every extension talks to Parlance.

The result is that design, code, live products and native apps are all held to one definition, wherever the work happens.

The six extensions

Figma plugin

Audit designs against your contracts without leaving the canvas. Source: design.

Install & connect

  1. Install Parlance from Figma Community.
  2. Open any file and run the plugin from Plugins → Parlance.
  3. Paste an API key from Dashboard → Settings → API keys to connect your workspace.
  4. Select frames or components and run a contract check — issues appear in place and can be pushed to your project.

Showcase: /extensions#figma-plugin.

Browser extension

Audit live production against the same contracts, in a real browser. Source: live. Available for Chrome, Firefox and Safari.

Install & connect

  1. Install it for your browser:
  2. Open any page, click the Parlance icon in the toolbar and choose Run audit.
  3. It works standalone with no account — connect an API key to audit against your own contracts and capture issues to a project.

Showcase: /extensions#browser-extension.

VS Code extension

Catch drift in the editor, as you write. Source: code. Automate with the SDK / REST API.

Install & connect

  1. Install Parlance Auditor from the Visual Studio Marketplace (or search “Parlance” in the Extensions view).
  2. Run Parlance: Set API Key from the command palette to connect your workspace, then Parlance: Select Project.
  3. Run Parlance: Run Accessibility Audit — diagnostics appear inline. To run the same checks outside the editor, automate them with the SDK or REST API.

Showcase: /extensions#vscode-extension.

Xcode

Bring contracts to native iOS development. Source: native, during development. Runs in Xcode against Swift.

Install & connect

  1. Download Parlance for Xcode from the Mac App Store.
  2. Enable Parlance Editor under System Settings → Privacy & Security → Extensions → Xcode Source Editor, then restart Xcode.
  3. Connect your workspace with an API key, then audit SwiftUI and UIKit screens from Xcode's Editor menu — built on the shared ParlanceKit core, against the same contracts as web.

Showcase: /extensions#xcode.

Native auditor

Audit shipped native apps against your design system. Source: native. Ships as the Parlance Browser app for iPhone and iPad.

Install & connect

  1. Download Parlance Browser from the App Store.
  2. Browse to any product screen inside the app and run an audit — token and accessibility checks on real, shipped UI.
  3. Connect an API key to push issues to your workspace with native attribution.

Showcase: /extensions#native-auditor.

MCP server

Give your AI agents and tools first-class access to Parlance audits over the Model Context Protocol. Published on npm as @parlancelabs/mcp-server.

  • Exposes contracts, glossaries and audits over the Model Context Protocol.
  • Run audits from any MCP-compatible client.
  • Automate enforcement in agentic workflows.

Install & connect

  1. Add the server to any MCP-compatible client by running npx @parlancelabs/mcp-server.
  2. Set PARLANCE_API_KEY from Dashboard → Settings → API keys so the server can reach your workspace.
  3. Point your client at the server — contracts, glossaries and audits are available as MCP tools.

Showcase: /extensions#mcp-server.

Choosing the right extension

Pick by where the work happens:

Next steps

  • Audits — what audits report and how to read issues.
  • Client SDK — the SDK every extension consumes, live on npm.
  • REST API — automate Parlance in your own services.
  • Extensions showcase — store links and the full feature breakdown for each extension.