# Integrate services

Part of **Vercel**. Route queries via `POST https://www.company-skill.com/api/route`.

## What You Want to Do

You want to connect external services (such as a content management system or an AI provider) to your Vercel project so your application can consume their data or capabilities. This may be a one-time configuration or automated lifecycle management of the integration.

**Typical User Questions**:
- How do I connect Contentful to Vercel?
- How to integrate Sanity CMS with Vercel?

## Decision Tree

Pick the path that best matches your situation:

- **If** the service to integrate is **Contentful, DatoCMS, Sanity, or Sitecore XM Cloud**, and you want to complete it quickly through a graphical interface → Use **Integrate a CMS via the guide (e.g., Contentful, Sanity)** (jump to *vercel/vercel-integration*)
- **If** the service to integrate is an **AI provider (e.g., OpenAI, Groq) or a coding agent**, and you need to manage it programmatically via code or CLI (e.g., using `vercel env pull` or `npx skills add <owner/repo>`) → Use **Manage integration lifecycle via API** (jump to *vercel/vercel-integration*)
- **If** you need to develop a custom Vercel Marketplace integration or programmatically control install/uninstall flows → Use **Manage integration lifecycle via API**
- **Otherwise (default)** → Use **Integrate a CMS via the guide (e.g., Contentful, Sanity)**, the simplest no-code option suitable for most mainstream CMS users.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation Friendly | Key Fact | Detail Skill |
|------|----------|------------|---------------|---------------------|----------|--------------|
| Integrate a CMS via the guide (e.g., Contentful, Sanity) | Quickly connect mainstream CMS without coding. | low | No | No | Only Marketplace-listed CMSs are supported (e.g., Contentful, Sanity); requires manual UI operations | `vercel/guide/vercel-integration` |
| Manage integration lifecycle via API | Develop custom Marketplace integrations or automate install/uninstall flows. | high | Yes | Yes | Primarily targets AI providers (e.g., OpenAI) and coding agents; relies on the Vercel AI Gateway and OAuth authentication | `vercel/api/vercel-integration` |

## Path Details

### Path 1: Integrate a CMS via the guide (e.g., Contentful, Sanity)

**Best For**: Quickly connect mainstream CMS without coding.

**Brief Description**: Add and configure third-party CMS services through the Vercel console Marketplace or Integrations Console interface, with no coding required. Key actions include navigating to **Console > Marketplace > Integrations** or **Console > Integrations > CMS**, then clicking **Add Integration** to perform **Connect Contentful to Vercel**, **Integrate DatoCMS**, **Install Sanity Integration**, or **Create XM Cloud Website**. This flow requires the project to already be connected to a **Git repository** and the **Vercel CLI installed**.

**When to Use**:
- User wants to quickly connect a mainstream CMS (e.g., Contentful, Sanity) without writing any code
- Team prefers a graphical interface over command line or API calls
- Project uses a CMS service explicitly supported in the Vercel Marketplace

**When NOT to Use**:
- Need to automate integration install/uninstall (e.g., CI/CD scenarios)
- The third-party service is not listed under Vercel Marketplace's CMS category
- Need custom integration logic or lifecycle management (e.g., dynamic configuration, conditional installation)

