01
Connect Payload once
Install the plugin in the Payload project that owns your content. Your database and files stay where they are.
The control plane for Payload + AIShip better content.
Keep control.
Schemalink gives AI clients a permission-aware way to discover, improve, and manage the content already living in your Payload projects.
Built for teams moving fast with content
A shorter path from setup to useful.
No content migration. No second admin panel. Just a clear connection between the tools you use and the content you own.
02
Choose the boundaries
Select the projects, collections, and actions each AI connection can use. Publishing and deleting stay explicit.
03
Ask in plain language
Your AI client discovers the shape of your content, then works through the permissions you approved.
From package install to your first useful prompt.
Install the plugin
Your content is structured. Your AI access should be too.
Permission by design
Give each connection the smallest useful access: project, collection, operation, and nothing more.
Payload stays the source
Schemalink coordinates requests. Your content, database, and media stay in the systems you already operate.
One connection, many projects
Connect an AI client once, then decide exactly which Payload projects it can see.
An audit trail that helps
Know what changed, which client requested it, and when—without reading server logs.
The questions your team already asks.
Make the work you already do with Payload faster, more complete, and easier to review.
Start with a projectFind the gaps
“Which posts need better SEO?”
Search real content, inspect the fields that matter, and get a focused list instead of a spreadsheet dump.
Keep locales complete
“What is missing in French?”
Compare localized content across collections and identify missing or stale translations before they become a support ticket.
Work safely
“Update this as a draft.”
Let AI prepare edits while your live content stays untouched. Review, refine, and publish only when you are ready.
Give AI a way in. Keep your data boundaries intact.
Schemalink never hands an AI client your database credentials. It checks the connection, project, collection, and requested operation before the request reaches Payload.
Connect Your SiteYour database stays yours
Draft and publish are separate permissions
Every MCP action has an actor
Disable a connection without deleting it
AI access
LIVECodex
MCP connection
Permissions
DiscoverReadDraftUpdate
CollectionsAll collections
Last used2 minutes ago
Manage connectionEnabled
Permissions are checked again at request time.
More projects. Same sharp boundaries.
Try every Schemalink feature free for one month.
Solo
$9/month
1 month free
1 connected project
- Discover collections and schemas
- Read and search content
- Create and edit drafts
- Compare locales and find gaps
- Publish and delete content
- Manage media and audit activity
Pro
Most flexible$19/month
1 month free
Up to 3 connected projects
- Discover collections and schemas
- Read and search content
- Create and edit drafts
- Compare locales and find gaps
- Publish and delete content
- Manage media and audit activity
Agency
$39/month
1 month free
Up to 10 connected projects
- Discover collections and schemas
- Read and search content
- Create and edit drafts
- Compare locales and find gaps
- Publish and delete content
- Manage media and audit activity
A little less mystery.
No. Payload remains the source of truth. Schemalink checks and routes authorized requests to the installation that already owns your content.
Ready when your content is
Let AI do the busywork.
Keep the final say.
Set up the connection once. Let your AI search, check, and draft. Give every important action a boundary.
Connect Your Site