Skip to main content
Glama
README.md
<p align="center">
  <img src="assets/glif-icon-400.png" width="120" alt="Glif" />
</p>

# Glif MCP Server

**Glif** is a media-generation agent: generate images, video, and audio, transcribe, render HTML, search the web, run code, and chain multi-step media operations — from any MCP client.

- **Endpoint:** `https://glif.app/api/mcp` (Streamable HTTP, JSON-RPC 2.0)
- **Auth:** OAuth 2.1 with dynamic client registration — sign in with your Glif account, no API keys
- **Install page with one-click buttons:** https://glif.app/mcp
- **Docs for agents:** https://glif.app/llms.txt

This repo holds the registry metadata for the hosted server (see [`server.json`](server.json)); the server itself is part of the glif.app platform and is not open source.

> [!NOTE]
> Looking for the old locally-run stdio server (npm `@glifxyz/glif-mcp-server`)? It's deprecated — the code is parked on the [`legacy-local-server`](https://github.com/glifxyz/glif-mcp-server/tree/legacy-local-server) branch.

## Tools

`compose_project` does the work — describe what you want in plain language, including a whole series of variations, and Glif picks the models and chains the steps. It returns a `job_id` immediately; poll `get_job_status` for the media, which comes back as `resource_link` blocks pointing at CDN URLs. The rest are read and upload helpers. Call `tools/list` for the authoritative set, or see https://glif.app/mcp.

Generation spends credits from the signed-in Glif account; read-only tools are free. See https://glif.app/pricing.

## Install

### Claude (web / desktop)

Settings → Connectors → **Add custom connector**, paste:

```
https://glif.app/api/mcp
```

### Claude Code

```sh
claude mcp add --scope user --transport http glif "https://glif.app/api/mcp"
```

### Cursor

[![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=glif&config=eyJ1cmwiOiJodHRwczovL2dsaWYuYXBwL2FwaS9tY3AifQ%3D%3D)

Or add to `.cursor/mcp.json`:

```json
{ "mcpServers": { "glif": { "url": "https://glif.app/api/mcp" } } }
```

### VS Code

```sh
code --add-mcp '{"name":"glif","type":"http","url":"https://glif.app/api/mcp"}'
```

### ChatGPT

Enable developer mode, then Settings → Apps & Connectors → **Add new connector**, paste `https://glif.app/api/mcp`, pick OAuth.

### Codex

```sh
codex mcp add glif --url "https://glif.app/api/mcp"
codex mcp login glif
```

### Any other MCP client

```json
{ "mcpServers": { "glif": { "url": "https://glif.app/api/mcp", "transport": "http" } } }
```

Your client opens a browser OAuth sign-in on first connect — approve it to link your Glif account. More clients (Replit, Hermes, OpenClaw, LM Studio, …) with copy-paste snippets: https://glif.app/mcp

## Links

- Website: https://glif.app
- MCP install page: https://glif.app/mcp
- Discord: https://discord.gg/glif
- X: https://x.com/heyglif

## Registries

- Anthropic MCP Registry

## License

MIT - see [LICENSE](LICENSE)

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing featured workflows, user info, personal workflows, running a workflow, searching workflows, and workflow details. No overlap or ambiguity.

Naming Consistency3/5

Naming patterns are mixed: some use verb+noun (list_featured_workflows, run_workflow, search_workflows), some use possessive+noun (my_user_info, my_workflows), and one uses noun+noun (workflow_info). This inconsistency could confuse an agent.

Tool Count5/5

6 tools is well-scoped for a workflow platform, covering essential operations without being overwhelming or too sparse.

Completeness3/5

Missing CRUD operations for workflows (create, update, delete), which are important for managing workflows. The set focuses on consumption and view only, leaving gaps for workflow creation and management.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive