Elaichi
Server Details
Governed AI agents for the software your company already runs. 400+ connectors behind one org-wide endpoint, where every call resolves against the current role of the person the agent acts for, not against the connection. Works with Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 52 tools
The resource-prefixed names make most tools easy to separate, and the descriptions are unusually explicit about boundaries. The main confusion risk is the cluster of tool-listing/execution surfaces: connection.list_tools, connector.list_tools, search_tools, toolbox.execute, and synthetic_tool.execute overlap enough to cause occasional misselection. Overall mostly distinct, with a few near-overlapping pairs.
The dominant pattern is clear and consistent: elaichi__<resource>__<verb> in snake_case. The two unprefixed tools, execute_tool and search_tools, break the pattern, and a few names like offboarding and set_roles deviate from strict verb phrasing. Still predictable and readable overall.
52 tools is well above the calibration threshold for 'too many' even for a broad administration platform. Each resource area has several CRUD-style operations, but the total feels heavy for a single MCP surface. The count will make tool selection and navigation burdensome.
Many lifecycle operations that the tool descriptions themselves reference are not exposed: deletions, unsharing, role create/update/delete, member delete, invite delete/resend, team remove_member/delete, and transfer operations. These missing operations create dead ends during common governance workflows. Core read/create/update paths exist, but the surface is significantly incomplete relative to its own described domain.
Publisher details
- Operator
- Elaichi · Publisher source
- Operator website
- https://elaichi.ai
- Vendor relationship
- First-party
- Documentation
- https://elaichi.ai/docs/
- Privacy policy
- Not provided
- Trust center
- https://trust.elaichi.ai
- Restrictions
- Paid plan after a 14-day free trial (no credit card to start). Adding the endpoint to Claude Team or Enterprise requires an Owner. · Publisher source
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.