Custom HTTP & MCP Integrations

GLUCOSE ships with a library of pre-built enterprise connectors. Now you can extend that reach yourself. Custom HTTP & MCP integrations let your team connect GLUCOSE to the systems that matter to you — even the ones we’ve never heard of — without waiting on a connector to be built for you.

Custom HTTP integrations turn any REST or webhook-style endpoint into a tool an Experience Agent can call. Point it at your API, describe what it does and the inputs it expects, set your authentication, and the agent can reach it mid-conversation — pulling live data or triggering an action in your own stack.

MCP integrations go a step further. Register an external MCP server and GLUCOSE discovers the tools it exposes automatically, so every capability on that server becomes available to your agents without wiring each one by hand. As the server grows, your agents keep up.

Both live in the same Tools & Connectors layer as everything else — governed by the same guardrails, versioned with the rest of your configuration, and callable from any agent, on any channel.

What’s new

• Bring your own HTTP endpoints — turn any REST or webhook API into an agent-callable tool by describing its inputs, response, and authentication.
• Connect external MCP servers — register an MCP server and GLUCOSE auto-discovers the tools it exposes, no per-tool wiring required.
• No connector backlog — reach the systems you need today instead of waiting for a pre-built connector.
• Live data and actions — agents can fetch real-time information or trigger operations in your own stack mid-conversation.
• Governed like everything else — custom integrations run under the same guardrails and version control as native connectors.
• Available everywhere — call your custom tools from any Experience Agent, across every channel.

Also new: a reorganized GMC sidebar

We’ve completely reorganized the Management Console sidebar so it reflects the scope of each resource at a glance. Navigation is now grouped by whether a resource is organization-wide — shared across your whole account — or environment-wide — scoped to a single environment. No more guessing where a setting lives or which environments a change will affect.

• Scope-aware navigation — organization-wide and environment-wide resources are now clearly separated, so it’s obvious what each change touches.
• Faster to find things — resources are grouped by scope instead of scattered, cutting down the hunt for the setting you need.
• Fewer cross-environment mistakes — you can tell whether you’re editing something account-wide or environment-specific before you click.

This is just the start. Agent-to-Agent (A2A) support is on the way — so your agents will soon coordinate with other agents in your stack as naturally as they call tools today.