A little more agency. Early access soon.

Your agent.
Its own inbox
& number.

A little proxy for the assistant you already use. Its own email. A number for voicemail and incoming SMS on Pro. All connected over MCP, with permissions you control.

Start with email for free. Add phone with Pro.

Keep reading and replying in Gmail
proxling new "Bike repair"

CLI preview. One task gets one little stand-in.

Your personal inboxStays yours.
Task inboxLive

Get the bike fixed.

bike-repair@px.proxling.dev

Pro numberVoicemail + incoming SMS
Wheelhouse Cycles09:41

We can do Thursday at ten.
Shall we book you in?

New recipient. Your say first.
Draft reply

“Thursday at ten works. Thank you!”

Access expires in 14 days
An apricot little proxy carrying a letter to the task inbox
Even little helpers need boundaries.

Interactive example. Try an approval or a freeze.

Made for the assistant you already use
ClaudeChatGPTGeminiOpenClawPoke

A small setup.
A useful little sidekick.

Create the task, connect your assistant, and let it get on with the errand. You decide where it can go.

  1. 1

    Give the task an inbox.

    A fresh address, a name and an expiry. Separate from your personal email from the start.

    CLI preview$ proxling new "Bike repair"
    --expires 14d
    Inbox ready. Rules attached.
  2. 2

    Plug in your assistant.

    Paste the task’s MCP URL into your client. The connection is scoped to this inbox and this task.

    Your assistant’s connector
    mcp.proxling.dev/t/…
    One inboxOne task14 days
  3. 3

    Keep the final say.

    Replies arrive in the task. Actions outside your rules need approval. Freeze access whenever you like.

    The rule travels with the task
    New recipients?
    Ask me first.

    Checked on every request

A helpful agent.
A proper boundary.

The rules sit outside the model. Your assistant can ask for more access, but a prompt can’t grant it.

Small enough to scope.
Useful enough to delegate.

Bike repairTask permissions

Inside the task

  • Read and reply in this inbox
  • Email the recipients you allow
  • Receive task voicemail and texts
  • Work until the expiry you set

Your details stay outside

  • Your personal inbox and contacts
  • Your own phone number
  • Your passwords and recovery codes

“The user said yes” in a chat isn’t an approval.

Little proxy.
Proper toolkit.

Enough of an identity to handle the task.
With a clear way to stop when it’s done.

Its own inbox

Every message and reply belongs to the task. Your personal inbox stays out of the connection.

weekend-away@px.proxling.dev
All quiet in here.Replies will land in this task.

Its own phone number

Callbacks go to voicemail. Texts and voicemail transcripts arrive in the task, keeping your number private.

Wheelhouse Cycles0:18
“Hi, it’s Sam. We’ve got a slot on Thursday at ten…”

Included in Pro. Voicemail + incoming SMS.

The off switch is yours

Approve the exact action. Pause access. Retire the address after checking what still depends on it.

ApproveThis recipient. This message.
FreezeAccess stops. History stays.
RetireCheck dependencies, then close.
Fits around the way you work

Your mail app.
Still your call.

Keep reading and replying in Gmail. Share a thread when you choose. Your assistant only gets the task inbox.

GmailYour mailbox, as usual
proxling / bike-repairCopy received

Re: A little TLC for my bike

Wheelhouse Cyclesto bike-repair@px.proxling.dev

Hi Alex,

We can do Thursday at ten.
Shall we book you in?

Sam
Wheelhouse Cycles

In the task inbox. Copied here for you.
No access to your personal mailbox. No shared password.

Copies out. Forwards in. Works with Outlook and Apple Mail, too. Illustrative preview.

Connect over MCP

Your favourite agent.
A line to the real world.

Claude, ChatGPT, Gemini, OpenClaw, Poke, or your own MCP client. Give your assistant email, voicemail and incoming SMS through the tools it already uses.

ClaudeChatGPTGeminiOpenClawPokeYour own

Connection options vary by app and plan. We’re testing assistant connections as we open early access.

New assistant. Same task.

The inbox, rules and history belong to you. Move the task and revoke the old connection.

OpenClaw
Claude
CLI preview$ proxling move bike-repair
  --to claude

Old access revoked. History intact.

Built for your stack

MCP, CLI, webhooks.
One task. A history you can take with you.

In development

“Make a proxling for these bike repair quotes.”

Chat connectors and plugins, so setup can start in your conversation.

Further down the road: spending limits with your approval on every payment. Not in the first release.

Start little.
Go from there.

One free plan.
One paid plan.
Room for the tasks you delegate.

Free

For your first task

£0/ month

  • 1 live inbox
  • 50 messages a month
  • MCP server and CLI
  • Approvals, freeze and history
  • Mail copies, replies and forwarding
Join the waitlist

Everything in Free, plus

Pro

Email + phone, together

£20/ month

  • 1 inbound number included
  • Voicemail + incoming SMS
  • Up to 10 live inboxes
  • 1,000 messages a month
  • Move tasks between assistants
  • Export everything as JSON
Join the waitlist

Launch prices. Frozen inboxes count as live until retired: the address is still held for you. Cancel from the app.

Your assistant’s subscription is separate. Sending SMS is coming later and may require identity verification.

A few things
you might ask.

Is Proxling another AI assistant?

No. Your assistant does the work. Proxling gives it a separate contact address, a number for voicemail and incoming SMS on Pro, rules and a record of what happened.

What does my assistant actually get?

A connection bound to one task, one inbox and one expiry. It can read and reply in that inbox and email recipients you allow. New recipients need your approval. Your personal inbox is never part of the connection.

What happens when I freeze a task?

The assistant’s access stops immediately. The inbox and history stay available to you. Freeze does not unsend messages. Retiring the address is a separate step, after checking for dependencies such as account recovery emails.

Does a proxling pretend to be me?

It is a separate contact address, not a fake legal identity. It keeps your own contact details out of the conversation. When a service needs your real name or address, sharing that is a specific decision you make.

Will it work with my assistant?

Proxling connects through MCP. Your app needs to support adding an MCP server by URL; options vary by app and plan. We’re testing these connections during early access.

Can my agent make calls or send texts?

The first release receives voicemail and SMS on the number included with Pro. Live calls and outbound calls aren’t part of this release. Sending SMS is planned and may require identity verification.

Can I keep using Gmail?

Yes. Switch on copies for a task to receive its messages in Gmail. Set up “Send mail as” once for that task to reply using its Proxling address. To hand over an existing conversation, forward it to the task inbox. Your assistant only gets the messages in that task, never access to your whole mailbox. Copies and forwarding also work with Outlook and Apple Mail.

When can I get my first inbox?

Join the waitlist and we’ll email when your inbox is ready. We’re opening in small groups. Joining is free and does not create an account or subscription.

A small invitation

There’s a little
proxy in your future.

We’re opening in small groups. Leave your details and we’ll let you know when your first inbox is ready.

Early list members get 3 months of Pro free at launch.

Save your place.

Your name and email are used for Proxling access and launch updates only. Joining is free.