Custom MCP Server Integration

You can connect MCP servers already built within your enterprise to QueryPie AI Hub.

Key Features

Real-time communication with Remote MCP servers based on SSE (Server-Sent Events).
Supports authentication through custom headers. Currently only supports authentication with fixed values.
Supports dynamic tool schema loading.
Supports various MCP protocol versions.

How to Integrate Custom MCP Server

Access MCP Integrations Page

Click the All Integrations tab in the Integrations menu.

MCP Integrations Page

Click the Custom MCP Integration Setup card to navigate to the Install New MCP Integration page.

Enter Integration Information

Custom SSE Setup

Enter the following information in the Integration Information section:

Name (Required): Name of the MCP server to integrate (e.g., Custom SSE)
Description (Required): Brief description of the MCP server (e.g., Connect to Custom MCP SSE endpoint)
MCP Server URL (SSE) (Required): SSE endpoint URL of the MCP server
- Format: https://mcp.example.com/sse
- Enter the SSE endpoint URL of your actually running MCP server.

In the Headers for MCP server (Optional) section, set headers if authentication is required.

Key: Header key (e.g., Authorization, X-API-Key)
Value: Header value (e.g., Bearer your-token-here)
If additional headers are needed, click the + button to add more headers.

After entering all information, click the Install button.

Integration Complete

Integration Information Entry

Once integration is successful, you can check it in the Installed Integrations list.

The tools from the integrated MCP server automatically become available in AI chat.
You can create MCP Presets to combine tools for specific workflows.

Troubleshooting

Connection Failure

Verify that the MCP server URL is correct.
Check firewall settings.
Verify that custom header settings are correct.
Confirm that the MCP server is operating normally.

Tool Loading Failure

Verify that the MCP server returns correct tool schemas.
Check that the JSON format is correct.
Check server logs to analyze error messages.