Bring Enterprise Search
to Claude Desktop
Learn how to connect Glean to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Glean MCP Server?
Connect your Glean workspace to any AI agent and unlock enterprise knowledge through natural conversation.
What you can do
- Universal Search — Search across all connected data sources (Confluence, Slack, Google Drive, Jira, and more) from a single query
- Datasource Filtering — Focus searches on a specific connected platform for targeted results
- People Search — Find employees by name, role, expertise, or department across your organization
- Document Management — Index new documents, bulk-index batches, retrieve document metadata, and remove outdated content
- Curated Collections — Browse and inspect curated content collections for onboarding, policies, and shared knowledge
- AI Chat — Ask questions to Glean's AI assistant, which generates answers grounded in your organization's knowledge base
- Autocomplete — Get intelligent search suggestions based on organizational knowledge as you type
How it works
1. Subscribe to this server
2. Enter your Glean API Token from the Admin Console
3. Start searching your enterprise knowledge from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Knowledge Workers — find answers across Confluence, Slack, Drive, and Jira without switching between tools
- IT Administrators — index custom documents and manage curated collections programmatically
- Engineering Teams — search codebases, wikis, and design docs through a single conversational interface
Built-in capabilities (12)
Autocomplete suggestions
Bulk index documents
AI chat
Verify connectivity
Delete a document
Get collection details
Get document details
Index a document
List collections
Search across all content
g., Confluence, Slack, Google Drive). Search in specific datasource
Search people
Why Claude Desktop?
Claude Desktop is the definitive way to connect Glean to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Glean in Claude Desktop
Glean and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Glean to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Glean in Claude Desktop
The Glean MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Glean for Claude Desktop
Every tool call from Claude Desktop to the Glean MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search across multiple data sources like Confluence, Slack, and Google Drive simultaneously?
Yes! The search tool queries all connected data sources in a single request. If you want to narrow results to a specific platform, use search_by_datasource with the datasource name (e.g., 'Confluence', 'Slack', 'Google Drive'). Use autocomplete to get intelligent suggestions as you refine your query.
Can I ask the Glean AI assistant questions about my organization's knowledge?
Yes. The chat tool sends a natural language question to Glean's AI assistant, which generates an answer grounded in your organization's indexed knowledge — including documents, wikis, Slack conversations, and Jira tickets. This is ideal for getting synthesized answers rather than just search results.
Can I index custom documents into Glean programmatically?
Yes. Use index_document to add a single document with a JSON payload containing title, body, URL, and metadata. For large batches, use bulk_index_documents to index multiple documents in one request. Use delete_document to remove outdated content and get_document to verify indexing status.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.