---
title: "MCP HTTP Endpoints"
description: "Connect to your MCP servers using the unified HTTP endpoint."
---

MCPHub provides a unified streamable HTTP interface for all your MCP servers. This allows you to send requests to any configured MCP server and receive responses in real-time.

**Security note**: MCP endpoints require authentication by default to avoid exposing connected tools and data. If you intentionally want public MCP access, disable **Enable Bearer Authentication** in the Keys settings. **Skip Authentication** only affects dashboard login. By default MCPHub reads Bearer credentials from the `Authorization` header, but this is configurable via **Bearer Auth Header Name** if upstream passthrough headers would otherwise conflict.

### Unified Endpoint

This endpoint provides access to all enabled MCP servers.

- **Endpoint**: `http://localhost:3000/mcp`
- **Method**: `POST`

### Group-Specific Endpoint

For targeted access to specific server groups, use the group-based HTTP endpoint.

- **Endpoint**: `http://localhost:3000/mcp/{group}`
- **Method**: `POST`
- **Parameters**:
  - `{group}`: The ID or name of the group.

### Server-Specific Endpoint

For direct access to individual servers, use the server-specific HTTP endpoint.

- **Endpoint**: `http://localhost:3000/mcp/{server}`
- **Method**: `POST`
- **Parameters**:
  - `{server}`: The name of the server.

> **Note**: If a server name and group name are the same, the group will take precedence.
