Use Grembed your way

Make links, read previews,
follow updates.

Use Grembed from your assistant, terminal or a little tool of your own. They all read the same public previews, and you don’t need an account or API key.

MCP CLI JSON API RSS & updates

Connect an assistant

Open your client’s MCP or tool connection settings and add a remote server.
Use https://grembed.dev/mcp with Streamable HTTP. No token or sign-in is needed.
Ask it to make a Grembed link, read a preview, or show the latest updates.

Remote connection

If your client uses a configuration file, this is the usual shape. The setting names can vary between clients.

{
  "mcpServers": {
    "grembed": {
      "url": "https://grembed.dev/mcp"
    }
  }
}

Try a request

“Make a Grembed link for https://civitai.com/user/ValentineDesigns.”

“What’s changed in Grembed recently?”

“Read the public preview for this link.”

Plain text guide for your assistant

If your client needs a local MCP command

Install the CLI below, then use grembed mcp. It runs a local connection over standard input and output, and reads the same public service.

{
  "mcpServers": {
    "grembed": {
      "command": "grembed",
      "args": [
        "mcp"
      ]
    }
  }
}

Use it from your terminal

The CLI needs Node.js 20 or later. Install it once, then use grembed for links, previews and release notes.

npm install -g https://grembed.dev/downloads/grembed-cli.tgz

grembed convert 'https://civitai.com/user/ValentineDesigns'
grembed resolve 'https://civitai.com/user/ValentineDesigns'
grembed updates --limit 3
grembed update creator-journeys-and-tools
grembed feeds
grembed info

Add --json when another program will read the result. updates accepts --limit and --offset for paging through the notes.

Run the standalone file instead

Download grembed.mjs and run it with Node. It has the same commands, so you can keep it with a project without installing a global command.

curl -fsS -o grembed.mjs 'https://grembed.dev/downloads/grembed.mjs'
node grembed.mjs convert 'https://civitai.com/user/ValentineDesigns'
node grembed.mjs updates --limit 3 --json

Call the JSON API

Use convert when you only need a share link; it doesn’t fetch a preview. Use resolve when you need the public title, creator, text, counters and selected media.

Request	What you get
`GET /api/convert?url=…`	Share, preview and original URLs.
`GET /api/resolve?url=…`	The public preview card.
`GET /api/updates?limit=10&offset=0`	Release notes and the next page offset.
`GET /api/info`	The version, connection links and request limits.
`GET /api/feeds`	The update blog and RSS feed.
`POST /api/tools`	Any of the six tool operations below.

Make a link

curl -fsS --get 'https://grembed.dev/api/convert' \
  --data-urlencode 'url=https://civitai.com/user/ValentineDesigns'

Call an operation

curl -fsS 'https://grembed.dev/api/tools' \
  -H 'Content-Type: application/json' \
  --data '{
  "name": "convert_link",
  "arguments": {
    "url": "https://civitai.com/user/ValentineDesigns"
  }
}'

Tool calls and the new GET endpoints return {"ok":true,"result":…}. Errors use an appropriate HTTP status and {"ok":false,"error":"…"}. The existing /api/resolve endpoint returns the card directly.

A conversion result contains share_url, preview_url and original_url. Preview fields depend on the link type and what Civitai makes public; an absent counter or picture stays absent.

OpenAPI document · Assistant guide

The same six operations everywhere

Operation	Arguments	Use it for
`convert_link`	`url`	Making a share link without fetching the page.
`resolve_preview`	`url`	Reading the public preview used by the embed.
`list_updates`	`limit`, `offset` (optional)	Reading recent release notes.
`get_update`	`id`	Reading one complete update.
`get_service_info`	None	Finding the current version and connection details.
`list_feeds`	None	Finding the update feed.

For get_update, use an entry’s id from list_updates. Each entry includes its version, title, summary, publication date, full notes and a link back to the blog.

Follow along with RSS

Add https://grembed.dev/rss.xml to your reader. Every update has its own permanent link, so you can share one set of notes without sending someone through the whole archive.

Read the update blog, ask your assistant for recent updates, or run grembed updates. They all use the same release notes.

A few practical details

Links can be up to 4,096 characters long. Update requests return up to 50 entries; use nextOffset to ask for the next page. JSON tool requests can be up to 64 KiB.

Preview lookups follow the same public visibility and media checks as shared embeds. If Civitai is unavailable or asks you to wait, check the response status and try again later; repeatedly requesting the same page won’t help it load sooner.

The tools don’t change Civitai content or start Radio playback. If all you need is a link, conversion is the quickest call.

Make links, read previews,follow updates.