Hygraph
About
Integrate Hygraph directly into MCP-compatible tools like Claude and Cursor, executing content operations via natural language
Details
- Author
- Unknown
- Categories
- Cloud Service, Other, Automation, API
Jump to
The Hygraph MCP server is available for all projects and is currently inEarly Access. Features may change, and production use should be evaluated accordingly.
The Hygraph MCP server connects AI assistants to your Hygraph project using theModel Context Protocol (MCP). It gives AI assistants, such as Claude, Cursor, Windsurf, and VS Code, a direct, permission-aware connection to your Hygraph project through a standardized interface to Hygraph's APIs.
Instead of setting up everything manually in Studio, you describe what you want in plain language. Tasks that previously required a developer, such as bulk content updates, schema creation, and cross-environment migrations, can now be done with a single prompt.
- Permission-aware by default:MCP operations follow the permissions defined on your Permanent Auth Token (PAT), so assistants can only perform actions you explicitly allow.
- Faster workflow automation:Use natural language to query, create, and publish content or apply structured bulk updates without writing one-off scripts for each task.
- Standardized integration across clients:Connect the same Hygraph project to multiple MCP-compatible tools, such as Claude, Cursor, VS Code, Windsurf, using a consistent server interface.
- Reduced operational risk:Destructive actions like delete and unpublish are not supported via MCP, helping prevent accidental data loss in automated workflows.
- Environment-aware workflows:Use separate endpoints and tokens per environment, such as staging vs production, to support safer deployment and review processes.
With the appropriate permissions (for example, aGeneral MCP ServerorContent MCP ServerPAT), AI assistants can:
- Read entries
- Filter and query entries
- Create new entries
- Update existing entries
- Publish entries
- Perform bulk updates
- Move content between environments
With the correct permissions (for example, aGeneral MCP ServerorManagement MCP ServerPAT), AI assistants can:
- Inspect existing content models
- Retrieve the structure of a specific model (fields, types, validations)
- Create new content models
- Add new fields to existing models
- Update field configurations
- Manage enumerations and components
- Move schema changes between environments
- Perform structured schema refactoring tasks
All MCP operations are governed by the permissions on your Permanent Auth Token (PAT). Use this table to choose the right token type for your workflow.
For full details on creating and configuring tokens, seeMCP server setup.
The following example prompts demonstrate how you can use natural language to interact with your Hygraph project through the MCP server.
- List all blog posts in Hygraph published this week.
- Find all entries in Hygraph with statusDRAFTthat were last updated more than 90 days ago.
- Find all posts in Hygraph with statusDRAFTand update their priority toHigh.
- Publish all entries in Hygraph currently in review.
- Find all posts in Hygraph withurgentin the title, update their priority toHigh, then publish them.
- Move all published entries in Hygraph to the staging environment.
- Show me the structure of theProductmodel in Hygraph.
- Create a new model in Hygraph calledAuthorwithname,bio, andavatarfields.
- Add a requiredSEO Titlefield to all models in Hygraph that represent pages.
- Add a new enumeration in Hygraph calledPrioritywith valuesLow,Medium,High.
- List all blog posts from Hygraph and create individual Markdown files for each post with front matter including slug, title, and publish date.
- Generate TypeScript types for all content models in Hygraph.
The Hygraph MCP server is designed to prevent accidental data loss in automated workflows. The following operations are intentionally not supported via MCP and must be performed manually in Hygraph Studio:
- Delete entries or schema elements
- Unpublish entries
This ensures that AI-assisted workflows cannot unintentionally remove or revert production content or schema.
Ready to connect your AI assistant? See theMCP server setup guide.
Manage content on the microCMS headless CMS using its content and management APIs.
Interact with the Umbraco CMS Management API for administrative tasks.
Apify-hosted MCP server for Webflow with 22+ tools. Sites, CMS collections, pages, content management, and publishing. No local setup needed.
Interact with Contentstack's Content Management API to manage your CMS content.
65+ AI tools as an MCP server. Research, write, code, scrape, translate, analyze, agent memory, workflows. Pay per call from $0.006.
Connects Claude to WordPress sites to create posts and manage sites using the WordPress REST API.
Ctrl Signal MCP - the harness for your AI generated landing pages
Your AI generates the landing page; ctrlsignal is the harness around it — hosting, lead capture, bookings, workflows and one-click rollback that turn a generated page into a live, lead-capturing site. Build in Claude Code, Cursor or any MCP client; no deploy config, no glue code.
This server enables AI assistants and other MCP clients to interact with Directus instances programmatically.
Connect Cursor, Claude Code, or any MCP-compatible tool directly to your ElmapiCMS instance. Manage collections, content, and assets through natural language.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


