Syncline MCP Server (TypeScript)

com.kekwanuPublished by kekwanu.comv1.0.35Updated Oct 24, 2026

Syncline MCP Server (TypeScript) - AI-powered meeting scheduling with intelligent auto-scheduling

The publisher's own server: type.com

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Local MCP server that connects an AI assistant to Syncline for AI-powered meeting scheduling with intelligent auto-scheduling.

What you can do
  • Connects the assistant to Syncline, a meeting scheduling service.
  • Supports AI-powered meeting scheduling, including intelligent auto-scheduling of meetings.
  • No individual tools are documented in the supplied listing, so the exact operations available are not described.
When to use it
Useful when you want an assistant to help arrange meetings through Syncline, especially when automatic scheduling suggestions are wanted instead of manual back-and-forth.
Requirements
Runs as a local process over stdio, installed from the npm package @kekwanulabs/syncline-mcp-server, so a Node.js runtime is needed. Requires a Syncline API key supplied in the SYNCLINE_API_KEY environment variable, obtainable from the Syncline developer page. Desktop only.
Before you install
The server needs a Syncline API key stored in SYNCLINE_API_KEY; treat it as a secret and keep it out of shared configuration. Scheduling actions may create or change meetings and calendar data, and meeting details are sent to the Syncline service.

Installation

In SourceWeft

  1. Open Syncline MCP Server (TypeScript) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.35LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

Other Type integrations