freelance.link

link.freelancePublished by freelance.linkOfficial publisherv1.0.0Updated Nov 5, 2026

Keep your freelance.link availability current: projects, absences and your waitlist.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote freelance.link MCP server that lets an assistant keep a freelancer's availability current: projects, absences and waitlist.

What you can do
  • Update availability information on freelance.link.
  • Manage projects, absences and the waitlist from the assistant.
  • Keep the freelancer's public availability status current.
  • No individual tools are listed, so the exact operations are not documented here.
When to use it
Useful for freelancers who publish their availability through freelance.link and want an assistant to keep projects, absences and waitlist entries up to date without opening the site.
Requirements
A remote MCP endpoint at freelance.link over streamable HTTP; OAuth authentication is required, so a freelance.link account is needed. No environment variables or headers are declared.
Before you install
The server changes availability data on a live freelance.link account, including projects, absences and waitlist entries, so edits may be visible to clients. OAuth grants access to that account; review the scopes requested before connecting.

Installation

In SourceWeft

  1. Open freelance.link in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/link.freelance%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "freelance-link": {
      "type": "http",
      "url": "https://freelance.link/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Freelance integrations