General Tools
olai.com
Provides company information, services, pricing, locations, and FAQs for Olai Interactive.
ENDPOINT 1
https://olai.com/api/mcp/mcp
MCP server metadata
- Name
- olai-mcp
- Version
- 1.0.0
Known tools 7
get_company_infoLiefert Basis-Informationen über Olai Interactive: Standorte, Schwerpunkte, Gründungsjahr, Kontakt.
Inferred read-onlyget_servicesListet alle Services von Olai mit Beschreibung, URL, typischer Dauer und Preisrange.
Inferred read-onlyget_pricing_modelsLiefert die drei Wege, wie Olai mit Kunden zusammenarbeitet: Standard-Projekt, Partnerschaftliche Entwicklung, Enge Partnerschaft.
Inferred read-onlyget_locationsLiefert die Standorte und Service-Regionen von Olai: Solothurn (HQ), Basel, Zürich.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.olai-mcp]
url = "https://olai.com/api/mcp/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"olai-mcp": {
"type": "http",
"url": "https://olai.com/api/mcp/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: olai-mcp
Remote MCP URL: https://olai.com/api/mcp/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"olai-mcp": {
"url": "https://olai.com/api/mcp/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"olai-mcp": {
"type": "http",
"url": "https://olai.com/api/mcp/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "olai-mcp",
"transport": "streamable-http",
"url": "https://olai.com/api/mcp/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for olai.com was fetched 2026-08-03T18:07:25.179Z and is being refreshed.
olai.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.