For AI Agents & Assistants

Your links, reachable
by any AI agent.

returnbob runs a standard Model Context Protocol (MCP) server — an open protocol, not tied to one AI product. Connect any MCP-compatible assistant, agent, or app and manage your links in plain conversation.

Get Your MCP Access descriptionRead the MCP Docs

Open protocol Not tied to one AI product Works with any MCP client

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants and agents call tools on external services — the same way a browser can open any website regardless of who built it. returnbob exposes its own MCP server, so any MCP-compatible client can create, search, update, and analyze your links directly in a conversation.

hub

Any MCP Client

No plugin per platform to maintain — chat assistants, coding agents, IDEs, and custom apps all connect through the same standard endpoint.

shield

Scoped Access

Two separate keys: one sees everything, one only sees public/unlisted links — give an agent exactly the access you want.

bolt

Six Ready Tools

Create, list, search, update, delete links, and pull analytics — all exposed as clean, documented MCP tools.

dns

Runs on Our Servers

No separate infrastructure to host or maintain — the MCP server is part of returnbob itself.

One protocol. Any client.

Point any MCP-compatible client at your returnbob URL and a Bearer key. No plugin, no custom integration to maintain — the same standard endpoint works everywhere MCP is supported.

Read the Docs

URL:     https://www.returnbob.com/mcp
Header:  Authorization: Bearer rtb_pub_...

# Example — Claude Code / Desktop:
claude mcp add --transport http returnbob \
  https://www.returnbob.com/mcp \
  --header "Authorization: Bearer rtb_pub_..."

Your links, reachable by any AI agent.