Catch Log — fishing logbook with an MCP endpoint

app.rowb.catchlogv1.0.0Updated Sep 30, 2026

A fishing catch logbook: record catches with date, location, species and conditions via MCP.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant record and look up fishing catches — date, location, species and conditions — in a hosted catch logbook.

What it does
Catch Log is a remote MCP endpoint for a fishing catch logbook. According to the registry description, it lets an assistant record catches with date, location, species and conditions. The manifest does not list individual tools, so the exact set of operations is not documented here.
When to use it
Worth adding if you keep a fishing log and want an assistant to file catches as you report them, or to look back at where and when you caught something. Not useful if you do not track catches.
Requirements
A remote streamable HTTP endpoint; nothing runs locally. It requires an Authorization header carrying a Bearer API key. A free key is offered at signup with a 50 calls per month limit and no card required.
Before you install
The Authorization header holds a secret API key; keep it out of shared logs and transcripts. The free tier is capped at 50 calls per month, and the service is third-party hosted, so catch details you submit are stored on the provider's servers.

Installation

In SourceWeft

  1. Open Catch Log — fishing logbook with an MCP endpoint in the dashboard and add it to a workspace.
  2. 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": {
    "logbook": {
      "type": "http",
      "url": "https://catchlog.rowb.app/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 30, 2026