Glean added six remote Model Context Protocol (MCP) server templates to its enterprise AI platform on October 1, extending the range of business systems that can be accessed through Glean Assistant and Glean Agents.
The new templates connect Glean with GIS Cloud, Lightrun, MYOB, PaidSync, Avoma and Prisma Postgres. Glean listed the additions in its October 1, 2026 release notes, where it described them as remote MCP server templates rather than native Glean connectors.
Most of the newly added servers use per-user OAuth authentication, according to the release notes. Administrators select which MCP servers to add and enable through Glean’s MCP server directory.
The additions cover a wide range of enterprise tasks. GIS Cloud provides access to maps and spatial data, Lightrun exposes live application runtime information, MYOB provides financial information, PaidSync connects advertising operations, Avoma brings meeting intelligence into the agent environment, and Prisma Postgres provides database and infrastructure management capabilities.
Six different types of enterprise work
GIS Cloud’s MCP integration can expose maps, layers, features, tables, forms, queries and files. Its documentation says users can authorize read-only or read/write access, while destructive operations require confirmation. L
Lightrun takes a different approach by connecting agents to live software runtime information. Its MCP server can provide expression values, call stacks, execution timing and code metrics from running applications.
MYOB’s integration is more limited. The accounting software maker says its MCP connection is currently in beta and read-only, with availability restricted to invited users in Australia. It can provide information such as revenue, profit, expenses, receivables, overdue invoices and cash position, while payroll, inventory, tax lodgement and changes to MYOB records are outside the current implementation.
PaidSync adds advertising operations to the mix. Its platform supports advertising analysis and management across multiple advertising and measurement services, including campaign and budget operations. PaidSync’s documentation describes MCP use cases that include retrieving advertising performance and carrying out actions such as pausing campaigns or changing budgets, with some operations using previews or confirmation steps.
Avoma gives agents access to meeting-generated information. Its MCP platform can retrieve meeting transcripts, notes, action items and scorecard information, while selected write operations can update meeting metadata such as purpose, outcomes and privacy settings.
Prisma Postgres provides access to databases and related infrastructure. Prisma’s MCP server supports operations including database inspection, SQL execution, backups, connection-string management and Compute deployment management. Prisma warns that some operations can delete resources, cause data loss or disrupt live traffic.
Glean’s MCP directory is expanding rapidly
The six additions were part of a much larger expansion. Glean’s release notes show 182 MCP templates added on September 22, another 25 on September 24 and 67 on September 29, followed by the six announced on October 1. That represents 280 additions across four releases in nine days.
Glean has also been positioning MCP as a governed way to connect agents to external tools. Its MCP administration documentation says Glean acts as an MCP host, allowing administrators to control which remote servers and tools are available to employees. The platform can expose those tools through Glean Assistant and Glean Agents.
The approach differs from a conventional chatbot integration because MCP tools can provide executable functions as well as access to information. The result is a setup in which an agent can retrieve information from an external system and, where permissions allow, invoke actions in that system.
That distinction is visible in the six new templates. Some are primarily information-oriented, such as MYOB’s current read-only financial access, while others expose operational functions that can affect campaigns, meeting settings, databases or geographic data.
Agent identity is being added alongside tool access
Glean’s October 1 release also made Agent Identity generally available. The feature gives agents their own governed accounts in connected systems rather than requiring them to operate through an employee’s identity.
Glean has described the model as a way to provide agents with scoped credentials and an audit trail for automated activity.
The combination of MCP access and separate agent identities addresses different parts of the same enterprise deployment problem: MCP provides a standardized way for AI systems to reach tools, while identity and permission controls determine which tools an agent can use and under whose credentials those actions occur.
Glean’s broader MCP work has also included an MCP Gateway, which the company introduced as a layer for enterprise context, authentication, permissions, administration and monitoring around MCP connections.
Glean has cautioned that MCP itself does not solve enterprise security concerns. Its guidance highlights issues including excessive permissions, malicious or unsafe tools, prompt injection and unreliable agent behavior, and recommends limiting permissions and available tools to what an agent actually needs.
Glean’s October release notes also distinguish between remote MCP servers supported directly in Glean and MCP server support inside agents, which the documentation currently identifies as being in beta.
Discover more from Aree Blog
Subscribe now to keep reading and get access to the full archive.
