Hubro Documentation Help

MCP (Model Context Protocol)

Model Context Protocol (MCP) is an open standard that enables seamless integration between AI models and external data sources or tools. In the context of Hubro, MCP acts as a bridge that allows your AI assistant to "understand" and interact with your study data and platform features directly.

What is MCP?

Think of MCP as a common language or set of rules that helps organize, exchange, and make sense of information shared between different components. By implementing this protocol, Hubro allows any MCP-compliant client (like Claude Desktop) to securely access resources and execute tools within the Hubro ecosystem without the need for custom, one-off integrations.

What can it be used for?

Integrating Hubro with an AI assistant via MCP opens up several powerful use cases:

  • Real-time Data Insights: Query the current status of your studies, such as the number of active participants or questionnaire completion rates.

  • Automated Reporting: Summarize study progress or identify trends in participant engagement using the AI's analytical capabilities combined with real-time platform data.

  • Enhanced Productivity: Use Hubro's internal tools directly from your chat interface to manage studies, check logs, or verify platform settings.

How to use integrated MCP provider

To connect your AI assistant to Hubro, you need to configure it to point to our MCP server. This typically involves using a gateway to bridge the communication.

Claude Desktop Configuration

Here's how you can use MCP in Claude Desktop. Update your claude_desktop_config.json file with the following configuration:

{ "mcpServers": { "Hubro": { "command": "docker", "args": [ "run", "-i", "--rm", "supercorp/streamableHttp", "--streamableHttp", "http://live.hubroplatform.no/mcp", "--oauth2Bearer", "YOUR_ACCESS_TOKEN" ] } } }

Authentication

The Hubro MCP server requires authentication via an OAuth2 Bearer token.

  1. Log in to the Hubro platform.

  2. Navigate to Tools section, MCP access and click on "Generate Token".

  3. Replace YOUR_ACCESS_TOKEN in the configuration above with your actual token.

Sample prompts

18 May 2026