search
Discovers relevant DocsBot Admin API catalog operations
LABSCO SUMMARY
Two tools plus live permission checks is how you expose a large admin API without a large tool surface.
The meta-tool pattern trades discoverability for context cost — a model must search before it can act, but the client only ever loads two definitions. What makes it safe here is that permissions are evaluated per call against the dashboard's own RBAC, so the executor cannot become a way around the roles you already configured. Scope admin is not a small grant, though; the boundary is the user's own permissions.
What it is
DocsBot's endpoint, using the meta-tool pattern: rather than a tool per operation, it exposes a search over its admin API catalogue and a generic executor.
What you get
- search — find the relevant admin API operations
- execute — run one with structured parameters, with DocsBot evaluating dashboard permissions at call time
- Alongside these, three portable Agent Skills packages: administration, documentation search and support
Requirements
OAuth with dynamic client registration, scope admin. Role-based access control and dashboard permissions are evaluated live on every MCP action rather than at connection time.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Doing admin work through a conversation
Search the catalogue for the operation, then execute it with the right parameters.
02
Keeping the tool list tiny
Two definitions instead of a catalogue, with discovery at call time.
03
Staying inside existing roles
Dashboard permissions are checked on every action, not just at connect.
2 tools
Listed in project docs. Your client may show a different list.
execute
Runs a selected catalog operation with structured parameters; DocsBot evaluates dashboard permissions and RBAC live on every action
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth (dynamic client registration); scope admin
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.docsbot.aiRequirements
- OAuth (dynamic client registration); scope admin
