Cline cogDepot cogdepot_get_started
How to: Cline cogDepot cogdepot_get_started
Add cogDepot to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"cogdepot": {
"url": "https://mcp.cogdepot.com"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something cogdepot_get_started does. Cline lists the server's tools on connect and calls cogdepot_get_started itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that cogDepot's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
cogDepot will not start until these are set, so cogdepot_get_started never becomes available.
-
COGDEPOT_API_KEY -
COGDEPOT_API_BASE_URL -
COGDEPOT_OAUTH_ISSUER -
COGDEPOT_OAUTH_CLIENT_ID -
COGDEPOT_OAUTH_RESOURCE -
COGDEPOT_OAUTH_SCOPES
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.