
Syncline MCP Server (Go)
com.kekwanuPublished by kekwanu.comv1.1.1Updated Oct 24, 2026
Syncline MCP Server (Go) - AI-powered meeting scheduling with intelligent auto-scheduling
Overview
Local Syncline MCP server that lets an assistant handle AI-powered meeting scheduling with intelligent auto-scheduling.
- What you can do
- Meeting scheduling: described as AI-powered meeting scheduling with intelligent auto-scheduling.
- No tool list is published, so the exact actions an assistant can take are not documented here.
- The server runs locally over stdio and authenticates to Syncline with an API key.
- When to use it
- Worth considering if you use Syncline for meeting scheduling and want an assistant to help arrange meetings with automatic scheduling. Because no tools are documented, confirm the available actions before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package @kekwanulabs/syncline-mcp-server-go, so a Node.js runtime is needed. Requires a Syncline API key supplied in the SYNCLINE_API_KEY environment variable, obtained from the Syncline developer page. Desktop only.
Installation
In SourceWeft
- Open Syncline MCP Server (Go) in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.1.1LatestSep 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.