leeshfield MCP

MCP (Model Context Protocol) server for leeshfield (video generation platform). AI clients (Claude, etc.) can log in to a leeshfield account via OAuth, add assets, reference them to generate videos, and receive results.

Architecture

MCP 클라이언트 (Claude 등)
   │  Streamable HTTP + OAuth 2.1 (PKCE)
   ▼
leeshfield-mcp  ← 이 리포. 얇은 어댑터 (리소스 서버)
   │  Bearer 토큰 그대로 전달 (introspection으로 검증)
   ▼
leeshfield 본체  ← 인가 서버(/oauth/authorize, /api/oauth/*) + REST API

• The authorization server is leeshfield itself. Because the user session (login/consent screen) lives on that domain. This server only advertises the AS location via RFC 9728 protected resource metadata.

• This server has no authority of its own. Every tool call passes the user access token straight through to the leeshfield API, and workspace permissions/tenant isolation are enforced by leeshfield.

• Stateless Streamable HTTP — no session state, safe for redeployment and multiple replicas.

Related MCP server: creatify-mcp

Tools

Environment Variables

Development

npm install
LEESHFIELD_URL=http://localhost:3000 MCP_PUBLIC_URL=http://localhost:3100 \
OAUTH_INTROSPECT_SECRET=dev PORT=3100 npm run dev

Validation: npm run typecheck && npm run lint

Client Connection

# Claude Code
claude mcp add --transport http leeshfield https://leeshfield-mcp.klr.kr/mcp

When connecting, a browser opens and you log in to leeshfield (Google/email), then approve on the consent screen. Client registration (DCR) and token issuance are automatic.

Deployment

• Branches: develop → dev(dev.leeshfield-mcp.klr.kr, internal network only) / main → prod(leeshfield-mcp.klr.kr)

• Jenkins → OCI Registry → ArgoCD (gitops apps/leeshfield-mcp)

• dev MCP points to dev leeshfield(dev.leeshfield.klr.kr), prod points to the prod main server.