01 / Sidecars
Extra MCP proxies
Extra MCP proxies mean another process to secure and upgrade.
Gluesync Module
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.
Why Core Hub MCP
01 / Sidecars
Extra MCP proxies mean another process to secure and upgrade.
02 / Privilege drift
Agent credentials that bypass Control Plane roles break audit.
03 / Outcome
Point Claude, Cursor, MCP Inspector, or any MCP client at Core Hub and keep the same permissions as the UI.
How it works
Embed
corehub-mcp mounts /mcp (SSE) and /mcp/http (streamable HTTP) beside REST.
Authenticate
Bearer session JWT or Personal API Token (gsp_…); zero elevated privileges in the module; loopback REST into Core Hub.
Act
125 built-in tools in Gluesync 2.3 (Beta) plus optional per-session Query Studio database tools when enabled.
Capabilities
The Gluesync 2.3 (Beta) catalog is 125 built-in tools (73 read and 52 write), including Chronos schedules, Core Hub webhooks, email notifications, and the AI agents category that lets any MCP client start published Spark agents and search the Enterprise brain. Automator/Bootstrapper MCP remains a separate local/stdio path.
Built into Core Hub
Use one embedded server for Core Hub management, diagnostics, reporting, and data tasks.
MCP connectivity
Connect a compatible client through SSE at /mcp or streamable HTTP at /mcp/http.
Control Plane security
The module adds zero elevated privileges and routes operations back into Core Hub under the authenticated caller.
Explore the platform
Core Hub MCP complements AI data supply and Query Studio. Query Forge remains the separate federated JDBC path.
Keep AI-facing stores current and expose Core Hub operations under the caller's permissions.
Explore AI & RAG →Give every MCP client one shared schema graph, agent memory, skills, and approved company tools, under the caller's permissions.
Explore Enterprise brain →Inspect schemas, run SQL, and provide optional per-session database tools to MCP clients.
Explore Query Studio →Run federated SQL across isolated agents through a dedicated JDBC gateway.
Explore Query Forge →Resources
Technical guides, API reference, deployment tutorials.
Read documentation ↗What we're building next. Submit feature requests.
View roadmap ↗Access technical support and operational assistance.
Get support ↗Real-time platform availability and incident history.
Check status ↗Use the embedded server with the same bearer identity and Control Plane permissions as the Web UI.