Content Tools

liinks.co

Manages Liinks profiles, including profile fields, theme styles, social links, and blocks.

1 endpoint12 known toolsFirst detected August 24, 2026Last detected August 24, 2026

ENDPOINT 1

https://www.liinks.co/api/mcp

No auth detected

MCP server metadata

Name: liinks
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Manage Liinks profiles (link-in-bio pages at liinks.co/<slug>). Terminology: a *profile* is the entire public site (header, socials, theme, pages); a *page* is a section within a profile (every profile has at least the implicit `home` page, rendered as tabs). Typical flow: call `list_profiles` first to get valid profile ids (the API key owner's profile is always included), then read with `get_profile` before writing. After visual changes, `screenshot_profile` renders the live page so you can verify the result. Authentication: connect with an `Authorization: Bearer liinks_live_<token>` header. Keys are created in the Liinks dashboard under Admin → Settings → API Keys and require a paid plan.

Known tools 12

list_profiles

List the Liinks profiles this API key can manage.

Inferred read-only

get_profile

Read everything about one profile in a single call: profile fields, theme styles, social links, all blocks (in display order), and the page list.

Inferred read-only

update_profile

Partially update a profile's fields (displayName, bio, tagline, slug, profile picture, …).

Potential side effects

set_styles

Partially update the profile theme: colors, fonts, background, header layout, spacing.

Potential side effects

set_socials

Replace the profile's social-icon row with the provided ordered list.

Inferred read-only

add_block

Add a block to a profile page.

Inferred read-only

update_block

Partially update an existing block.

Potential side effects

remove_block

Delete a block from the profile.

Potential side effects

reorder_blocks

Set the top-to-bottom order of blocks on one page.

Inferred read-only

list_form_submissions

Read visitor responses to forms on the profile, newest first.

Inferred read-only

list_subscribers

Read the profile's email subscribers, newest first.

Potential side effects

screenshot_profile

Render the live public profile in headless Chrome and return JPEG URLs covering the full page in viewport-sized chunks (top to bottom).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.liinks]
url = "https://www.liinks.co/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "liinks": {
      "type": "http",
      "url": "https://www.liinks.co/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: liinks
Remote MCP URL: https://www.liinks.co/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "liinks": {
      "url": "https://www.liinks.co/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "liinks": {
      "type": "http",
      "url": "https://www.liinks.co/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "liinks",
  "transport": "streamable-http",
  "url": "https://www.liinks.co/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.