# How to connect Contentful to OpenClaw > Connect Contentful to OpenClaw in one click. 8 Contentful tools your agent can call from chat. No API keys. Web version: https://claw-link.dev/openclaw/contentful ClawLink gives OpenClaw a more practical Contentful setup than rolling your own integration. Install one ClawHub skill, connect Contentful in the browser, and OpenClaw can call real Contentful actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Contentful MCP for OpenClaw Looking for a Contentful MCP server for OpenClaw? ClawLink connects Contentful to OpenClaw and exposes 8 Contentful tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Contentful integration](https://claw-link.dev/hermes/contentful) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/contentful ## Setup It takes three steps to connect OpenClaw to Contentful. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Contentful** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect contentful # connect Contentful (browser OAuth) npx -y @useclawlink/cli actions contentful # list available actions npx -y @useclawlink/cli run contentful --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Contentful integration can do 8 Contentful tools are ready for OpenClaw once the account is connected. ### All 8 Contentful tools for OpenClaw | Tool | What it does | |---|---| | **Get content types** `contentful_get_content_types` | Retrieve all content types in an environment | | **Get asset** `contentful_get_asset` | Retrieve a single asset by ID | | **Get app definition** `contentful_get_app_definition` | Retrieve details of a specific app definition | | **Activate content type** `contentful_activate_content_type` | Activate (publish) a content type | | **Archive asset** `contentful_archive_asset` | Archive an asset | | **Archive entry** `contentful_archive_entry` | Archive an entry | | **Archive release** `contentful_archive_release` | Archive a release | | **Get editor interface** `contentful_get_editor_interface` | Retrieve editor interface configuration | ## Example prompts **Get Content Types** > Pull the relevant data from Contentful, summarize it in plain English, and point out anything that needs attention. **Get Asset** > Pull the relevant data from Contentful, summarize it in plain English, and point out anything that needs attention. **Get App Definition** > Pull the relevant data from Contentful, summarize it in plain English, and point out anything that needs attention. **Activate Content Type** > Use Contentful to activate content type and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Contentful working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Contentful app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Contentful through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Contentful. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Contentful actions to the runtime in a format your agent can reliably use. | 8 tools for Contentful are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Contentful to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Contentful in the browser, and the 8 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Contentful skill but can't call the tools The ClawHub skill teaches OpenClaw about Contentful, but the calls run through the ClawLink plugin and your connected account. Make sure Contentful is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Contentful from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### The Contentful account is connected but the action fails Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Contentful and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Contentful integration? Yes. ClawLink is the fastest way to connect OpenClaw to Contentful: link your Contentful account once in the browser and OpenClaw can call the Contentful API through 8 ready-made tools — no custom code or token handling. ### How do I add Contentful to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Contentful skill from ClawHub, then you click Connect in the dashboard to authorize Contentful. OpenClaw calls the tools from the next message — no config files or API keys. ### How long does it take to connect Contentful to OpenClaw? About two minutes. Sign in, click Connect next to Contentful in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Contentful up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Contentful working from chat. ### OpenClaw installed the Contentful skill but can't call the tools The ClawHub skill teaches OpenClaw about Contentful, but the calls run through the ClawLink plugin and your connected account. Make sure Contentful is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw Apify integration](https://claw-link.dev/openclaw/apify) — Run web scrapers, manage Actors, datasets, and schedules - [Connect Hostinger](https://claw-link.dev/openclaw/hostinger) — Manage domains, DNS, VPS, and web hosting - [Connect Vercel](https://claw-link.dev/openclaw/vercel) — Manage projects, deployments, domains, and environment variables