{
  "markdown": "# PicSee MCP Server\n\nThe official remote Model Context Protocol (MCP) server for [PicSee](https://picsee.io), a URL shortener with link management and click analytics.\n\nConnect an AI agent to PicSee to create short links, manage existing links, and inspect click performance using natural language.\n\n## Official MCP endpoint\n\n```text\nhttps://api.picsee.io/mcp\n```\n\n- Transport: Streamable HTTP\n- Authentication: Anonymous or OAuth 2.1 with PKCE\n- Registry name: `io.picsee/short-link`\n- Official Registry: [MCP Registry](https://registry.modelcontextprotocol.io/?q=io.picsee%2Fshort-link)\n\n## Capabilities\n\n### Anonymous access\n\nAnonymous 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.\n\n### Signed-in access\n\nAfter signing in with PicSee OAuth, available tools depend on the account's API plan:\n\n- Create short links using available PicSee or branded domains.\n- Check API plan status and usage.\n- List available domains, tags, and tracking tools.\n- List, delete, or recover short links.\n- View overview, daily clicks, device, referrer, and country analytics.\n- Use Advanced-plan editing, search, metadata, tracking, and audience-label features when available.\n\nThe server dynamically exposes only the tools supported by the signed-in account.\n\n## Install\n\n### Codex\n\n```bash\ncodex mcp add picsee --url https://api.picsee.io/mcp\n```\n\nRestart Codex after installation. To sign in for account management and analytics:\n\n```bash\ncodex mcp login picsee\n```\n\n### Claude Desktop or another MCP client\n\nAdd the following Streamable HTTP server to the client's MCP configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"picsee\": {\n      \"url\": \"https://api.picsee.io/mcp\"\n    }\n  }\n}\n```\n\nIf a client does not support remote Streamable HTTP directly, use an MCP remote bridge supported by that client.\n\n## Example prompts\n\n```text\nShorten https://picsee.io and attribute the API usage to Codex.\n```\n\n```text\nShow my 10 most recent PicSee short links.\n```\n\n```text\nShow daily clicks and referrer sources for short link abc123 over the last 30 days.\n```\n\n```text\nChange the destination of abc123 to https://example.com/new-page.\n```\n\nEditing requires an eligible PicSee API plan.\n\n## Authentication\n\nPicSee uses OAuth 2.1 authorization code flow with PKCE and Dynamic Client Registration.\n\n- Authorization server: `https://public-api-oauth.picsee.io`\n- Protected resource: `https://api.picsee.io/mcp`\n- Scopes: `user:read`, `user:write`\n\nThe MCP client stores the access and refresh tokens. This repository does not ask users to paste API tokens into prompts or configuration files.\n\n### Why these scopes are requested\n\n- `user:read`: Read the account's API status, domains, tags, short-link list, and analytics.\n- `user:write`: Create, edit, delete, and recover short links when the account plan permits those actions.\n\n## Tool availability\n\n| Access level | Available tools |\n| --- | --- |\n| Anonymous | `create_short_link` |\n| Signed in | `create_short_link`, `get_api_status`, `get_api_usage_by_external_id`, `get_my_domains`, `get_my_tags`, `get_my_tracking_tools`, `list_short_links`, `delete_short_link`, `get_link_overview`, `get_link_daily_clicks`, `get_link_platforms`, `get_link_referrers`, `get_link_regions` |\n| Advanced plan | Signed-in tools plus `edit_short_link` and `get_link_audience_labels`; advanced fields and search filters are also enabled |\n\nTool 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.\n\n## Privacy and security\n\n- Never share PicSee access tokens in prompts, issues, screenshots, or logs.\n- Review the destination URL before creating or editing a short link.\n- Analytics may contain private campaign and audience information; share it only with intended recipients.\n- OAuth permissions can be revoked from your PicSee account.\n\nSee [PicSee Privacy Notice](https://picsee.io/privacy) and [Terms of Use](https://picsee.io/policy).\n\n## Documentation and support\n\n- [MCP and Agent Skill guide](https://picsee.io/help/agent-skill)\n- [PicSee API documentation](https://picsee.io/developers/docs/public-api.html)\n- [PicSee Help Center](https://picsee.io/help/)\n- [Report a technical issue](https://github.com/PicSeeInc/picsee-mcp/issues)\n\nWhen reporting an issue, include the MCP client name, operation attempted, timestamp, and sanitized error message. Do not include access tokens or private analytics data.\n\n## Development\n\nPrerequisites:\n\n- Node.js 22 or later\n- pnpm\n\n```bash\npnpm install\npnpm check\npnpm dev\n```\n\nBefore releasing, verify that the version in `package.json`, `server.json`, and the MCP `initialize` response is identical.\n\n## License\n\nMIT © PicSee Inc.\n",
  "bytes": 4810,
  "sha": "5b2ae6d5369fd9426f92874ae59c2c8801264c387c23dfc7ca81caa7a42d97cd",
  "repo_slug": "picseeinc/picsee-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_picsee_short_link_ba6d94f8/readme"
}