MCP Server Integration

LimeLink MCP server @limelink/mcp 0.1.0 is a separately released integration for compatible MCP clients. It requires Node.js 18 or later and uses stdio only.

Install and Start

Pin the reviewed release in your MCP client configuration:

{
  "mcpServers": {
    "limelink": {
      "command": "npx",
      "args": ["-y", "@limelink/mcp@0.1.0"]
    }
  }
}

The package executable is limelink-mcp. It does not provide an HTTP or remote MCP transport.

Documentation Without Credentials

The server exposes limelink://docs/index plus 15 allow-listed limelink://docs/{slug} pages without credentials. Documentation is fetched from limelink.org; successful responses are cached in memory for one hour. The cache is not persistent or shared between processes, and failed fetches are not cached.

Organization Profiles

API tools use version-1 named Organization profiles from the file selected by LIMELINK_PROFILES_FILE. This is the MCP package's only credential configuration entry point.

{
  "version": 1,
  "defaultProfile": "production",
  "profiles": {
    "production": {
      "apiKey": "your_organization_api_key",
      "organizationLabel": "Production",
      "projects": {
        "website": "11111111-1111-4111-8111-111111111111"
      }
    }
  }
}

Point the MCP process at that file:

{
  "mcpServers": {
    "limelink": {
      "command": "npx",
      "args": ["-y", "@limelink/mcp@0.1.0"],
      "env": {
        "LIMELINK_PROFILES_FILE": "/absolute/path/to/limelink-profiles.json"
      }
    }
  }
}

Profile selection uses an explicit tool profile, then the configured default, then the only profile when exactly one exists. Project-backed tools accept a Project alias from the selected profile or a Project UUID. API profiles initialize lazily on their first API call by inspecting the credential and its scopes; list-profiles is local. Profile-file edits, Project alias changes, and key rotation require a server restart.

Earlier environment-key and default-Project MCP configuration is ignored by this release. No prompt templates are registered.

Six Tools and Scopes

Tool	Purpose	Required scope
`list-profiles`	List locally configured profile names and labels	None; local only
`list-projects`	List Projects available to a profile	`projects:read`
`list-custom-domains`	List Custom Domains for a Project	`domains:read`
`create-link`	Create a V2 Core Link	`links:write`
`get-link-by-suffix`	Look up a Link by suffix through the retained V1 endpoint	`links:read`
`get-link-by-url`	Resolve a full Link URL through V2	`links:read`

Creation and URL resolution use V2. Suffix lookup temporarily retains V1, so not every Link operation is V2. The production API origin is fixed, and the server does not add request timeout, retry, or backoff behavior.

Security and Troubleshooting

Create an Organization API key under Organization API credentials and grant only the scopes needed by the selected tools.
Store the profile file outside source control and shared or synchronized directories. Use owner-only permissions where supported, for example chmod 600 /absolute/path/to/limelink-profiles.json.
Never paste credentials into prompts, repositories, logs, screenshots, browser code, or mobile apps.
Review mutation arguments before approving create-link.
Restart the server after editing profiles, aliases, or rotating keys.
If an API tool is denied, verify the selected profile, owning Organization, Project alias or UUID, and required scope.

Review the tagged v0.1.0 source and release before upgrading. For static context, use LLM Agent Integration. Terraform is a separate integration with its own configuration and operations; see Terraform Integration.