Integration

Payload CMS integration

Open-source headless CMS and application framework built on Next.js. Payload provides a fully functional REST API auto-generated from your Collection and Global configs, supporting CRUD operations, authentication, versioning, media uploads, and powerful querying capabilities with automatic pagination and sorting. Features include access control, hooks, localization, and draft/publish workflows.

Connect Payload CMS How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Payload CMS.Built from the 28 Payload CMS tools below, on the connection you add once.

Common Payload CMS use cases

User logout
Upload images
Edit blog post
User login form
Add new blog post
Update site header
Extend user session
Load UI preferences
Password reset form
Preview old version

What you can do with Payload CMS

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 8 operations

bulk_delete_documentsBulk delete documentsDELETEBulk deletes all documents in a collection matching the provided where query.
bulk_update_documentsBulk update documentsPATCHBulk updates all documents in a collection matching the provided where query.
count_documentsCount documentsGETReturns the total count of documents in a collection, optionally filtered by query.
create_documentCreate documentPOSTCreates a new document in a specified collection with the provided field data.
delete_documentDelete documentDELETEPermanently deletes a document from a collection.
find_document_by_idFind document by idGETRetrieves a single document by its unique identifier from a specified collection.
find_documentsFind documentsGETRetrieves a paginated list of documents from a specified collection with optional filtering, sorting, and relationship population.
update_documentUpdate documentPATCHUpdates an existing document with partial or complete field data.

Authentication, 7 operations

forgot_passwordForgot passwordPOSTInitiates password reset by sending a reset token to the user's email.
loginLoginPOSTAuthenticates a user with email and password, returning a JWT token.
logoutLogoutPOSTLogs out the current user and invalidates their session.
refresh_tokenRefresh tokenPOSTRefreshes the JWT authentication token for the current user.
reset_passwordReset passwordPOSTSets a new password using a valid password reset token.
unlock_userUnlock userPOSTUnlocks a user account locked after exceeding the maximum failed login attempts.
verify_emailVerify emailPOSTVerifies a user's email address using the token sent during registration.

Version, 6 operations

find_collection_versionsFind collection versionsGETRetrieves a paginated list of document versions for a collection.
find_global_versionsFind global versionsGETRetrieves a paginated list of versions for a global document.
get_collection_version_by_idGet collection version by idGETRetrieves a single document version by its version ID.
get_global_version_by_idGet global version by idGETRetrieves a single version of a global document by its version ID.
restore_collection_versionRestore collection versionPOSTRestores a document to a previous version, making it the current live version.
restore_global_versionRestore global versionPOSTRestores a global document to a previous version.

Preference, 3 operations

create_preferenceCreate preferencePOSTCreates or updates a user preference by key.
delete_preferenceDelete preferenceDELETEDeletes a stored user preference by its key.
get_preferenceGet preferenceGETRetrieves a stored user preference by its key.

Global, 2 operations

get_globalGet globalGETRetrieves a single global document by its slug.
update_globalUpdate globalPOSTUpdates a global document with the provided field data.

Media, 1 operation

upload_mediaUpload mediaPOSTUploads a file to an upload-enabled collection with optional metadata.

User, 1 operation

get_meGet meGETRetrieves the currently authenticated user's profile and token information.

Use Payload CMS from Claude Code, Cursor or Codex

Connect Payload CMS in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Payload CMS operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Payload CMS

Create your workspace
Sign up free. Nothing to install.
Connect Payload CMS once
Add your Payload CMS connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Payload CMS integration FAQ

What can you do with the Payload CMS integration?

LiveContext exposes 28 operations on Payload CMS, covering document, authentication, version and preference. Common uses include User logout, Upload images and Edit blog post.