otherapi_key

L2s

L2S is a professional URL shortener offering advanced analytics, QR code generation, and team collaboration features.

Verdict

The L2s MCP lets your team create, manage, and inspect shortened URLs without leaving Switchy. @Mention it to turn long links into compact versions, retrieve metadata about existing short links, or audit all URLs tied to your account. Useful for marketing teams tracking campaign links, support agents sharing cleaner resources, or anyone who needs quick link shortening mid-conversation. Requires an API key from L2s, which means one account handles all shortening — team members can't scope links to individual profiles.

Common use cases

  • Shorten campaign URLs during launch planning
  • Audit all active short links in one query
  • Retrieve click metadata for a specific link
  • Generate clean URLs for customer-facing docs
  • Check user settings before bulk shortening

Integration

Vendor
L2s
Category
other
Auth
API_KEY
Tools
4
Composio slug
l2s

Tools

  • Get URL Details

    Tool to retrieve details of a shortened url. use when you need metadata about a specific shortened link. use after obtaining a valid url id.

  • Get User Settings

    Tool to retrieve current user's settings. use after authentication to fetch email, notification, and appearance preferences.

  • List Shortened URLs

    Tool to list all shortened urls. use after user authentication to retrieve the user's urls with pagination details.

  • Shorten URL with L2S

    Tool to shorten a given long url. use when you need a concise link representation.

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Click 'Add MCP Server' and select L2s from the list. 3. Log into your L2s account at l2s.io and generate an API key from the developer or account settings page. 4. Paste the API key into the Switchy connection dialog and click 'Connect'. 5. Switchy will validate the key and confirm the connection. 6. Open any Space and type '@L2s shorten https://example.com/very/long/path' to test — the MCP should return a shortened URL. 7. Use '@L2s list shortened urls' to verify you can retrieve your account's links. All team members share the same L2s account credentials, so shortened URLs appear under one profile.

What teammates see: by default, memories from L2s are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List All Short URLs

@L2s list all shortened urls in my account, including creation dates and original targets
Open in a Space →

Batch Shorten for Docs

@L2s shorten these three URLs: https://docs.example.com/getting-started, https://docs.example.com/api-reference, https://docs.example.com/faq
Open in a Space →

Check Account Settings

@L2s retrieve my current user settings, including email, notification preferences, and appearance theme
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@L2s list all my shortened URLs from the last 30 days and show me which ones got the most clicks

Output

Retrieved 47 shortened URLs created in the last 30 days. Top performers: l2s.io/abc123 (1,204 clicks, created Jan 15, links to product launch page), l2s.io/xyz789 (892 clicks, created Jan 8, links to pricing calculator), l2s.io/def456 (673 clicks, created Jan 22, links to webinar registration). The remaining 44 links averaged 34 clicks each. All links remain active with no expiration set.

Notes

This example combines the List Shortened URLs tool with AI synthesis to surface insights from click data. Requires valid API key with read permissions. Note that L2s returns pagination metadata — if you have hundreds of links, the MCP may need multiple calls to fetch the full set before ranking by clicks.

Prompt

@L2s shorten this URL for our Q1 campaign: https://example.com/products/winter-sale-2024?utm_source=email&utm_campaign=q1promo and set a custom alias 'winter24'

Output

Created shortened URL: l2s.io/winter24 → https://example.com/products/winter-sale-2024?utm_source=email&utm_campaign=q1promo. The link is now active and will track clicks, referrers, and geographic data. Custom alias 'winter24' is reserved to your account. UTM parameters are preserved in the target URL, so your analytics will attribute traffic correctly.

Notes

