> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect AI Agents to MCP servers

> Attach Model Context Protocol (MCP) servers to Fliqr AI Agents so they can use Shopify, Stripe, Zapier, Make, and other MCP-capable systems.

MCP (Model Context Protocol) servers expose tools and data from external systems to your AI Agent. Instead of building a custom HTTP function for every action, you connect an MCP server and attach it to the agent.

## When to use MCP

* Browse products or customers in **Shopify** / **WooCommerce**
* Work with payments data in **Stripe**
* Reach hundreds of apps through **Zapier** or **Make** MCP bridges
* Any vendor that publishes an MCP endpoint

For a single custom API you own, [Functions & actions](/docs/core-concepts/ai-agents/functions-actions) may still be simpler.

## Add an MCP server

<Steps>
  <Step title="Open MCP Servers">
    Go to **AI Center → AI Tools → MCP Servers**.
  </Step>

  <Step title="Add New">
    Click **Add New** and enter the MCP server **URL** and **authentication** type required by the provider.
  </Step>

  <Step title="Save">
    Confirm the connection. Fix auth errors before attaching the server to an agent.
  </Step>
</Steps>

## Attach MCP to an Agent

<Steps>
  <Step title="Edit the Agent">
    Open the AI Agent that should use the server.
  </Step>

  <Step title="Select the MCP server">
    In the **AI tools** section, select the MCP server you added.
  </Step>

  <Step title="Prompt for tool use">
    In the system prompt, describe when the agent should use store/CRM/payment tools. Clear intent language improves tool selection.
  </Step>

  <Step title="Test">
    In the Playground, ask a question that requires live MCP data (for example, “Is SKU 123 in stock?”).
  </Step>
</Steps>

## Popular MCP-capable services

Examples teams commonly connect: **Zapier**, **Make**, **Shopify**, **Stripe**, **WooCommerce**, and other platforms that publish MCP support.

<Warning>
  MCP tools can read or change external data. Scope credentials tightly and treat model-selected tool calls like untrusted input on the server side.
</Warning>

## Next

<CardGroup cols={2}>
  <Card title="Functions & actions" icon="bolt" href="/docs/core-concepts/ai-agents/functions-actions">
    Define custom HTTP tools when MCP is not available.
  </Card>

  <Card title="Best practices" icon="check" href="/docs/core-concepts/ai-agents/best-practices">
    Safe tool use and prompt patterns.
  </Card>
</CardGroup>