Provisioning on Control Hub

Publisher

Cisco Systems, Inc. (Webex for Developers)

URL

https://developer.webex.com/mcp/docs/provisioning-on-control-hub

Published

unknown

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• An administrator can review each tool's input schema, output schema and annotations from Control Hub before enabling it. fact in context
• Cisco defines an agentic app as a service exposing structured capabilities that an artificial intelligence agent can invoke, not tied to a protocol, and analogous to a Model Context Protocol server when that standard is used. fact in context
• The authorization code method requires a registration endpoint and an authorization endpoint in addition to the fields the client credentials method requires, the user token method requires no administrator input at all, and the application key method requires only the key. fact in context
• The authentication section in Control Hub asks for details according to the configuration set in the developer portal, so what an administrator must supply is determined by what the developer registered. fact in context
• An authorise automatic server data updates setting lets changes to a server's name, description, transport type, other metadata or its address within the same domain take effect without re-authorisation, while showing the administrator an indication that changes occurred. fact in context
• Cisco states that Cisco official servers have their authentication configured automatically and that an administrator should change the settings only to override the default. fact in context
• Agentic app provisioning lives in Control Hub under Apps and then Agentic Apps, and the list shows public apps together with private apps onboarded by users of the organisation. fact in context
• Custom headers allow up to 5 key and value pairs and are configurable for all authentication types. fact in context
• Control Hub presents 5 authentication methods for an agentic app: OAuth2 client credentials, OAuth2 authorization code, user token, application key and custom headers. fact in context
• The general tab of an agentic app in Control Hub allows or blocks the app for all users of the organisation. fact in context
• The provisioning documentation states that users bear full responsibility for understanding, complying with and managing all aspects of the liability framework related to their use of Model Context Protocol applications, and never defines what that framework is or where it is published. fact in context
• Cisco states that the Control Hub provisioning guide is for administrators only, covering user access, authentication and governance controls over which agentic capabilities are available. fact in context
• Cisco states that re-authorisation is always needed to formally approve a new tool schema, whether or not the signature change setting allows continued access. fact in context
• Cisco states that similar functionality is available on the resources and prompts pages and does not itemise what similar covers. inference in context
• For a Model Context Protocol server Control Hub presents 3 capability tabs, 1 each for tools, resources and prompts. fact in context
• For OAuth2 client credentials the token endpoint authentication method may be client secret basic or client secret post, and for the authorization code method it may additionally be none. fact in context
• Enabling a tool in Control Hub makes it discoverable and usable by organisation users, and disabling it makes the tool no longer visible or available to them. fact in context

Cite this source record

APA

WarmTransfer. (2026, September 5). Provisioning on Control Hub. WarmTransfer. https://warmtransfer.net/knowledge/sources/webex-dev-provisioning-on-control-hub

BibTeX

@misc{warmtransfer-webex-dev-provisioning-on-control-hub,
  title  = {Provisioning on Control Hub},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/webex-dev-provisioning-on-control-hub},
  note   = {Cisco Systems, Inc. (Webex for Developers), accessed 2026-09-05}
}