This example uses the Shorten URL tool to create a branded short link with a memorable alias. The MCP writes to your L2s account, so the link persists beyond this session. If the alias is already taken (by you or globally, depending on L2s's namespace rules), the tool will return an error — handle this by trying a different alias or omitting it for an auto-generated ID.

Prompt

@L2s get the full details for l2s.io/abc123 including when it was created, how many times it's been clicked, and what the original long URL was

Output

Link l2s.io/abc123 was created on January 15, 2024 at 3:42 PM UTC. It has been clicked 1,204 times as of now. The target URL is https://example.com/products/launch-page-v2. Additional metadata: no expiration date set, click tracking enabled, last clicked 2 hours ago from a referrer in the US (Chrome on macOS). The link is currently active.

Notes

This example uses the Get URL Details tool to fetch metadata for a specific shortened link. You must provide a valid URL ID that exists in your L2s account — the MCP cannot retrieve details for links created by other users. Useful for auditing link performance or verifying target URLs before sharing them in campaigns.

Use-case deep-dives

Campaign link tracking for marketing teams

When L2s works for small-team UTM management

A 3-person growth team running paid ads across LinkedIn, Twitter, and email needs branded short links with click tracking. L2s wins here if you're generating fewer than 50 links per week and don't need complex analytics dashboards. The Shorten URL tool creates clean links in seconds, and List Shortened URLs lets the team audit what's live without opening a separate platform. The Get URL Details tool surfaces basic click metadata, which is enough for weekly campaign reviews. If you're running A/B tests with hundreds of variants or need funnel attribution beyond first click, you'll outgrow this fast. For teams who just want branded links and basic counts without paying for Bitly Enterprise, L2s keeps it simple.

Customer support ticket link sharing

Why L2s falls short for high-volume support workflows

A 6-person support team handling 200 tickets daily needs to share knowledge base articles, bug tracker links, and video walkthroughs with customers. L2s isn't the right call here. The 4-tool scope means no bulk shortening, no team-wide link libraries, and no integration with Zendesk or Intercom where the links actually get sent. You'd be manually shortening URLs one at a time in a separate AI workspace, then copy-pasting into your ticketing system. The Get User Settings tool is irrelevant to the workflow, and there's no way to tag links by product area or issue type. If your support flow already lives in a single platform with native link shortening, adding L2s just creates an extra step. Skip this unless you're a solo support rep who needs occasional branded links outside your main tool.

Internal documentation link cleanup

L2s as a one-time doc hygiene project

A product manager is migrating a 2-year-old Notion workspace to a new wiki and wants to replace 80+ ugly Jira and Figma URLs with clean short links before the team onboards. L2s works for this one-off batch job. Authenticate once with the API key, then use Shorten URL repeatedly in a single Switchy session to process the list. List Shortened URLs lets you export the new links for find-and-replace in the wiki. The catch: if your docs are living documents that accumulate new external links weekly, you'll need a more automated solution than manually shortening in an AI chat. This is a weekend project tool, not a continuous workflow. If you're shortening more than 20 links per month going forward, integrate a link shortener directly into your wiki or use a Zapier automation instead.

Frequently asked

What does the L2s MCP do in Switchy?

It connects Switchy to your L2s account so AI agents can shorten URLs, retrieve link metadata, and list your existing shortened links. Your team can ask the AI to create short links during conversations instead of switching to the L2s dashboard. Useful when you're drafting campaigns, sharing resources, or building reports that need trackable links.

Do I need an L2s API key to connect this MCP?

Yes. The L2s MCP uses API key authentication, so you'll need to generate one from your L2s account settings before connecting. Paste it into Switchy's connection flow. Anyone on your team with an L2s API key can connect their own account — no admin approval required from L2s.

Can the L2s MCP edit or delete existing shortened links?

No. The MCP can create new short links, retrieve details about existing ones, and list all your links, but it can't modify or delete them. If you need to update a link's destination or remove it entirely, you'll still need to do that directly in the L2s dashboard.

Why use the L2s MCP instead of just opening L2s in a browser tab?

The MCP lets AI agents create and look up short links mid-conversation without you leaving Switchy. If you're drafting a dozen social posts or compiling a resource list, the AI can generate all the short links inline. Faster than tab-switching, and the context stays in one place.

Who on my team should connect the L2s MCP?

Anyone who regularly creates or manages short links — typically marketing, social media, or content folks. Each person connects their own L2s API key, so link creation shows up under their L2s account. If your team shares one L2s login, one person can connect it and others can ask the AI to use it.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.