DocsBot

Use DocsBot to administer DocsBot teams, bots, sources, members, integrations, Skills, reporting, and read-only account usage through an OAuth-authenticated remote MCP server. Activate when a user asks to manage DocsBot, inspect DocsBot account state, configure bots or sources, review dashboard data, or use the DocsBot Admin API through an agent.

Use this skill when working with the hosted DocsBot server:

text

https://mcp.docsbot.ai

The hosted server advertises fixed, named Admin MCP tools. Call a known tool directly with its operation-specific pathParams, query, and/or body input. For example, call list_teams to resolve the team, list_bots with pathParams.teamId to resolve a bot, and get_bot with pathParams.teamId and pathParams.botId to inspect it. Read the advertised input schema before sending fields that are not already clear. Do not call a generic execute tool or send an operationId.

list_tool_categories, search_tools, and get_tool_schema inspect metadata for tools already advertised to the client. Use them only when the relevant name or schema is unclear; they do not enable, execute, or discover hidden operations. Stable tool names remain callable across additive, backward-compatible hosted MCP updates. New or changed metadata may be held by OpenAI's automated scan while the last approved definition remains live; a newly added tool is unavailable until approved. Keep calls compatible with the currently advertised schema. Plugin skills, config, and listing changes require a new package ZIP.

Download Approvals

Generated question-log, lead, Q&A, and source downloads (export_question_log, export_leads, export_qa_source, and get_source_download_url) are additive, non-destructive operations that create temporary private transport files. Hosted policy classifies these tools as non-read-only; use the client's approval flow when requested. They leave application records and earlier downloads unchanged. Signing an existing source file with get_source_file_download_url remains read-only. Never bypass an approval prompt or infer authorization to perform another action from download approval.

Setup

If the MCP server is not already configured, add it to the client as a Streamable HTTP MCP server:

json

{
  "mcpServers": {
    "docsbot": {
      "url": "https://mcp.docsbot.ai"
    }
  }
}

For Codex, the direct MCP setup is:

bash

codex mcp add docsbot --url https://mcp.docsbot.ai
codex mcp login docsbot

For Codex plugin installation, use the marketplace package in this repository instead:

bash

codex plugin marketplace add uglyrobot/docsbot-agent-skills
codex plugin add docsbot-administration@docsbot

OpenClaw Setup

Requires a DocsBot account with access to a team. Available tools depend on the account role and plan. If the server is not already configured, register its Streamable HTTP endpoint and use OpenClaw's native OAuth login:

bash

openclaw mcp set docsbot '{"url":"https://mcp.docsbot.ai","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login docsbot
openclaw mcp doctor docsbot --probe

Complete browser authorization with DocsBot. Keep credentials in OpenClaw's native OAuth store; do not paste tokens into skill files or chat. Start a new session after connecting so the tools load. Respect OpenClaw's configured tool approval policy. Installing this skill does not itself connect or authorize the MCP server.

Workflow

1. Establish the working team before any team-scoped action.
2. Establish the working bot before any bot-scoped action.
3. Call a known named tool directly. Use search_tools only to find an unfamiliar advertised tool.
4. Use get_tool_schema when required fields, permissions, or side effects are unclear.
5. Send the named tool's required pathParams, query, and/or body fields, without an operationId.
6. Keep useful IDs from results in thread context: team ID/name, bot ID/name, source IDs, member emails, integration IDs, and pagination state.
7. For writes, destructive actions, member changes, source deletion, or integration changes, summarize the intended action and ask for confirmation before execution unless the user's request already explicitly authorizes that exact action.
8. Report the result with IDs, names, and next steps that the user can verify in DocsBot.

Bot Builder Subworkflow

When the user asks to create, configure, tune, test, or hand off a new DocsBot bot, load the dedicated bot-builder subworkflow before making MCP writes.

That subworkflow is part of DocsBot, but it is intentionally kept as a nested reference tree because production bot creation has its own discovery, branding, source-selection, prompt, deployment, action, evaluation, and handoff rubric. Follow its reference chain from references/bot-builder/ for bot-building tasks instead of merging those rules into this general administration workflow.

During a new or complete bot setup, prepare the voice prompt as well as the text prompt. The logical voicePrompt is saved as voiceAgent.instructions. Follow the bot-builder's voice guidance to preserve existing settings; enable advanced voice only when the user requests it, confirms it, or clearly includes voice in the intended outcome.

Response Quality Subworkflow

