HN Showcase
Back to browse
Crossbeam-CLI – Connect Claude to Crossbeam without the enterprise tier

Crossbeam-CLI – Connect Claude to Crossbeam without the enterprise tier

by ryanhughes·Jun 29, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●MidShip It

Free Crossbeam API access when the official connector costs $4,800/year.

Strengths
  • •Dual interface serves both technical users (CLI) and sales teams (Claude extension).
  • •Credentials stay local—session cached on user's disk, never sent elsewhere.
  • •41 read tools exposed via MCP for natural-language partner data queries.
Weaknesses
  • •Relies on undocumented endpoints that Crossbeam could change or block anytime.
  • •Read-only access; no write support for updating partner records or mappings.
Target Audience

Sales teams, partner managers using Crossbeam without enterprise plans

Similar To

Crossbeam official API · Crossbeam Claude connector

Post Description

I built crossbeam-cli, an open-source tool that connects Claude to Crossbeam so you can ask questions about your partners, overlaps, and account mapping in plain English.

Crossbeam gates programmatic access behind its top Supernode tier. Even the official Claude connector starts around $4,800/year.

crossbeam-cli works on any plan, free tier included, because it talks to the same internal API the web app uses. You log in with your own credentials and requests go straight from your computer to Crossbeam.

It ships two ways: a one-click Claude desktop extension (MCPB) for non-technical partner teams, and a CLI (npm i -g crossbeam-cli) for scripting and agents.

So far I've only implemented read-only tools, but I could add write support in the future.

It's unofficial and not affiliated with or endorsed by Crossbeam. It relies on undocumented endpoints, so they could change or break it at any time.

Would love to hear what you all think.

https://fan-pier-labs.github.io/crossbeam-cli/

Similar Projects

Infrastructure●●Solid

Bifrost: Fastest enterprise AI gateway

Bifrost combines an OpenAI-compatible front door with adaptive load balancing, semantic caching, automatic failover, cluster mode and a built-in web UI — you can spin it up with npx or Docker in seconds. The performance claims (sub-100µs overhead at 5k RPS, '50x faster than LiteLLM') and multi-provider routing are the project's selling points; I want to see independent benchmarks and deeper docs on guardrails/provider quirks before trusting it for critical workloads.

WizardrySolve My ProblemSlick
aanthonymax
104mo ago