Skip to main content
A Connector links Figr to an external tool through the Model Context Protocol (MCP). Once connected, the agent can call that tool live during a canvas query, fetching funnel data, reading a doc, or pulling tickets, and design directly from what it finds. Where a Design Language defines how things look and a Context Pod captures what your product is, Connectors bring in what is true right now: your live, changing data.

​
Available connectors

The Connectors page lists ready-to-use integrations:
  • Analytics: Mixpanel, Amplitude
  • Docs and knowledge: Notion, Confluence, Google Workspace
  • Product and planning: Linear, Miro, Mobbin
  • Communication: Slack, Granola
Each shows its name, category, and connection status. Anything not listed can be added as a custom connector.

​
Open the Connectors page

Reach it two ways: from the canvas, click the database icon in the chat console, then Manage connectors. Or open Connectors in workspace settings.
Canvas chat console with the Manage connectors option

From the canvas, the database icon opens Manage connectors.

​
Connect a standard tool

Using Mixpanel as the example:
1

Click Connect

Find the tool on the Connectors page and click Connect.
2

Review the setup modal

A modal opens, like “Mixpanel, Add connector,” with instructions and a warning that you will be redirected to authenticate.
3

Authorize with OAuth

Click Connect with OAuth. Your browser opens the provider’s authorization page. Review the requested access, like tracking, metrics, and funnel queries, then click Authorize.
4

Return to Figr

You land back with a “Connected to Mixpanel” banner. The tool now shows a green Connected badge and a toggle.
Toggle a connector off anytime to stop the agent from using it, without disconnecting.
Connectors page listing integrations like Notion, Mixpanel, and Linear

The Connectors page, with available integrations and Add custom.

​
Add a custom connector

Any MCP-compatible tool can be added manually.
1

Click Add custom

Top right of the Connectors page.
2

Fill in the details

Name (a label, like Figr MCP), MCP Server URL (the endpoint, like https://mcp.figr.design/mcp), and Transport type (the connection method).
3

Add the connector

Click Add connector. It saves with a yellow Requires authentication badge.
4

Authenticate

Click Connect to run the OAuth handshake, then Allow access on the consent screen. The badge turns green and the connector is live.
Add custom connector modal with Name, MCP Server URL, and Transport type

The Add custom connector modal.

​
Connection states

​
Using connectors in a design

Once a tool is connected, ask for what you need on the canvas. The agent decides when to call the connector and pulls the data in mid-task.
For the first one, Figr queries the connected Mixpanel source for live funnel data, finds the weakest step, and designs against the real numbers. No export, no copy-paste.
Canvas chat querying live Mixpanel funnel data to generate insights

A canvas query pulling live funnel data from a connected source.

​
Why it matters

Static inputs go stale. A screenshot of last quarter’s dashboard is wrong the moment the data moves. Connectors keep Figr current: every query fetches fresh data, so designs reflect reality at the moment you ask.

​
Best practices

  • Connect only what you will use. Each active connector is a tool the agent may call, and a focused set keeps queries fast and predictable.
  • Toggle off rather than disconnect when pausing a tool you will return to.
  • Name custom connectors clearly so you can tell them apart.
  • Be specific in prompts. Name the data you want, like “last 30 days of signup funnel,” so the agent queries precisely.
  • Review OAuth scopes before authorizing, so you know exactly what access you are granting.

​
Troubleshooting

Figr MCP

Expose your own project context to AI coding assistants over MCP.

Context Pods

Bundle static product knowledge for a project.

Setting up Design Language

Teach Figr how your product should look.