PicSee MCP Server

The official remote Model Context Protocol (MCP) server for PicSee, a URL shortener with link management and click analytics.

Connect an AI agent to PicSee to create short links, manage existing links, and inspect click performance using natural language.

Official MCP endpoint

https://api.picsee.io/mcp

• Transport: Streamable HTTP
• Authentication: Anonymous or OAuth 2.1 with PKCE
• Registry name: io.picsee/short-link
• Official Registry: MCP Registry

Capabilities

Anonymous access

Anonymous clients can create a PicSee short link using the shared pse.is domain. Anonymous access does not expose account data, link lists, management tools, or analytics.

Signed-in access

After signing in with PicSee OAuth, available tools depend on the account's API plan:

• Create short links using available PicSee or branded domains.
• Check API plan status and usage.
• List available domains, tags, and tracking tools.
• List, delete, or recover short links.
• View overview, daily clicks, device, referrer, and country analytics.
• Use Advanced-plan editing, search, metadata, tracking, and audience-label features when available.

The server dynamically exposes only the tools supported by the signed-in account.

Install

Codex

codex mcp add picsee --url https://api.picsee.io/mcp

Restart Codex after installation. To sign in for account management and analytics:

codex mcp login picsee

Claude Desktop or another MCP client

Add the following Streamable HTTP server to the client's MCP configuration:

{
  "mcpServers": {
    "picsee": {
      "url": "https://api.picsee.io/mcp"
    }
  }
}

If a client does not support remote Streamable HTTP directly, use an MCP remote bridge supported by that client.

Example prompts

Shorten https://picsee.io and attribute the API usage to Codex.

Show my 10 most recent PicSee short links.

Show daily clicks and referrer sources for short link abc123 over the last 30 days.

Change the destination of abc123 to https://example.com/new-page.

Editing requires an eligible PicSee API plan.

Authentication

PicSee uses OAuth 2.1 authorization code flow with PKCE and Dynamic Client Registration.

• Authorization server: https://public-api-oauth.picsee.io
• Protected resource: https://api.picsee.io/mcp
• Scopes: user:read, user:write

The MCP client stores the access and refresh tokens. This repository does not ask users to paste API tokens into prompts or configuration files.

Why these scopes are requested

• user:read: Read the account's API status, domains, tags, short-link list, and analytics.
• user:write: Create, edit, delete, and recover short links when the account plan permits those actions.

Tool availability

Tool availability is determined at connection time. Use your MCP client's tool inspector or tools/list to see the exact tools available to the current account.

Privacy and security

• Never share PicSee access tokens in prompts, issues, screenshots, or logs.
• Review the destination URL before creating or editing a short link.
• Analytics may contain private campaign and audience information; share it only with intended recipients.
• OAuth permissions can be revoked from your PicSee account.

See PicSee Privacy Notice and Terms of Use.

Documentation and support

• MCP and Agent Skill guide
• PicSee API documentation
• PicSee Help Center
• Report a technical issue

When reporting an issue, include the MCP client name, operation attempted, timestamp, and sanitized error message. Do not include access tokens or private analytics data.

Development

Prerequisites:

• Node.js 22 or later
• pnpm

pnpm install
pnpm check
pnpm dev

Before releasing, verify that the version in package.json, server.json, and the MCP initialize response is identical.

License

MIT © PicSee Inc.