lc.cx

@lc.cx create a short link for our new product landing page at https://example.com/products/widget-pro with the tag 'launch-2024'

Created short link: lc.cx/widget-pro pointing to https://example.com/products/widget-pro. Tagged with 'launch-2024'. This link is now live and will be tracked in your workspace analytics. Monthly quota: 48 of 50 links remaining.

Each successful creation permanently consumes one unit from your monthly quota, even if you later delete the link. The MCP requires API_KEY authentication and workspace selection. Choose your path carefully — short links cannot be edited after creation, only deleted.

@lc.cx list all short links tagged 'campaign-q1' from the last 30 days so I can see what's still active

Found 7 short links tagged 'campaign-q1': lc.cx/promo-jan (→ blog post, 342 clicks), lc.cx/webinar-reg (→ registration form, 89 clicks), lc.cx/case-study (→ PDF, 156 clicks), lc.cx/demo-signup (→ calendar, 201 clicks), and 3 others. All created between Jan 3–28. Use offset parameter to retrieve additional pages if more than 20 results exist.

List operations return paginated results showing destination URLs, click counts, and metadata. This read-only query does not consume quota. Filtering by tag requires the tag to exist in your workspace — create tags first if organizing a new campaign.

@lc.cx check my account quota and summarize which workspaces have the most links so I know where to consolidate before month-end

Current plan: Pro (50 links/month). Quota used: 43 of 50 (7 remaining). Workspace breakdown: 'Marketing' has 28 active links, 'Sales' has 11, 'Support' has 4. You're approaching your monthly limit — consider archiving unused links or upgrading before creating more. Note that deleting links does not restore quota for the current billing period.

The account context tool reveals plan limits and workspace distribution, helping teams avoid quota exhaustion mid-campaign. Pair this with list operations to identify low-traffic links worth deleting. Quota resets monthly but deletions never refund consumed units within the same period.

When lc.cx wins for multi-channel attribution at small scale

A 3-person growth team running paid ads, email, and social needs to track which channels drive signups without paying for a full marketing ops stack. This MCP is the right call if you're creating under 100 links per month and need workspace-level tagging to separate campaigns. Use the Create Short Link tool with tags for channel and campaign name, then pull List Short Links during weekly standups to see which variants performed. The quota constraint matters: each link creation burns a unit permanently, so this works for deliberate campaign URLs but breaks down if you're auto-generating links for every blog post or support article. If your team is creating more than 200 links monthly or needs click analytics beyond basic counts, you've outgrown this MCP and should move to a dedicated link management platform. For small teams running 4-8 campaigns concurrently, lc.cx keeps attribution simple without vendor lock-in.

When this MCP handles personalized demo links for sales teams

A 6-person sales team sends personalized demo environment links to prospects and needs to track which accounts clicked through without manually logging into a link shortener. This MCP works if you're onboarding 20-40 new prospects monthly and want to tag links by account tier or sales rep. Use Create Short Link with the prospect's company name in the note field and a tag for the rep, then query Get Short Link during pipeline reviews to confirm engagement. The workspace feature lets you separate trial links from customer success links without mixing analytics. The boundary: if you need to programmatically generate links for every email send or integrate click data into your CRM, this MCP's 10-tool scope won't cover webhook setup or bulk operations. For teams where a human creates each link intentionally and checks status in Switchy during deal reviews, lc.cx keeps the workflow in one place without paying for enterprise link management.

When lc.cx simplifies wiki link rot for remote teams

A 12-person remote engineering team maintains an internal wiki with links to staging environments, runbooks, and vendor dashboards that change URLs every quarter. This MCP is borderline but works if you're managing under 50 internal shortcuts and need a single source of truth that non-technical teammates can update. Use Create Short Link to mint stable lc.cx URLs for each critical resource, tag them by system or team, then update the destination when infrastructure changes without breaking wiki references. The List Tags and List Short Links tools let anyone audit what's live during quarterly doc reviews. The trade-off: you're burning quota on internal links that could go to customer-facing campaigns, and there's no bulk update tool if you need to migrate 30 links at once. If your wiki has more than 100 external references or changes URLs weekly, a dedicated redirect service or DNS-based solution scales better. For small teams with stable-ish infrastructure and occasional URL churn, this keeps documentation accurate without engineering overhead.