Aigist

What Aigist MCP server does

The Aigist MCP server gives an LLM-controlled workflow access to published HTML and Markdown pages on Aigist. An agent can create a page and receive a shareable URL, inspect pages it has published, read the source of a specific page, replace that page’s contents while keeping its URL, or remove it.

Aigist is suited to workflows where generated content needs to become a link that other people can open. Examples include publishing a rendered document, maintaining a page through successive edits, or cleaning up pages that are no longer needed. The service also provides access control and Figma-style comments, according to the project description.

How it works

The service is hosted remotely at https://ai-gist.com/mcp and uses Streamable HTTP. There is no local server process to run or self-host. A compatible MCP client connects to that URL and invokes the available tools on the user’s behalf.

Authentication uses OAuth. On first use, the client opens a sign-in flow where the user can authenticate with GitHub or Google. After authentication, page operations apply to the user’s published pages rather than requiring credentials supplied as environment variables.

The Aigist MCP server exposes five operations:

• publish creates an HTML or Markdown page and returns a shareable URL.
• list_pages returns the user’s published pages.
• get_page retrieves the source for one page.
• update_page changes a page without changing its URL.
• delete_page removes one of the user’s pages.

Setup and configuration

For Claude Code, register the remote endpoint with:

claude mcp add --transport http aigist https://ai-gist.com/mcp

Claude Desktop Pro, Max, Team, and Enterprise users can add the URL as a custom connector. A browser-based sign-in completes the OAuth setup. Claude Desktop users on any plan can instead install the supplied aigist.mcpb bundle by downloading it and confirming the installation; the bundle includes the remote bridge and its dependencies.

Cursor can use a server entry with the URL in ~/.cursor/mcp.json or a project-level .cursor/mcp.json:

{
  "mcpServers": {
    "aigist": { "url": "https://ai-gist.com/mcp" }
  }
}

Clients that only support stdio can connect through mcp-remote, using npx -y mcp-remote https://ai-gist.com/mcp. The repository also includes a script for rebuilding the desktop bundle.

Tools and capabilities

The Aigist MCP server supports the full basic page lifecycle: create, enumerate, read, revise, and delete. Updates happen in place, so an existing page can retain its URL while its HTML or Markdown source changes. The remote service’s shareable pages, access control, and comments support collaboration around generated content.

Limitations and notes

The README documents OAuth sign-in and hosted access, but does not specify page limits, content-size limits, permissions granularity, comment operations, or retention rules. The listed MCP tools manage pages and their source; no separate comment tool is documented. Clients without native HTTP MCP support need the mcp-remote bridge or the provided Claude Desktop bundle.