MCP Hub overview
The MCP Hub is how your team connects approved AI assistants and tools to Prego in a controlled way. You do not need to know how the connection is implemented behind the scenes—your administrator or IT contact can follow the steps below and use the API overview if they need technical entry points.
What you can do
- Ask questions in context — Assistants can work with information your organization has chosen to expose through Prego, according to your plan and permissions.
- Automate routine steps — Combine MCP with your existing workflows (for example, summaries or notifications) where your product edition allows it.
- Stay within your guardrails — Access is tied to your organization’s tenant and the roles your admin assigns.
Before you start
- Confirm with your Prego administrator that MCP is enabled for your organization and which tools are allowed.
- Use only company-approved clients (for example, a supported IDE or assistant product).
- Treat connection details like any other credential: do not share them in chat, email, or public repositories.
Getting connected (typical flow)
- Open Settings (or the integration area your admin indicates) in the Prego admin experience.
- Request or create an MCP connection for the tool you use; your admin may need to approve it.
- In your AI tool, add the MCP server using the URL and authentication method your admin provides.
- Run a small test (for example, a simple read-only question) to confirm the link works.
If anything fails, contact your internal Prego admin or Prego support with the time of the attempt and the name of the client you used—avoid sending secrets.
Related
- Integrations — MCP alongside APIs and the SDK.
- API overview — Base URLs, authentication, and how requests are scoped to your organization.
- SDK overview — Building on top of Prego from apps or scripts.
- Authentication guide — How users and services sign in to Prego.