Connectors · Claude

Your product OS,
in Claude.

Add FishLadder to Claude once, then ask about your roadmap, tasks, customers, feedback, and wiki in plain language. No terminal, no API keys. Sign-in is OAuth, and Claude never receives a password.

Start Free Trial → Setup guide
Works in claude.ai, Claude Desktop, and Claude Code
Is anyone already working on SSO?
searched tasks checked customer feedback looked for a spec in the wiki
Yes. Sarah has “SSO via SAML” in progress on the auth board, due next sprint. Twelve customers have asked for it this quarter, mostly enterprise trials, and there's a draft spec in the wiki: Enterprise SSO. Want a summary of the spec?

One question, three lookups nobody asked for by name. Claude chains FishLadder's tools to actually answer, not just search.

Capabilities

22 tools. 8 of them write.

Claude reads broadly across your workspace and makes a small, deliberate set of changes. Every change is confirmed with you before it runs.

Reads & teams
14 tools
Ask about anything you can see in the app.
  • Roadmap projects and status
  • Tracker boards and tasks, searchable by text, project, assignee, and priority
  • Team members and who's working on what
  • CRM companies, contacts, and deals
  • Customer feedback, summarizable by theme or time period
  • Wiki spaces, page search, and full page text
  • Who you're signed in as, which teams you belong to, and which team Claude is reading from
  • Switch teams mid-conversation, no reconnecting
Writes
8 tools
Each one confirmed by Claude before it runs.
  • Create a task, with assignee, priority, and due date
  • Update a task: change status, mark complete or reopen, edit details
  • Create a wiki page, and edit an existing one
  • Add a company or a person to the CRM, and update their details
Nothing can be deleted through the connector.
Try asking

Questions that just work.

No syntax to learn. If you'd ask a teammate, you can ask Claude.

What's on the roadmap 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 about onboarding this month.
How does our incident escalation process work?
Add Globex to the CRM, with Sarah Chen as the contact.
Permissions

Access follows the person,
not the tool.

FishLadder gates on your role (viewer, member, admin) and the modules you've been granted. Both are enforced identically wherever you sign in from, so Claude cannot do anything you couldn't do yourself in the app.

viewer
A viewer is offered no write tools at all. Not shown-then-refused: not offered.
module access
Someone without CRM access has no CRM tools, and can't reach CRM data by rephrasing.
member
A member can do through Claude exactly what they can do in the browser. No more.
team scope
Every request is scoped to a single team. Ask Claude which one it's reading from, or ask it to switch.

This isn't a policy we're asking you to take on trust. Permissions are resolved per request from the same function the web app uses, and an automated check signs in as a viewer, a partially-provisioned member, and an admin against the live server before every release.

Built carefully

Designed to be trusted with your data.

The connector is conservative by design. A few behaviors worth knowing about:

🔍
Duplicates are reported, not created
Adding a company whose domain already exists returns “Acme is already in the CRM” instead of a second record that splits deals and history across two entries.
📄
Wiki edits keep history
Claude reads a page before editing it, and the previous version is kept in page history where it can be compared or rolled back in the app.
✋
Claude asks before each change
Every write is confirmed with you first. You'll see a permission prompt the first time each tool is used. That's a feature.
Setup

Connected in about a minute.

One URL, one sign-in. The same connector works in claude.ai, Claude Desktop, and Claude Code.

Full walkthrough in the help docs: setting up the connector and what it can do.

Good to know: a connection reads one team at a time. If you belong to several, Claude can list your teams, say which one it's reading from, and switch to another when you ask, right in the conversation.

1
Add the connector
In claude.ai: Settings → Connectors → Add custom connector, then paste https://app.ladder.fish/api/mcp
2
Leave the advanced OAuth fields empty
No client IDs, no keys to paste. FishLadder handles sign-in itself.
3
Sign in with your FishLadder account
A browser window opens, you approve, and you're connected. Claude never receives a password.
Prefer a terminal?

The connector talks.
The CLI scripts.

The connector is for asking about your work in plain language. The CLI is for developers and automation: scriptable, terminal-based, with JSON output that pipes anywhere. They share a permission model and almost nothing else.

See CLI docs → API reference
›npm install -g fishladder
›fish login
✓ authenticated · workspace: acme-corp
›fish tasks create "Fix auth bug @sarah !high due:fri"
✓ created · synced to Linear
›fish feedback analyze --format json < q3-interviews.txt | jq
↳ 3 themes · top: auth friction (14 mentions)

Ask your first question
five minutes from now.

14-day free trial · No credit card required · Connector included on every plan

Start Free Trial → Read the setup guide