lc.cx for AI agents
lc.cx is a URL shortener offering branded domains, tags, and click statistics for teams managing marketing links across campaigns and channels. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in lc.cx.
Create a branded short link
Create a short link on a branded domain for a new campaign or social post.
Check a link's click stats
Look up an existing short link's click activity and referrer breakdown, a read-only check before reporting on it.
Approve before deleting a link
Require approval before deleting a short link, since existing shares would stop resolving.
10 lc.cx actions, graded by risk.
Every lc.cx action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- lc_cx.list_tagsList Tags
- lc_cx.get_short_linkGet Short Link
- lc_cx.list_short_linksList Short Links
- lc_cx.get_account_contextGet Account Context
write
4Create and change things. Allow, or ask the user first.
- lc_cx.update_tagUpdate Tag
- lc_cx.create_tagsCreate Tags
- lc_cx.create_short_linkCreate Short Link
- lc_cx.update_short_linkUpdate Short Link
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- lc_cx.delete_tagDelete Tag
- lc_cx.delete_short_linkDelete Short Link
lc.cx in three steps.
- 01Your users connect lc.cxThey add their lc.cx api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Tags” can wait for the user, and “delete Tag” can be denied outright.
- 03Any agent can actYour agent calls lc.cx through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('lc_cx', { read: 'allow', write: 'ask', // create_tags destructive: 'deny', // delete_tag }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How lc.cx connects.
Users add their lc.cx api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same lc.cx connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use lc.cx from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
lc.cx and Arc0, answered.
Can I use lc.cx with Claude, ChatGPT or Cursor?
Yes. Connect lc.cx to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the lc.cx actions you allow.
How do users connect lc.cx?
Users add their lc.cx api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which lc.cx actions can my agent take?
10 in total: 4 read, 4 write and 2 destructive, such as “create Tags”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in lc.cx?
Yes. Actions like “delete Tag” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call lc.cx too?
Yes. The same lc.cx connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug lc.cx into your agent.
Your users connect lc.cx once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan