ClawLink

dev.claw-linkPublished by claw-link.devOfficial publisherv0.1.0Updated Oct 24, 2026

MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

ClawLink is a remote MCP server that connects an AI assistant to over 100 apps such as Gmail, Slack, Notion and GitHub through one-click OAuth.

What you can do
Connect an assistant to 100+ third-party apps through a single remote MCP endpoint, using one-click OAuth authorization per app. Work across services such as Gmail, Slack, Notion and GitHub from one connection rather than separate integrations. Authenticate requests with a ClawLink API key sent in the x-clawlink-api-key header. The manifest lists no individual tools, so the exact actions available per app are not specified.
When to use it
Useful when you want one assistant connection spanning several common SaaS apps instead of installing a separate MCP server for each, and you are comfortable authorizing those apps through ClawLink's OAuth flow.
Requirements
A remote endpoint at claw-link.dev over streamable HTTP; no local package or runtime. OAuth authorization is required, plus a ClawLink API key created in the ClawLink dashboard and supplied in the x-clawlink-api-key header. Network access to the endpoint.
Before you install
The server brokers access to your accounts in Gmail, Slack, Notion, GitHub and other apps, so OAuth grants may allow reading or changing data in those services. The API key is a secret; keep it out of shared logs and configuration. Data passes through a third-party service, and the manifest does not detail which tools or write actions are exposed.

Installation

In SourceWeft

  1. Open ClawLink 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/dev.claw-link%2Fclawlink/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": {
    "clawlink": {
      "type": "http",
      "url": "https://claw-link.dev/api/mcp"
    }
  }
}

README

This repository has no README.

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. v0.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.