DocsBot AI MCP integration for AI agents.
Connect AI agents to DocsBot AI through 6 structured actions, including get bot, fetch document, and get team. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the DocsBot AI integration exposes
The DocsBot AI Agent App exposes 6 provider-backed actions for ai and data work. Its current contract lets an authorized agent get a docsbot bot by team and bot id, fetch the full reconstructed document text for a docsbot search result file id, and get a docsbot team by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected DocsBot AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real DocsBot AI capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_botREADGet a DocsBot bot by team and bot ID.
INPUTS: teamId / botId
fetch_documentREVIEWFetch the full reconstructed document text for a DocsBot search result file ID.
INPUTS: teamId / botId / fileId
get_teamREADGet a DocsBot team by ID.
INPUTS: teamId
list_botsREADList DocsBot bots in a team.
INPUTS: teamId
list_teamsREADList DocsBot teams visible to the API key user.
semantic_searchREADSearch a DocsBot bot's trained source chunks by natural-language query.
INPUTS: teamId / botId / query / top_k / autocut
INPUT CONTRACTS
Know what the action needs before it runs.
get_bot
teamIdOPTIONAL- The DocsBot team ID.
botIdOPTIONAL- The DocsBot bot ID.
fetch_document
teamIdOPTIONAL- The DocsBot team ID.
botIdOPTIONAL- The DocsBot bot ID.
fileIdOPTIONAL- The DocsBot file ID returned by semantic_search.
get_team
teamIdOPTIONAL- The DocsBot team ID.
list_bots
teamIdOPTIONAL- The DocsBot team ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bot
Get a DocsBot bot by team and bot ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_botVerify with Get Team
Get a DocsBot team by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_teamSAFETY BOUNDARY
Operate DocsBot AI with explicit limits
- Authorize DocsBot AI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned DocsBot AI data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in DocsBot AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the DocsBot AI task completed successfully.
CONNECTION MODEL
API key
DocsBot AI user API key sent as a Bearer token. Create or change it from the API Keys section of your DocsBot dashboard: https://docsbot.ai/app/api
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by DocsBot AI.