Using Fishladder in Claude

Once the connector is added, ask Claude questions in plain language. You do not need to name tools or IDs — Claude works out which lookups to run. Mention Fishladder by name when a question could apply to something else ("what's in our Fishladder roadmap this quarter?").

Things to ask

• "What's on the roadmap for this quarter, and what's slipping?"
• "What is Priya working on right now?"
• "Any open tasks on the billing board that mention webhooks?"
• "Summarise the feedback we've had about onboarding this month."
• "Which deals are open and over $50k?"
• "What's due for Acme in the next 30 days?" (tasks and project target dates)
• "Which deals close or quotes expire this month?"
• "How does our incident escalation process work?" (reads River docs)
• "Create a task on the Platform board to add rate limiting, assigned to me."

Claude is good at chaining these. Asking "is anyone already working on SSO?" will typically have it search tasks, check feedback, and look for a spec in River before answering.

What the connector can reach

The full list of tools, with their inputs, is in the MCP tool reference.

Reading

Writing

• Create a task on a tracker board, with an optional assignee, priority, and due date.
• Update a task — change its status, move it between columns, mark it complete or reopen it, or edit the title, description, assignee, priority, or due date. Only the fields you mention change.
• Create a wiki page in a River space, optionally under a parent page. Claude reports where it landed (space and parent pages).
• Move a wiki page to another space or under another page; its child pages move with it.
• Link a wiki page to a task (or a board, roadmap project, CRM record, quote, job or candidate) so the page shows up on it. You need access to the part of Fishladder the record lives in, and the link carries the record's real name.
• Add a Google Drive file to a task's Google Drive section, and list the files already there.
• Link a HubSpot company or contact to a task, a board, a roadmap project or a wiki page, list what's linked, and unlink it. Linking a company to a board makes every task on it that client's — which is what Slack channel alerts use. Nothing is changed in HubSpot.
• Edit a wiki page — change its title or rewrite its body. The previous version is kept in the page history, so an edit can always be compared or rolled back in the app. If someone else edited the page while Claude was working, the edit is refused instead of overwriting their changes, and Claude re-reads before trying again.
• Comment on a wiki page — anchor a comment to a specific passage, or suggest replacement wording, without changing the page. Both show up highlighted in the page's margin panel labeled "via Claude"; a suggestion is only applied when someone accepts it in Fishladder.
• Add a company or contact to the CRM, and update their details or lifecycle stage. If the company domain or contact email already exists, Claude tells you rather than creating a second record.

Everything else is read-only. Claude cannot delete anything, change deals, or move tasks between boards through the connector. It only sees boards in project groups you can open, and can only assign work to people who can open that board.

Editing a wiki page replaces the body rather than adding to it. Ask Claude to read the page first when you want a change to an existing document, so the rest of the page survives.

Permissions

The connector uses your own access, and matches what you can do in Fishladder itself.

• Members and admins can have Claude create and edit tasks and wiki pages. Changes appear in the app attributed to you.
• Viewers get read-only access. The editing tools are not offered to them at all.
• Modules you cannot open are invisible. If you do not have River, Claude has no wiki tools; if you do not have CRM, it cannot see companies or deals.

Because access is checked per team, and your role can differ between teams, the connector reflects whichever team you last had open in Fishladder.

A connection covers one team. If an answer looks wrong or empty when you expected data, ask Claude which teams you have — it can list them and name the one it is reading from. Reading the wrong team looks identical to that team being empty, so it is worth checking before concluding something is missing. To work on a different team, just ask Claude to switch to it by name. Opening it in Fishladder works too — the next answer follows, with nothing to reconnect.

Claude asks before making any change. You will see what it intends to do and can stop it.

Getting better answers

• Name the board or project when you know it. "On the Platform board…" is faster and more accurate than letting Claude search everything.
• Say what you want the answer for. "I'm writing a board update" produces a very different summary than the raw list.
• Ask it to check first. "Search first so we don't duplicate" before creating work.

Troubleshooting

"This account is not a member of any Fishladder team." Your account exists but has no team. Accept your invitation, or ask an admin to add you, then reconnect.

Claude is showing the wrong team's data. It follows whichever team you most recently had open in the Fishladder web app. Open the team you want there, then ask again — no need to reconnect. Every answer names the team it searched, so you can confirm it switched.

The task-creation tool is missing. It is not offered to viewers. Ask a team admin to make you a member, then reconnect.

The connector fails to add. Check the URL is exactly https://app.ladder.fish/api/mcp, with no trailing slash, and leave the advanced OAuth fields empty.

Claude says it is being rate limited. Each team can make 600 connector requests per minute. This is generous for normal use; if you are hitting it, several people or automations are likely sharing one very busy team. Wait a moment and retry.

Other ways to connect

The same URL works in Claude Desktop and Claude Code. For scripting and CI, use the Fishladder CLI and API keys instead.