When the user asks why a bot answered the way it did, to analyze conversation or question logs, diagnose bad/unanswered/escalated answers, debug retrieval with semantic search, find knowledge gaps from history, or improve response quality from log evidence, load the dedicated response-quality subworkflow before deep log analysis or remediation writes.

That subworkflow is part of DocsBot, but it is intentionally kept as a nested reference tree because log diagnosis has its own evidence rules, semantic-search debug matrix, root-cause taxonomy, revise→Q&A remediation, and handoff shape. Follow its reference chain from references/response-quality/ instead of improvising from general administration steps alone.

Evals and Instruction History

Before selecting a saved Evals or instruction-history workflow, inspect the currently advertised tools with search_tools and verify the relevant input contracts with get_tool_schema. Load the Evals and instruction workflow only for capabilities whose named tools are advertised. Bundled documentation does not mean Evals APIs, reports, version history, or dashboard handoffs are released for this account. If the tools are absent, draft questions locally, review ordinary conversation history through the response-quality workflow, and improve current instructions through advertised get_bot/update_bot tools. Do not call missing tools or promise saved sets, runs, or version restoration.

Team Detection

The Admin MCP token identifies the authorized DocsBot user. It does not contain a fixed team ID or role snapshot, and DocsBot checks current team access and permissions live on each call.

When the user does not provide a team ID:

1. Call list_teams.
2. If exactly one team is returned, use it as the working team and state its name.
3. If multiple teams are returned, choose only when the user's wording clearly matches a team name, domain, customer, or prior thread context.
4. If multiple teams remain plausible, ask the user which team to use and show the shortest useful choices: team name, team ID, plan, and bot count when available.

If a user says "current team", "my team", or "the active team", do not assume the dashboard session's internal currentTeam is available through MCP. Resolve the working team from explicit context or by listing teams.

Bot And Source Lookup

For bot-scoped work, ensure a working team is selected, call list_bots with pathParams.teamId, then match by exact bot ID first and bot name second. If the bot is ambiguous, ask the user to choose.

For source-scoped work, ensure working team and bot are selected, call list_sources with pathParams.teamId and pathParams.botId, and use pagination or supported filters instead of fetching every source. Match source IDs directly when provided; otherwise match by URL, title, type, status, or tags. Fetch the full source only when list results are insufficient.

Use tag operations when the task mentions source tags, retriever tags, targeted retrieval, or tagged documentation. Bot retrieverTags define the allowed tag vocabulary, and source tags must match that vocabulary.

Metadata Discovery Queries

When the tool name is unfamiliar, use search_tools with a focused task phrase:

• list teams
• get team
• list bots
• get bot
• update bot
• list sources
• get source
• create source
• update source
• delete source
• source tag counts
• team members
• invites
• questions
• conversations
• leads
• stats
• webhooks
• integrations
• MCP connections
• Skills library
• account usage

Metadata discovery is optional when the named tool is known. Use get_tool_schema for its advertised input contract when needed.

Fast Path Operations

Call these stable names directly for common setup and lookup tasks:

Task	Named tool
List teams visible to the authorized user	list_teams
Get one team by ID	get_team
Create a team	create_team
Update team settings	update_team
List bots in a team	list_bots
Get one bot by ID	get_bot
Create a bot	create_bot
Update bot settings	update_bot
Delete a bot	delete_bot
List a bot's research jobs	list_research_jobs
Get one research job	get_research_job
Cancel and remove a research job	cancel_research_job

If a named tool is absent from the advertised catalog, do not attempt a generic operation. Report that the capability is unavailable.

Constraints

• Do not call arbitrary DocsBot URLs. Use only advertised named tools.
• Do not invent team IDs, bot IDs, source IDs, or tool names. Resolve IDs from named read tools and use metadata discovery for unfamiliar advertised names.
• Treat existing DocsBot dashboard RBAC as the source of truth. If an action is denied, report the denial rather than attempting to bypass it.
• After an uncertain or timed-out write, read back the intended resource state before retrying. Repeated create or send calls can duplicate resources or effects; if the outcome cannot be verified, report the uncertainty instead of retrying blindly.
• Do not expose OAuth tokens, API keys, internal headers, or private response data beyond what the user needs for the task.
• Do not use Admin MCP for per-bot documentation retrieval or question-history semantic search; those are separate per-bot MCP servers.

Subscription and commerce mutations are outside this plugin. Do not use update_bot to enable Stripe payments, refunds, cancellations, or other commerce actions. Read account usage through an advertised read tool when available.

References

• DocsBot MCP server guide
• MCP client configuration examples
• Bot-builder subworkflow