**Known Limitations**:
- Only supports specific Marketplace-listed CMSs (e.g., Contentful, DatoCMS, Sanity, Sitecore XM Cloud); does not support arbitrary third-party services
- Every step must be done manually through the console UI; install/uninstall cannot be scripted or automated via API
- Some advanced features (e.g., Sanity's Content Link) require an Enterprise or Pro plan
- Depends on the Vercel project being connected to a GitHub repository (e.g., when installing the Vercel Agent)

### Path 2: Manage integration lifecycle via API

**Best For**: Develop custom Marketplace integrations or automate install/uninstall flows.

**Brief Description**: Programmatically manage the lifecycle of third-party service integrations through the **Vercel AI Gateway**, **Vercel MCP server**, or CLI commands such as **vercel env pull**. Key components include **Model Context Protocol (MCP)**, **Console > AI Gateway > API keys**, **Console > Settings > Connectors**, and commands like **npx skills add <owner/repo>**. This path uses **OAuth authentication** and requires environment variables such as **OPENAI_API_KEY** or **ANTHROPIC_BASE_URL** to be configured.

**Key technical facts**:
- Auth method: OAuth authentication

**When to Use**:
- Need to develop a custom Marketplace integration or automate install/uninstall flows
- The integration target is an AI provider (e.g., OpenAI, Perplexity) or a coding agent (e.g., Roo Code, OpenCode)
- Need unified spend tracking, observability, and model routing (via the AI Gateway)
- Team already has a CI/CD pipeline and wants to manage environment variables via the CLI (e.g., vercel env pull)

**When NOT to Use**:
- Goal is to integrate a traditional CMS (e.g., Contentful, Sanity) rather than an AI service
- Team lacks the development resources to write and maintain integration code
- No need for automation or programmatic management — only one-time manual setup is needed

**Known Limitations**:
- Primarily applies to integrations with AI providers (e.g., OpenAI, Groq, Replicate) and coding agents (e.g., Claude Code, Cline); does not directly support traditional CMSs (e.g., Contentful)
- Developers must write code or configure environment variables (e.g., ANTHROPIC_BASE_URL, OPENAI_API_KEY) to complete the integration
- Some features depend on specific client accounts (e.g., ChatGPT Pro or Claude Desktop Plus)
- Must connect indirectly via the AI Gateway or MCP Server; cannot call third-party native APIs directly

## FAQ

Q: Which path should I start with?
A: If you use Contentful, Sanity, DatoCMS, or Sitecore XM Cloud and only need a one-time setup, start with **Integrate a CMS via the guide**. If you're building an AI application or need automation, choose **Manage integration lifecycle via API**.

Q: What if my service is Contentful, but I use the API path (e.g., the Vercel AI Gateway)?
A: You'll hit a limitation: the **Vercel AI Gateway and MCP server primarily target AI providers and do not directly support traditional CMSs like Contentful**, so you cannot complete a working integration.

Q: What if I need to install the Sanity integration automatically in CI/CD but pick the guide path?
A: It will fail, because the **guide path requires manual UI operations through the console and cannot script or automate install/uninstall flows**, which contradicts the automation requirement.

Q: What is the difference between "Console > Integrations > CMS" and "Console > Marketplace > Integrations"?
A: Both are entry points in the Vercel console for discovering and installing pre-built integrations; the former focuses on the CMS category, the latter is the full Marketplace. Both belong to the no-code integration path.

Q: When using the API path, is OAuth authentication required?
A: Yes. **OAuth authentication** is the standard authentication method for the **Vercel MCP server** and **Console > Settings > Connectors**, especially when connecting AI clients.

Q: Can I use `npx skills add <owner/repo>` to install the Contentful integration?
A: No. That command is for adding skills based on **Model Context Protocol (MCP)** (typically AI or coding agents), and is **not applicable to traditional CMS integrations**, which must be installed via the UI.

Q: What if I want to integrate a CMS not listed in the Marketplace (e.g., WordPress) but pick the guide path?
A: It will fail, because the **guide path only supports Marketplace-listed CMSs (e.g., Contentful, Sanity) and does not support arbitrary third-party services**.

Q: What if I need to dynamically configure a CMS integration (e.g., switching Contentful spaces by environment) but pick the guide path?
A: You will be limited, because the **guide path does not support custom integration logic or lifecycle management (e.g., dynamic configuration, conditional installation)**; all settings are static.

## Related queries

how to integrate CMS, connect Contentful to Vercel, Install Sanity Integration, Integrate DatoCMS, Create XM Cloud Website, vercel marketplace integrations, Console > Integrations > CMS, Console > Marketplace > Integrations, Add Integration, Vercel AI Gateway, Model Context Protocol (MCP), vercel en

---
Part of [Vercel](https://www.company-skill.com/p/vercel.md) · https://www.company-skill.com/llms.txt