MCP and Developer API access
Connect AI agents to a source-backed knowledge base.
Keldura turns videos, documents, websites, and video channels into organized folders first. Then agent users can connect through MCP setup surfaces, and developers can build with the Developer API.
MCP for agent access - Developer API for software - folder knowledge - safe API-key handling
Agent access starts with organized knowledge
The useful part is not another generic prompt box. It is giving tools a structured, cited workspace to use.
Import source material.
Collect videos, playlists, channels, websites, local files, Drive documents, images, audio, and PDFs.
Organize it into folders.
Keep source collections manageable before exposing them to agent workflows or software integrations.
Connect through MCP or API.
Use MCP for agent access and the Developer API for application workflows that need Keldura knowledge.
MCP is agent access, not a Bot channel
Keldura keeps the public terminology clear so teams know which surface they are configuring.
MCP for agent tools.
Use the MCP setup surface when an agent-capable client needs access to Keldura knowledge.
Developer API for software.
Use API docs and API-key settings for programmatic workflows, while keeping secrets out of recordings and shared docs.
Bots for people-facing chat.
Define Bots from folders, prompts, and models when people should ask questions through channels such as Telegram or Website widget.
Citations for trust.
Keep agent and API workflows grounded in the same source folders used by cited Chat inside the app.
Related Keldura workflows
AI agent knowledge base FAQ
How do agents access Keldura knowledge?
Keldura exposes agent access through MCP setup surfaces and exposes software access through the Developer API.
Is MCP a Bot channel?
No. MCP is agent access for tools and clients. Bot channels are people-facing surfaces such as Telegram and Website widget.
Can agents use video and document folders?
Yes. The value of the workspace is that videos, documents, websites, and source channels can be organized into folders before agent or API access.
Give agents a real knowledge workspace.
Import and organize the source material first, then connect tools through MCP or software through the API.
Try Keldura free