
RidgeHQAPP
app.ridgehqv1.0.1Updated Oct 1, 2026
Trip, roster, client and session tools for dive and watersports operators, scoped to one tenant.
Overview
AI-generated overview
Lets an assistant read and manage dive and watersports operator data — trips, rosters, clients and sessions — within one tenant.
- What it does
- A remote MCP server for dive and watersports operators. It exposes tools covering trips, rosters, clients and sessions, scoped to a single tenant. The registry description does not list individual tool names or operations, so the exact read and write actions are not documented here.
- When to use it
- Worth adding when an assistant needs to work with a dive or watersports operator's scheduling and customer records — for example looking up trips, rosters, clients or sessions — rather than general-purpose tasks.
- Requirements
- A remote streamable HTTP endpoint at Authentication is required: an Authorization header carrying a Bearer token, either a RidgeHQAPP personal access token or an OAuth 2.1 access token from RidgeHQAPP's authorization server. No local runtime or packages are needed.
Before you install
The Authorization header is a required secret; treat the token as sensitive and avoid exposing it. The server is tenant-scoped, so it only reaches one operator's data. The description does not state which tools write, change or delete records, so confirm that before granting access.
Installation
In SourceWeft
- Open RidgeHQAPP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://api.ridgehq.app/mcp"
}
}
}README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.1LatestOct 1, 2026

