#MCP server

The Hygraph MCP server is available for all projects and is currently in Early Access. Features may change, and production use should be evaluated accordingly.

The Hygraph MCP server connects AI assistants to your Hygraph project using the Model 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.

#Key benefits

• 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.

#What you can do

#Content operations

With the appropriate permissions (for example, a General MCP Server or Content MCP Server PAT), AI assistants can:

• Read entries
• Filter and query entries
• Create new entries
• Update existing entries
• Publish entries
• Perform bulk updates
• Move content between environments

#Schema operations

With the correct permissions (for example, a General MCP Server or Management MCP Server PAT), 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

#Permissions

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.

PAT type	Read	Create	Update	Publish	Schema management	Delete
General MCP Server	✓	✓	✓	✓	✓	✗
Management MCP Server	—	—	—	—	✓	✗
Content MCP Server	✓	✓	✓	✓	—	✗
Read-only (custom)	✓	—	—	—	—	✗

For full details on creating and configuring tokens, see MCP server setup.

#Example prompts

The following example prompts demonstrate how you can use natural language to interact with your Hygraph project through the MCP server.

Content queries:

• List all blog posts in Hygraph published this week.
• Find all entries in Hygraph with status DRAFT that were last updated more than 90 days ago.

Content updates:

• Find all posts in Hygraph with status DRAFT and update their priority to High.
• Publish all entries in Hygraph currently in review.

Multi-step workflows:

• Find all posts in Hygraph with urgent in the title, update their priority to High, then publish them.
• Move all published entries in Hygraph to the staging environment.

Schema operations:

• Show me the structure of the Product model in Hygraph .
• Create a new model in Hygraph called Author with name, bio, and avatar fields.
• Add a required SEO Title field to all models in Hygraph that represent pages.
• Add a new enumeration in Hygraph called Priority with values Low, Medium, High.

Combined workflows:

• 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.

#Safety guardrails

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.

#Next steps

Ready to connect your AI assistant? See the MCP server setup guide.