Hygraph logoMCP server · Content and web

Hygraph MCP server

Hygraph in any MCP client, through Memtro: Hygraph does not publish this server. Memtro's Hygraph connector reads Hygraph through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Hygraph headless CMS: the project's content models (found by introspection), entries of any model with previews of their text fields and their created, updated and published dates, and assets with file names, types and sizes. When asked, creates, updates, publishes, unpublishes or deletes one entry, and creates from a URL, publishes, unpublishes or deletes one asset.

Reads

  • hygraph_list_modelsThe content models in the Hygraph project (Post, Product, Author…), each with the query name used to list its entries and the text fields previewed.
  • hygraph_list_entriesEntries of one Hygraph model, newest change first by default: id, created, updated and published dates, and short previews of the model's text…
  • hygraph_list_assetsAssets (images, documents, video) in the Hygraph project, newest change first: file name, MIME type, size in bytes, dimensions for images…

Acts, when you ask

These change something in Hygraph. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • hygraph_create_entryCreate one entry in a Hygraph model, as a DRAFT (nothing is published until hygraph_publish_entry).
  • hygraph_update_entryChange fields of one Hygraph entry by id.
  • hygraph_publish_entryPublish one Hygraph entry's draft to a content stage (normally PUBLISHED), making it live for everyone who reads that stage, such as the website.
  • hygraph_unpublish_entryUnpublish one Hygraph entry from a content stage (normally PUBLISHED): readers of that stage, such as the website, no longer see it.
  • hygraph_delete_entryPermanently delete one Hygraph entry by id, from every stage.
  • hygraph_create_asset_from_urlCreate a Hygraph asset by having Hygraph fetch a file from a public https URL, as a DRAFT.
  • hygraph_publish_assetPublish one Hygraph asset to a content stage (normally PUBLISHED), so entries on that stage can show it.
  • hygraph_unpublish_assetUnpublish one Hygraph asset from a content stage (normally PUBLISHED); readers of that stage lose it.
  • hygraph_delete_assetPermanently delete one Hygraph asset by id; entries that use it lose it.

Connect it

First connect Hygraph on Dashboard → Connections, then add Memtro to your client once. The Hygraph tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Hygraph connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › What changed in our Hygraph blog posts this week?
  • › Which content models does our Hygraph project have?
  • › Show the draft versions of our product entries changed since Monday.
  • › When was the pricing page entry last published?
  • › Publish the draft of the spring launch post

Questions

Is this an official Hygraph MCP server?
No. It is Memtro's MCP server with Memtro's Hygraph connector behind it: the connector reads Hygraph through its API with the credentials you connect on Dashboard → Connections, and Hygraph publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Hygraph?
Only when you ask, and only what it has been granted: create a draft entry in a model; update fields of one entry (the draft, published content changes when it is published); publish one entry to a content stage (readers of that stage see it); unpublish one entry from a content stage (readers lose it); delete one entry (permanent); create an asset from a public URL; publish one asset; unpublish one asset; delete one asset (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time