Skip to main content

​
Overview

Integrate Syncline with Claude Desktop or Claude Code to give Claude the ability to schedule meetings, find availability, and manage calendars directly.

​
Prerequisites

1

Install Syncline MCP Server

npm install -g @kekwanulabs/syncline-mcp-server
See Installation for details.
2

Get Platform API Key

Sign up at syncline.run/developer/login to get your API key.
3

Have Claude Desktop or Claude Code

Download Claude Desktop or install Claude Code.

​
Setup for Claude Desktop

​
1. Locate Configuration File

The Claude Desktop configuration file location varies by OS: 
~/Library/Application Support/Claude/claude_desktop_config.json

​
2. Add Syncline Configuration

Edit the config file and add the Syncline MCP server: 
{
  "mcpServers": {
    "syncline": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_your_api_key_here"
      }
    }
  }
}
Replace sk_live_your_api_key_here with your actual Syncline Platform API key from the developer dashboard.

​
3. Restart Claude Desktop

Close and reopen Claude Desktop for changes to take effect.

​
4. Verify Integration

In Claude Desktop, start a new conversation and try: 
Schedule a 30-minute meeting between alice@example.com and bob@example.com tomorrow at 2pm
Claude should use the Syncline MCP tools to complete the request.

​
Setup for Claude Code

Claude Code automatically detects MCP servers configured in the same format as Claude Desktop.

​
Using Project-Specific Configuration

For project-specific MCP servers, create a .claude/settings.json file in your project: 
{
  "mcpServers": {
    "syncline": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_your_api_key_here"
      }
    }
  }
}
Claude Code will automatically load this configuration when working in the project directory.

​
What Claude Can Do

Once integrated, Claude can:

Find Availability

“When are Alice and Bob both free this week?”

Schedule Meetings

“Schedule a 30-min meeting with alice@example.com tomorrow at 2pm”

Check Calendars

“Is alice@example.com free on Friday afternoon?”

Update Preferences

“Update my work hours to 10am-6pm on weekdays”

​
Example Conversations

​
Schedule a Meeting

Can you schedule a product demo with alice@example.com and bob@example.com?
30 minutes, sometime tomorrow afternoon would be great.

​
Find Availability

When are alice@example.com and bob@example.com both free this week?

​
Check Single Person’s Calendar

Is alice@example.com free on Friday afternoon?

​
Advanced Configuration

​
Multiple API Keys

If you work with multiple Syncline accounts: 
{
  "mcpServers": {
    "syncline-work": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_work_account_key"
      }
    },
    "syncline-personal": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_personal_account_key"
      }
    }
  }
}
Claude will have access to both servers and you can specify which to use: 
Using the syncline-work server, schedule a meeting with the engineering team

​
Custom Installation Path

If you installed Syncline locally instead of globally: 
{
  "mcpServers": {
    "syncline": {
      "command": "node",
      "args": ["/path/to/your/project/node_modules/@kekwanulabs/syncline-mcp-server/dist/index.js"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_your_api_key_here"
      }
    }
  }
}

​
Debug Mode

Enable debug logging to troubleshoot issues: 
{
  "mcpServers": {
    "syncline": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "sk_live_your_api_key_here",
        "DEBUG": "true"
      }
    }
  }
}
Logs will appear in Claude’s developer console.

​
Troubleshooting

​
Tools Not Showing Up

If Claude doesn’t see the Syncline tools:
  1. Verify configuration syntax - JSON must be valid
  2. Check API key - Ensure it starts with sk_live_
  3. Restart Claude - Must restart after config changes
  4. Check server logs - Enable debug mode to see errors

​
Invalid API Key Error

Error: Invalid API key
Solution:
  • Verify API key is correct in config file
  • Ensure no extra spaces or quotes
  • Get a fresh key from developer dashboard

​
Connection Timeout

Error: MCP server timeout
Solution:
  • Check internet connection
  • Verify firewall allows access to api.syncline.run
  • Try running the server manually to test:
npx @kekwanulabs/syncline-mcp-server

​
Permission Denied

Error: EACCES: permission denied
Solution:
  • Run with proper permissions
  • Or install globally with sudo: sudo npm install -g @kekwanulabs/syncline-mcp-server

​
Security Best Practices

Never share your API key or commit it to version control!

​
Use Environment Variables

Instead of hardcoding the API key in the config:
  1. Set environment variable in your shell:
export SYNCLINE_API_KEY=sk_live_your_api_key_here
  1. Reference it in config:
{
  "mcpServers": {
    "syncline": {
      "command": "npx",
      "args": ["-y", "@kekwanulabs/syncline-mcp-server"],
      "env": {
        "SYNCLINE_API_KEY": "${SYNCLINE_API_KEY}"
      }
    }
  }
}

​
Rotate Keys Regularly

Rotate your Platform API key every 90 days:
  1. Generate new key in developer dashboard
  2. Update configuration file
  3. Restart Claude Desktop/Code

​
Audit Tool Usage

Monitor MCP tool usage in your platform dashboard to detect unexpected activity.

​
What’s Next

Available Tools

Explore all MCP tools

Protocol Spec

Learn the MCP protocol

Build Custom Agent

Create your own AI agent