Heldly

io.heldlyPublished by heldly.ioOfficial publisherv1.0.0Updated Oct 24, 2026

AI-native scheduler that lives in Claude. Describe meetings in plain English; Heldly does the rest.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Heldly is a remote, AI-native scheduler that lets an assistant arrange meetings from plain-English descriptions.

What you can do
Heldly presents itself as an AI-native scheduler that lives inside Claude. According to its description, you describe meetings in plain English and the service handles the rest, rather than exposing a documented list of tools. No tool names or detailed capabilities are provided in the available material.
When to use it
Consider it when you want an assistant to help set up or arrange meetings from natural-language requests instead of manual calendar work. Because the available description is very brief, confirm the exact scheduling features before relying on it.
Requirements
It runs as a remote streamable HTTP endpoint at heldly.io, so no local package or runtime is needed. Authentication is required via OAuth. No environment variables or headers are declared.
Before you install
It requires OAuth sign-in, so you grant the service access to an account; review the scopes requested during authorization. The description does not state which calendar or meeting data it reads or writes, or whether data is shared with third parties, so verify this before connecting.

Installation

In SourceWeft

  1. Open Heldly 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/io.heldly%2Fscheduler/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": {
    "heldly": {
      "type": "http",
      "url": "https://heldly.io/api/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.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.