Skip to main content
This guide describes the OAuth connection update. Your MCP service and Knowlify app must both run that update. An older connector that asks for an apiKey still uses the previous setup.
MCP lets an AI assistant call Knowlify Training and Marketing video tools through one connector. With the OAuth connection, you sign in to Knowlify and approve access once. You do not paste an API key into a chat.

​
Connect

  1. Add one connector named Knowlify with the remote MCP URL supplied by your administrator. It ends in /mcp.
  2. Choose OAuth authentication and click Connect. If an older entry uses no authentication, remove it and add it again.
  3. Sign in on Knowlify. Check the client name, return address, and personal account on the approval page.
  4. Approve Training, Marketing videos, or Training and Marketing video access only if you started this connection. Both categories use the same connector.
  5. Ask your assistant: “List the available Knowlify Training styles and voices.”
If Claude retains an older Training-only tool list after reconnecting and refreshing tools, remove that entry and replace it with the same URL ending in /mcp?v=0.6.0. This forces fresh discovery while keeping one connector. Start a new chat after reconnecting. The current test service URL is https://knowlify-mcp-production.up.railway.app/mcp. Its hostname does not identify which API environment it uses. Your administrator configures that separately. Do not put your Knowlify API key into the connector URL, chat, or an OAuth client-secret field. The client discovers the sign-in flow automatically.

​
Client setup

​
Codex

The add command may start sign-in automatically; if it does, a second login is unnecessary. Approve the request while the terminal is waiting. If the callback expires, run login again and use the new request. Start a new session to load the connector. Codex CLI receives tool results and links; it must poll status explicitly instead of displaying the HTML player. For noninteractive codex exec runs, read-only tools can succeed while creation and editing are blocked by the client’s approval policy. Use an interactive approval flow, or --approve-for-me for explicitly authorized automation so Codex’s approval reviewer can evaluate each operation. Do not disable the sandbox or bypass approvals to make a test pass.

​
Claude Code

Claude Code also needs its own working Anthropic subscription or API billing. This is separate from Knowlify authorization. Native desktop callbacks are supported by Knowlify MCP 0.6.1 and later.

​
Cursor

Add a remote MCP server in Cursor’s settings and authenticate it. Alternatively, merge this entry into your existing user MCP configuration, preserving other servers:
Enable Knowlify for the chat being tested. Cursor compatibility requires MCP 0.6.4 for its callback registration and 0.6.5 for Marketing player refresh routing. Inline player availability depends on the client surface; video links remain the fallback. If Cursor asks “MCP App wants to call” get_video_status or get_marketing_video_status, choose Approve this tool to permit that read-only status tool. Automatic player updates cannot proceed while this permission is pending. Server-wide approval also covers other tools, including operations that edit videos or use credits, so it is not required for this check. Open the tool activity to see the player, then click Play when it is ready.

​
ChatGPT

Your account/workspace must permit custom remote MCP apps. If Developer mode is required, keep CSP enforcement enabled. In the tested web interface, open Plugins → Create app, enter the Knowlify server URL, and choose OAuth. Leave optional OAuth client credentials empty for automatic registration. Complete Knowlify approval, then select Try in chat. Developer mode installs an unreviewed app for testing; it does not publish Knowlify in the public directory. Availability and administrator controls vary. The same connection supports both video categories.

​
What you allow

The connection can create Training videos, retrieve video links, edit videos, undo eligible edits, and change narration voices. It can read styles, curated and personal custom voices, and website branding. Video work can consume your account credits. This release supports your personal workspace. It includes older videos without a saved category that appear in Training history. Organization workspaces are outside this connection’s scope. Marketing videos require explicit permission within the same connector; see Marketing videos. Existing Training connections remain Training-only. Your account must have API access.

​
Training tools

The same connector also exposes 16 Marketing video tools, for 26 tools total. Visibility in a tool list does not grant permission: each call checks the approved category. For example: “Create a 30-second workplace safety Training video. Request a 50/50 blend of cinematic scenes and Remotion infographics. Look up knowlify.com branding and apply its selected colors, fonts and logo. Show me the video when it finishes.” The cinematic percentage is a planning target, not an exact timing guarantee. Creation and editing are asynchronous. Compatible embedded players show one card per accepted video and check progress automatically while visible. Checks run at least 15 seconds apart per video, with at most 20 checks per minute per player. They pause after 30 minutes, on errors, or when the video needs user action. Refresh resumes paused checks. Other clients must poll until the video completes; a job ID alone is not a finished video. Reopening a saved completed card triggers one automatic status read to recover expired links and reflect later edits. A media-load failure schedules one bounded retry. Repeated failures leave the Refresh and Open video fallback. Playback requires clicking Play; the player cannot notify you while its chat is closed. Older chats may cache an earlier player; refresh the connector tool catalog and use a new tool call to load the current player. If the client shows “Unable to reach Knowlify” instead of the player, inspect the tool result separately. A completed status with video_url can still be opened even when the client cannot load the embed. A blank or failed embed is not an active automatic poller. Ask for the returned video link as a fallback, and report the client display error. See the current verification results.

​
Disconnect or reconnect

In Knowlify, open Developer → Manage video connections. Click Disconnect beside the client to stop future requests. Work already submitted can still finish. Connections expire after 30 days. Clients refresh their short-lived access tokens automatically until then. Reconnect if your connection expires, you revoke its underlying API key, or the client reports that authorization is required. If the assistant asks for an API key, check that the server has the OAuth update and recreate the connector so it reloads authentication and tool definitions. See Testing and availability for the underlying Training API.