OpenClipDocs
Developers & agents

Agent discovery surfaces

Every machine-readable endpoint OpenClip exposes for LLMs, crawlers, and autonomous agents.

OpenClip publishes purpose-built machine-readable surfaces so agents can discover the product, read pages as Markdown, and find the MCP server and Integration API without scraping HTML. If you are building an agent integration, start here; to actually connect, see MCP.

All surfaces

URLWhat it serves
https://openclip.app/llms.txtIndex of the site's key pages for LLMs, with links to their Markdown versions
https://openclip.app/llms-full.txtThe full site content in one Markdown file
https://openclip.app/{page}.mdMarkdown twin of a public page. Append .md to the path (for example https://openclip.app/mcp.md or https://openclip.app/pricing.md), or request the HTML URL with an Accept: text/markdown header
https://openclip.app/auth.mdMarkdown-only reference on how agents authenticate with OpenClip
https://openclip.app/docs/llms.txtIndex of every documentation page, linking to each page's raw Markdown
https://openclip.app/docs/llms-full.txtThe full documentation corpus in one Markdown file
https://openclip.app/docs/skill.mdAgent Skill file for these docs: when to use them and how to read them
https://openclip.app/docs.mdMarkdown twin of the documentation homepage
https://openclip.app/docs/{slug}.mdMarkdown twin of one documentation page, for example https://openclip.app/docs/developers/mcp.md
https://openclip.app/.well-known/mcp.jsonMCP Server Card: endpoint, auth, and capabilities of the MCP server
https://openclip.app/.well-known/mcp/server-card.jsonThe same Server Card at its SEP-1649 path (also at /mcp/server-card)
https://openclip.app/.well-known/mcp/catalog.jsonMCP catalog listing OpenClip's MCP servers
https://openclip.app/.well-known/agent-skills/index.jsonAgent Skills index; the skill files live at /.well-known/agent-skills/openclip/SKILL.md and /.well-known/agent-skills/openclip/reference.md
https://openclip.app/.well-known/api-catalogRFC 9727 API catalog (linkset) pointing to both the Integration API and the MCP server
https://openclip.app/sitemap.xmlMain XML sitemap
https://openclip.app/sitemap-ai.xmlSitemap of AI-relevant pages
https://openclip.app/docs/sitemap.xmlSitemap of the documentation site

Reading pages as Markdown

Public marketing pages negotiate content. Two equivalent ways to get Markdown instead of HTML:

# Append .md to the path
curl https://openclip.app/mcp.md

# Or negotiate on the HTML URL
curl -H "Accept: text/markdown" https://openclip.app/mcp

Docs pages use the same friendly alias: request /docs.md for the documentation homepage, or append .md to a page path such as /docs/developers/mcp.md. The /docs/llms.txt index lists every documentation page with its Markdown URL.

Finding the MCP server programmatically

An agent landing on openclip.app cold can bootstrap itself:

  1. Fetch /.well-known/api-catalog. Its linkset anchors both the Integration API (with its OpenAPI spec) and the MCP server (described by the Server Card).
  2. Fetch /.well-known/mcp.json for the MCP endpoint and auth details, then connect as described in Connect over MCP.
  3. Optionally fetch the skill files from /.well-known/agent-skills/ (or the zip at https://openclip.app/mcp/skill) for the canonical usage instructions.

Installing the Agent Skills

The endpoints above serve the umbrella openclip skill, which covers the whole tool surface. The full published set lives in a public repo:

npx skills add OpenClip-App/agent-skills

That installs from OpenClip-App/agent-skills and works with Claude Code, Codex, Cursor, and 70+ other agents. Alongside openclip it carries focused skills for clipping, captions, transcription, media conversion, video editing, thumbnails, background removal, repurposing, and UGC ads. Install only the ones you need.

Claude Code can take the skills and the MCP server together, so there is no separate connection step:

/plugin marketplace add OpenClip-App/agent-skills
/plugin install openclip@openclip

Use the /.well-known/agent-skills/ endpoints when an agent is bootstrapping itself with no shell, and the CLI or plugin when a human is setting the agent up.

On this page