Gluesync Enterprise Brain · Connect
Claude, ChatGPT, Grok, Meta Muse, Hermes Agent, OpenClaw, Cursor: they all speak the Model Context Protocol, and Gluesync Core Hub is an MCP server. Point them at your Core Hub and they get immediate answers based on company shared knowledge, with the permissions of the person asking.
How it works
Endpoint
Core Hub mounts Streamable HTTP at /mcp/http and SSE at /mcp beside its REST API. There is no sidecar to deploy and nothing to sync to a vendor cloud.
Identity
Each client authenticates with a session token or a Personal API Token. Every tool call runs under that user's Core Hub RBAC, so an AI-shaped path around your permissions does not exist.
Answer
Clients call list_published_agents, start_agent_run, and get_agent_run to hand a question to an immutable Spark agent version, or search_enterprise_brain to look up the tables and procedures directly.
Capabilities
The AI agents category of the Core Hub MCP server is how external tools reach the brain. Runs execute as the caller, results carry the skills they produced, and nothing returns row data unless the caller could already read it.
Ask
Search the schema graph and the memories visible to the caller. Returns tables, columns, and procedures: the route to an answer, not the answer's rows.
Delegate
Hand a question to a published Spark agent and read back a durable, redacted result with the skills it used or created.
Contribute
Let a client discover which agents exist and, with the right scope, publish a procedure as a reusable skill the whole company can call.
FAQ
Any client that implements the Model Context Protocol over Streamable HTTP or SSE. Claude Desktop and Claude Code, ChatGPT connectors and the OpenAI Agents SDK, Grok bots, Meta Muse, Hermes Agent, OpenClaw, Cursor, Windsurf, and MCP Inspector all qualify. The in-product Spark agents use the same brain natively.
No. The client sends a Core Hub token, and every call runs with that token's role and Query Studio data-access rules. A bot configured by a viewer sees what a viewer sees.
Only through tools its token is allowed to use, and only after a signed-in approval for writes proposed by a published agent. Read-only deployments can hide every write tool with a single setting.
Only what the agent puts in its prompt: the question, up to eight memory lines, up to eight schema-graph lines, and tool results the caller could read anyway. Provider credentials live in your own vault, and you can route to a local model.
Enterprise brain
The foundation for every AI tool your company uses, built on the databases Gluesync already integrates.
Explore → Extend Skills and company toolsAgents publish the procedures they discover as skills, and approved MCP servers such as GitLab or Notion become tool bundles you govern.
Explore → Own Ownership and privacyA dedicated brain database on your infrastructure, memory shared by default and private on request, never rows, never secrets, never SaaS.
Explore →Gluesync Enterprise Brain
One endpoint, one token, one brain. Bring Claude, ChatGPT, Grok, Meta Muse, or your own agent framework, and keep every answer under your Core Hub permissions.
