Docsbot.ai

Docsbot.ai MCP integration

Searches an indexed documentation base for grounded answers, keeps its sources re-indexed, and escalates the questions it cannot close.

Connect Docsbot.aiSee all integrations

38actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Generate conversation ticket

    Lyro converts a DocsBot chat into a support ticket. Your team escalates complex conversations to humans.

  • Get bot statistics

    Lyro retrieves analytics for a DocsBot over a time period. You see how many questions it answered and how well.

  • Create bot

    Lyro creates a new bot within a DocsBot team. Your support docs are now AI-searchable for customers.

See all 38 actions

How businesses use Docsbot.ai + Lyro

Each card is one request a support team gets, and the Docsbot.ai actions Lyro runs to close it.

  • Ground an answer in the indexed documentation

    Lyro runs a semantic search over the bot's indexed content and pulls back the most relevant chunks, so a product question is answered from your own docs rather than from a general model.

    Semantic Search Bot ContentList Bot SourcesGet Source Details

  • Add a new document to the knowledge base

    Lyro requests a presigned upload URL, sends the file to storage, and registers it as a bot source, so a new policy or release note is answerable as soon as it finishes indexing.

    Get Upload URLUpload File to Cloud StorageCreate Bot Source

  • Keep the indexed sources from going stale

    Lyro lists what a bot has been trained on, re-indexes a source that failed, and removes the page that no longer exists, so the knowledge base matches what your docs actually say today.

    List Bot SourcesRefresh SourceDelete Source

  • Turn a stuck conversation into a ticket

    When the docs do not cover the question, Lyro saves the lead's details and generates a ticket with a subject and body written from the customer's side, then hands the thread to a human agent.

    Capture Conversation LeadGenerate Conversation TicketList Bot Leads

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Docsbot.ai actions it has and picks the ones a request needs.

  1. 01

    Connect Docsbot.ai

    Authorize the Docsbot.ai account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Docsbot.ai actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Docsbot.ai · Lyro

Everything else about Docsbot.ai

Setup, permissions, and the limits of what Lyro can do inside Docsbot.ai.

  • Yes. Generate Conversation Ticket needs a Standard plan or higher, and the conversation has to have been created through the Chat Agent API rather than the legacy Chat API. The other DocsBot.ai actions Lyro uses, including Semantic Search Bot Content, carry no such requirement.

Every action available in Docsbot.ai

All 38 actions your agent can call on Docsbot.ai, straight from the live MCP connection.

  • Capture conversation lead

    Capture lead information by updating conversation metadata and saving the lead.

  • Create bot

    Create a new bot within a team.

  • Create bot source

    Create a new source for a bot.

  • Create webhook

    Create a new webhook subscription for a bot.

  • Delete bot

    Delete a specific bot by its ID.

  • Delete conversation

    Delete a specific conversation by its ID.

  • Delete lead

    Delete a specific lead by ID.

  • Delete question

    Delete a specific question from history.

  • Delete source

    Delete a specific source from a bot by its ID.

  • Delete webhook

    Delete a webhook (unsubscribe) by its ID.

  • Generate conversation ticket

    Generates a structured support ticket from a Chat Agent conversation.

  • Get bot details

    Fetch details of a specific bot by ID within a team.

  • Get bot monthly reports

    Retrieve monthly statistical reports for a bot.

  • Get bot statistics

    Retrieve comprehensive statistics and analytics for a bot over a time period or date range.

  • Get source details

    Retrieve detailed information about a specific source by its ID.

  • Get team details

    Fetch details of a specific team by its ID.

  • Get upload URL

    Get a presigned upload URL for uploading files as sources.

  • Get webhook details

    Retrieve details of a specific webhook by ID.

  • List team bots

    List all bots for a given team.

  • List bot conversations

    List conversation history for a bot with pagination.

  • List bot leads

    List captured leads for a bot with pagination and date filtering.

  • List questions

    List all questions asked of a specific bot.

  • List research jobs

    List all deep research jobs for a bot with pagination support.

  • List bot sources

    Retrieves a paginated list of all sources for a specific bot within a team.

  • List team members

    List all members of a team including their roles.

  • List teams

    List all teams.

  • List bot webhooks

    List all registered webhooks for a bot.

  • Rate answer

    Rate an answer from chat APIs as positive (1), neutral (0), or negative (-1).

  • Refresh source

    Refresh a source to re-index its content.

  • Semantic search bot content

    Perform semantic search on a bot's indexed content.

The tools Docsbot.ai sits next to

Same connection, same setup. Pick the next one your team already uses.

Browse every integration

Ready to connect Docsbot.ai?

Authorize the account and your agent has all 38 actions from the first conversation.

Connect Docsbot.aiTalk to sales
Support agent working at a laptop next to the Lyro mascot