Glif MCP Server

What glifxyz/glif-mcp-server MCP server does

The glifxyz/glif-mcp-server MCP server connects MCP clients to Glif’s hosted agent at https://glif.app/api/mcp. It is designed for natural-language media tasks rather than exposing a collection of narrowly defined generation parameters. An agent can describe a desired result, including multiple stages or variations, and Glif selects models and chains the requested operations.

Supported workflows include generating images, video, and audio; transcribing content; rendering HTML; searching the web; and running code. These capabilities can be combined into a larger project workflow. The repository contains registry metadata for the hosted service, while the server implementation runs as part of the Glif platform and is not open source.

How it works

The endpoint uses Streamable HTTP with JSON-RPC 2.0. The central compose_project operation starts a workflow and returns a job_id immediately. The client then calls get_job_status to check progress and obtain the resulting media. Completed outputs are returned in resource_link blocks that point to CDN URLs.

The repository advises clients to call tools/list for the authoritative tool inventory. Other available operations are described as read and upload helpers, but the excerpt does not enumerate their individual names or parameters. This makes the live server tool list the appropriate source when implementing a client integration.

Setup and configuration

Configure the remote URL in an MCP client rather than installing a local process. Claude, Cursor, VS Code, ChatGPT, Codex, and other MCP clients are supported through HTTP configuration examples in the project documentation. Claude Code and Codex also provide command-line registration examples, while Cursor can use its MCP configuration file.

On the first connection, the client opens a browser-based OAuth sign-in flow. Approving that flow links the client to a Glif account. Authentication uses OAuth 2.1 with dynamic client registration, and the README states that no API key is required.

The general configuration is equivalent to an MCP server entry with the Glif URL and HTTP transport. The hosted endpoint, rather than the deprecated local npm server, should be used for new integrations.

Tools and capabilities

The glifxyz/glif-mcp-server MCP server is suited to agents that need to:

• Describe a multi-step media project in plain language.
• Generate image, video, or audio outputs.
• Transcribe media.
• Render HTML as part of a workflow.
• Search the web or run code during project composition.
• Poll asynchronous jobs and consume CDN-linked media results.

Generation operations use credits from the authenticated Glif account. Read-only tools are free, according to the README; consult Glif’s pricing information for current credit details.

Limitations and notes

This repository is not the implementation of a locally runnable server. The former @glifxyz/glif-mcp-server stdio package is deprecated, so using that package for a new setup would not match the current hosted service. Network access and an MCP client with HTTP and OAuth support are required.

The exact tool set may change; use tools/list or the current Glif MCP documentation rather than relying on a fixed list. Generated media consumes account credits, and results are delivered as links to CDN resources rather than described as local files. The repository includes an MIT license for its contents, but the hosted server itself remains part of the Glif platform and is not open source.