<!-- Generated from the rendered page by scripts/write-llm-mirrors.mjs. Do not edit by hand. -->
Canonical: https://molo17.com/corehub-mcp/
Markdown mirror: https://molo17.com/corehub-mcp/index.md
Title: Core Hub MCP server · Gluesync · MOLO17
Description: Embedded Model Context Protocol server inside Gluesync Core Hub — 55 RBAC-safe tools for pipelines, observability, connections, and SQL via SSE and streamable HTTP.

Gluesync Module

# Core Hub MCP server

An embedded Model Context Protocol server runs inside Core Hub and exposes pipeline management, debugging, observability, connections, and SQL tasks as tools an AI agent can call — with the caller’s own token and the same RBAC as the Web UI.

[Explore Core Hub MCP](#how-it-works) [Talk to our team](/contacts/?topic=data-architecture)

![](/_astro/corehub-mcp-hero.C1u-Xry3_2uCCPW.png)

1.  01 Connect an MCP client
2.  02 Call RBAC-safe tools
3.  03 Query via Query Studio tools

Why Core Hub MCP

## Operate Core Hub from the agents you already use

01 / Sidecars

### Extra MCP proxies

Extra MCP proxies mean another process to secure and upgrade.

02 / Privilege drift

### Keep the audit boundary

Agent credentials that bypass Control Plane roles break audit.

03 / Outcome

### Use any MCP client

Point Claude, Cursor, MCP Inspector, or any MCP client at Core Hub and keep the same permissions as the UI.

How it works

## Same JVM, same RBAC, standard MCP transports

1.  01
    
    Embed
    
    ### Mount beside REST
    
    corehub-mcp mounts /mcp (SSE) and /mcp/http (streamable HTTP) beside REST.
    
2.  02
    
    Authenticate
    
    ### Use the caller's identity
    
    Bearer session JWT or Personal API Token (gsp\_…); zero elevated privileges in the module; loopback REST into Core Hub.
    
3.  03
    
    Act
    
    ### Call governed tools
    
    55 built-in tools plus optional per-session Query Studio database tools when enabled.
    

Capabilities

## Core Hub operations exposed as governed MCP tools

Available now in Core Hub from 2.2.10.x. Public documentation highlights 2.2.11 Connections support and hardening; Automator/Bootstrapper MCP remains a separate local/stdio path.

Built into Core Hub

### 55 built-in tools

#### Operational coverage without a separate proxy

Use one embedded server for Core Hub management, diagnostics, and data tasks.

-   Pipelines, agents, entities, sync, notifications, and metrics
-   Mapping functions, Query Studio, groups, and configuration
-   License, version, export, and Connections

[View Core Hub MCP docs ↗](https://docs.molo17.com/gluesync/latest/gs-modules/corehub-mcp.html)

MCP connectivity

### Standard transports

#### SSE and streamable HTTP

Connect a compatible client through SSE at /mcp or streamable HTTP at /mcp/http.

-   Streamable HTTP example: https://corehub-host.example/mcp/http
-   Authorization: Bearer YOUR\_TOKEN (session JWT or gsp\_ personal API token)
-   SSE endpoint: /mcp

[View connection guidance ↗](https://docs.molo17.com/gluesync/latest/gs-modules/corehub-mcp.html)

Control Plane security

### Governance

#### The caller's token and permissions stay in force

The module adds zero elevated privileges and routes operations back into Core Hub under the authenticated caller.

-   Read-only mode, allow-lists, and on-by-default controls
-   No extra privileges beyond the caller's token and Control Plane RBAC
-   Tool exposure can be bounded to the operations you choose

[View governance controls ↗](https://docs.molo17.com/gluesync/latest/gs-modules/corehub-mcp.html)

Explore the platform

## Continue exploring Gluesync

Core Hub MCP complements AI data supply and Query Studio. Query Forge remains the separate federated JDBC path.

[![](/_astro/icon-area-integration.DeylOLbd_Z1RvPLe.png)

### AI & RAG

Keep AI-facing stores current and expose Core Hub operations under the caller's permissions.

Explore AI & RAG →](/solutions/ai-rag/) [![](/_astro/query-studio-hero.BzuhlI4l_oU0m4.png)

### Query Studio

Inspect schemas, run SQL, and provide optional per-session database tools to MCP clients.

Explore Query Studio →](/query-studio/) [![](/_astro/query-forge-hero.Bcbe4yko_lqgo9.png)

### Query Forge

Run federated SQL across isolated agents through a dedicated JDBC gateway.

Explore Query Forge →](/query-forge/)

Resources

## Core Hub MCP documentation and resources

Documentation ![](/media/d2c/homepage/Documentation.svg)

### Documentation

Technical guides, API reference, deployment tutorials.

[Read documentation ↗](https://docs.molo17.com)

Roadmap ![](/media/d2c/homepage/Roadmap.svg)

### Public Roadmap

What we're building next. Submit feature requests.

[View roadmap ↗](https://roadmap.molo17.com)

Support ![](/media/d2c/homepage/Question-answering.svg)

### Support

Access technical support and operational assistance.

[Get support ↗](https://support.molo17.com)

Status ![](/media/d2c/homepage/Event--incident.svg)

### Service Status

Real-time platform availability and incident history.

[Check status ↗](https://status.molo17.com)

## Operate Gluesync from your MCP client

Use the embedded server with the same bearer identity and Control Plane permissions as the Web UI.

[Request a free trial](/get-gluesync/) [Talk to our team](/contacts/?topic=data-architecture) [Docs](https://docs.molo17.com/gluesync/latest/gs-modules/corehub-mcp.html)
