#MCP tools reference
The Hygraph MCP server provides tools for content, schema, AI guidelines, agents, and project discovery.
On the project endpoint (https://mcp-{REGION}.hygraph.com/{PROJECT_ID}/{ENVIRONMENT}/mcp), the project and environment are a part of the MCP endpoint URL.
On the global endpoint (https://mcp.hygraph.com/mcp), the assistant calls list_projects and list_environments first, then passes project and environment on every subsequent tool call.
See Connection modes for how to choose between the two.
#Content tools
| UI name | Tool | What it does |
|---|---|---|
| List Content Types | list_entity_types | Lists content type names in the environment. Those names are the valid typename values for the other content tools. |
| Get Content Type Schema | get_entity_schema | Returns fields, types, required flags, and value shapes for one type. |
| List Entries | list_entities | Lists entries of one type, with limit, stage, and field selection. |
| Get Entries by ID | get_entities_by_id | Fetches specific entries by ID. Mixed types are allowed in one call. |
| Sample Entries Across Types | discover_entities | Samples a few entries across types. Recommended for exploration, not for bulk reads. |
| Search Content | search_content | Runs a full-text search across all types. Case insensitive, no operators. |
| Execute GraphQL | execute_graphql | Runs a Content API query or mutation. delete* and unpublish* operations are rejected. |
| Create Entry | create_entry | Creates an entry in DRAFT. |
| Update Entry | update_entry | Updates an existing entry in DRAFT. |
| Publish Entry | publish_entry | Publishes an entry from DRAFT to PUBLISHED. |
execute_graphql can run any non-destructive Content API mutation, including bulk updates across many entries at once. Review it with the same care you'd give write access to your content before you approve it with "Always allow" in your client.
#Schema tools
| UI name | Tool | What it does |
|---|---|---|
| Get Project Schema Overview | get_project_info | Overview of models, components, enumerations, locales, stages, and available migration operations. |
| Get Migration Operation Schema | get_management_operation_schema | Input schema and example for one migration operation. |
| Apply Schema Migration | submit_batch_migration | Applies schema changes in one transaction. Supports dry_run. |
#AI guidelines tools
| UI name | Tool | What it does |
|---|---|---|
| Get AI Guidelines | get_ai_guidelines | Loads the project's brand, glossary, audience, and legal guidelines so the assistant can follow them when writing or translating. Does not create or change guidelines. |
See AI Guidelines for more information.
#Agents tools
| UI name | Tool | What it does |
|---|---|---|
| List Agents | list_agents | Lists agents in the environment and which ones can be triggered manually. |
| Trigger Agent Run | trigger_agents | Starts a manual agent (Use in Agent runs) on one or more entries. Does not wait for completion. |
| Check Agent Run Progress | check_progress | Reports the latest run status per entry, or recent runs for that agent. |
list_agents appears when agent discovery works. trigger_agents and check_progress appear only if the environment has at least one active manual agent. Workflow-bound agents cannot be triggered from MCP. See MCP server: agent operations for the full flow.
#Discovery tools (global endpoint only)
| UI name | Tool | What it does |
|---|---|---|
| List Projects | list_projects | Lists the projects the user can access. |
| List Environments | list_environments | Lists environment names for that project. |
These two tools only exist on the global endpoint. The project endpoint has no discovery tools, because its project and environment are already available in the MCP endpoint URL.
#What's next
- MCP server: What the MCP server does and the permissions each tool needs.
- MCP server setup: Connect a client and choose a connection mode.
- AI Agents: How manual and workflow-bound agents differ in Studio.