s.id Logo
s.id
Developer Platform

MCP Server

Let AI agents manage your s.id account through the Model Context Protocol.

Overview

s.id runs a hosted MCP (Model Context Protocol) server so AI agents and MCP-compatible clients — like Claude — can create links, manage microsites, and read analytics on your behalf. It speaks JSON-RPC 2.0 over a single endpoint and authenticates with the same API key or OAuth 2.0 credentials as the REST API.

Connect

Point your MCP client at the endpoint below and authenticate with an API key or an OAuth 2.0 Bearer token — the server auto-discovers your authorization server via RFC 9728.

Endpoint: https://mcp.s.id/mcp

{
  "mcpServers": {
    "sid": {
      "url": "https://mcp.s.id/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

Tools

28 tools are available, covering links, microsites, QR codes, and account data. Each tool requires the same scope as its REST equivalent.

Links

ToolDescriptionScope
create_linkCreate a short linklinks:write
bulk_create_linksCreate multiple short links in one calllinks:write
get_linkGet a link by IDlinks:read
list_linksList linkslinks:read
update_linkUpdate a linklinks:write
delete_linkArchive a linklinks:archive
unarchive_linkRestore an archived linklinks:write
check_short_availabilityCheck if a custom slug is availablelinks:read
get_link_statsGet a link's click timelinelinks:analytics
get_link_lifetime_statsGet a link's lifetime click countlinks:analytics
get_account_statsGet account-level click analyticslinks:analytics

Microsites

ToolDescriptionScope
create_micrositeCreate a micrositemicrosites:write
get_micrositeGet a microsite by slugmicrosites:read
list_micrositesList micrositesmicrosites:read
update_micrositeUpdate a micrositemicrosites:write
delete_micrositeDelete a micrositemicrosites:delete
check_microsite_slugCheck if a microsite slug is availablemicrosites:read
create_microsite_componentAdd a component to a micrositemicrosites:write
list_microsite_componentsList a microsite's componentsmicrosites:read
update_microsite_componentUpdate a microsite componentmicrosites:write
delete_microsite_componentDelete a microsite componentmicrosites:delete
order_microsite_componentsReorder a microsite's componentsmicrosites:write

QR

ToolDescriptionScope
get_link_qrGet a link's QR code settingsqr:read
set_link_qrCustomize a link's QR codeqr:write
get_global_qrGet global QR code settingsqr:read
set_global_qrCustomize global QR code settingsqr:write

Account

ToolDescriptionScope
get_user_infoGet the authenticated user's profileuser:read
get_quotaGet the authenticated user's account quotauser:read

Quota

A separate quota pool

MCP tool calls draw from their own daily quota, separate from your REST API call quota — using the MCP server does not consume your /v2 API allowance. Only tools/call requests count against it; tools/list and initialize are free.

View your usage

Authentication

API key or OAuth 2.0

Authenticate with the same sk_live_ API key or OAuth 2.0 Bearer token you use for the REST API — s.id is its own OAuth 2.0 authorization server, so a client can complete the full authorization flow and use the resulting token here.

OAuth 2.0 guide