Developers
Glean and other AI tools
Connect Glean, Claude and other AI platforms to TINIUN through the OpenAPI description, OAuth or the MCP server.
Three ways to connect
| Option | Use when | Credentials |
|---|---|---|
| MCP server | The platform can add a remote MCP server (Claude, Cursor and a growing list of others) | OAuth, approved by each person |
| OpenAPI tool or action | The platform can import an OpenAPI description and call it (many agent builders and enterprise search tools) | An API key with only the scopes it needs, or OAuth if the platform supports an authorization-code flow |
| Webhooks | You want TINIUN to push events into a workflow or index | Signing secret |
The OpenAPI description is at https://tiniun.com/api/v1/openapi.json; the MCP endpoint is https://tiniun.com/api/mcp.
Glean
Glean can call external systems through actions or tools defined from an API description, and, where your Glean deployment supports it, through remote MCP servers. To let Glean’s assistant answer workforce questions from TINIUN:
Pick scopes
Create an API key under Settings → Integrations → API keys with only what the assistant needs, for examplepeople:read,status:readandschedules:read, and the shortest expiry you can live with.Add the tool in Glean
In Glean’s admin or agent builder, add a custom action or tool from the OpenAPI URL above, with bearer-token authentication using that key. If your Glean supports remote MCP servers, addhttps://tiniun.com/api/mcpinstead.Test with one question
Ask something only TINIUN can answer, such as who is on break right now, and compare with the Team Floor.
Not verified against a Glean tenant
Indexing TINIUN content as a Glean data source is not provided out of the box. The API and webhooks could feed a custom data-source connector, which you would build and run.
Other AI platforms
Any platform that can send an HTTP request with a bearer token, import OpenAPI, or speak MCP can use TINIUN. Examples of what people ask for: a daily Slack summary of open exceptions (a webhook on exception.created into your automation tool), a copilot that explains yesterday’s adherence (the adherence:read scope), or an assistant that logs calls from your phone system (interactions:write).
Guidance
- Give each integration its own key or OAuth application so you can see and revoke it separately.
- Grant read scopes unless the integration must write.
interactions:writeis the only write scope. - Data you send to a third-party AI platform is governed by your agreement with that platform. Check it covers employee data.
See it with your own scenarios
A 30-minute walkthrough with our team, tailored to your operation.
Book a demo
