Picoli Mcp

io.github.amaterousPublished by GitHub account amaterousv1.0.1Updated Oct 27, 2026

MCP server for picoli.site - URL shortening and click analytics for AI agents

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

MCP server for picoli.site that lets an AI assistant shorten URLs, create custom slugs, and read click analytics for links.

What you can do
  • Create a short URL, optionally with a custom slug
  • Create up to 500 short URLs in one batch
  • Read click statistics for specific links, with bot traffic excluded
  • List all shortened links with click counts and pagination
  • Get an analytics overview: top 10 links, daily click trends and totals for a date range
When to use it
Useful when you want an assistant to generate short links for campaigns or sharing, or to report on how existing short links are performing without opening the picoli.site dashboard.
Requirements
Runs locally over stdio, typically via npx, so Node.js is needed. A picoli.site account and API key are required, passed in the PICOLI_API_KEY environment variable. The optional PICOLI_BASE_URL variable points at a self-hosted instance instead of the default service. Network access to the picoli.site API is required.
Before you install
The API key is a secret placed in the client configuration; keep it out of shared files. Creating short links writes data to your picoli.site account, and batch creation can add up to 500 links at once. Link data and analytics requests are sent to picoli.site, or to whatever host PICOLI_BASE_URL names.

Installation

In SourceWeft

  1. Open Picoli Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

picoli-mcp

MCP server for picoli.site — URL shortening and click analytics for AI agents.

Shorten URLs, track clicks, and analyze link performance directly from your AI assistant.

Setup

1. Get your API key

Create an account at picoli.site and get your API key from the dashboard.

2. Configure your MCP client

Claude Desktop / Claude Code

Add to your MCP configuration:

json
{  "mcpServers": {    "picoli": {      "command": "npx",      "args": ["-y", "picoli-mcp"],      "env": {        "PICOLI_API_KEY": "your-api-key-here"      }    }  }}
Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "picoli": {      "command": "npx",      "args": ["-y", "picoli-mcp"],      "env": {        "PICOLI_API_KEY": "your-api-key-here"      }    }  }}

Tools

shorten_url

Create a short URL with an optional custom slug.

Example prompts:

shorten_urls

Create multiple short URLs at once (up to 500).

Example prompts:

  • "Shorten these 3 URLs: ..."

get_link_stats

Get click statistics for specific links (bot traffic excluded).

Example prompts:

  • "How many clicks did my 'launch' link get?"
  • "Show me stats for these slugs: launch, demo, blog-post"

list_links

List all shortened URLs with click counts and pagination.

Example prompts:

  • "Show me all my short links"
  • "List my links sorted by clicks"

get_analytics

Get analytics overview: top 10 links, daily click trends, and totals.

Example prompts:

  • "Show me my link analytics for this week"
  • "What are my top performing links?"
  • "Give me click stats from 2026-01-01 to 2026-01-31"

Environment Variables

VariableRequiredDefaultDescription
PICOLI_API_KEYYes—Your picoli.site API key
PICOLI_BASE_URLNohttps://picoli.siteAPI base URL (for self-hosted instances)

Development

bash
git clone https://github.com/yun/picoli-mcp.gitcd picoli-mcpnpm installnpm run build

Test locally:

bash
PICOLI_API_KEY=your-key npx tsx src/index.ts

License

MIT

Source: README.md at commit b20085a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.