Skip to main content

MCP Servers

MCP servers extend tenant capabilities by connecting external tool endpoints.

Step 1: Select an MCP Server​

  1. Choose a server aligned to a specific workflow.
  2. Confirm data and permission requirements.
  3. Assign a business and technical owner.

Step 2: Register the Server​

  1. Open MCP settings in the Web UI.
  2. Add server connection details.
  3. Apply authentication details through secure inputs.
  4. Save configuration.

Step 3: Define Access Policy​

  • Restrict access by role.
  • Limit high-impact capabilities to trusted users.
  • Require approvals for sensitive operations.

Step 4: Test and Validate​

  1. Run read-only tool calls first.
  2. Confirm expected behavior and output quality.
  3. Document support and incident contact details.

Step 5: Operate in Production​

  • Monitor availability and failures.
  • Rotate credentials on schedule.
  • Remove or disable unused servers.

For design-to-app delivery, this sequence works well:

  1. Add Figma Dev Mode MCP to import file structure, styles, and variables.
  2. Add source-control MCP (GitHub/GitLab) for branch + PR automation.
  3. Add deployment MCP (Vercel/Cloudflare/AWS) for preview + release.
  4. Add monitoring MCP (Sentry/Datadog) for post-deploy feedback loops.

This keeps MCP adoption useful, controlled, and production-safe.