Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add skedyul -- npx -y skedyul@1.7.48รันในเทอร์มินัล
{ "mcpServers": { "skedyul": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
The official Node.js SDK for building Skedyul integration apps. Publish tools, webhooks, CRM models, agents, skills, and workflows — then run them on serverless (Lambda) or dedicated (Docker/ECS) compute.
Package: skedyul · Version: 1.4.x · Node: 22+
The Skedyul SDK for Node.js
npm install skedyul
# or
pnpm add skedyul
The CLI is included:
skedyul --help
skedyul.config.tsimport { defineConfig } from 'skedyul'
import pkg from './package.json'
export default defineConfig({
name: 'My Integration',
version: pkg.version,
description: 'What this app does',
computeLayer: 'serverless',
tools: import('./src/registries'),
webhooks: import('./src/registries'),
provision: import('./provision'),
})
// provision.ts
import type { ProvisionConfig } from 'skedyul'
import env from './env'
import { models, relationships } from './crm'
import * as channels from './channels'
import * as pages from './pages'
import navigation from './pages/navigation'
export default {
env,
navigation,
models: Object.values(models),
channels: Object.values(channels),
pages: Object.values(pages),
relationships,
} satisfies ProvisionConfig
import { z, type ToolHandler, type ToolDefinition } from 'skedyul'
const inputSchema = z.object({
name: z.string().optional(),
})
type Input = z.infer<typeof inputSchema>
type Output = { message: string }
const handler: ToolHandler<Input, Output> = async (input) => ({
output: { message: `Hello, ${input.name ?? 'world'}!` },
billing: { credits: 1 },
meta: { success: true, message: 'Greeting sent', toolName: 'hello' },
})
export const helloTool: ToolDefinition<Input, Output> = {
name: 'hello',
description: 'Say hello to someone',
inputSchema,
handler,
}
skedyul auth login
skedyul dev link --workplace my-clinic
skedyul build
skedyul dev serve --workplace my-clinic
See Local development for the full workflow.
import { server } from 'skedyul'
import config from './skedyul.config'
const mcpServer = server.create({
...config,
computeLayer: 'serverless',
tools: toolRegistry,
webhooks: webhookRegistry,
})
export const handler = mcpServer.handler
Or use the dedicated subpath export:
import { handler } from 'skedyul/serverless'
const mcpServer = server.create({
...config,
computeLayer: 'dedicated',
defaultPort: 3000,
tools: toolRegistry,
webhooks: webhookRegistry,
})
await mcpServer.listen()
See Server runtime for endpoints, hooks, and compute-layer differences.
Full documentation lives in docs/.
Recommended layout for a modular integration app:
my-app/
├── skedyul.config.ts # App metadata, registries, build, queues
├── provision.ts # Aggregates version-level config
├── install.ts # Optional per-installation config (shared models)
├── env.ts # Environment variable definitions
├── crm/
│ ├── index.ts
│ ├── relationships.ts
│ └── models/
├── channels/
├── pages/
├── agents/ # Agent YAML v3 files (deployed via CLI)
├── skills/ # Skill YAML files
├── workflows/ # Workflow YAML v2 files
└── src/
├── registries.ts # Tool and webhook registries
└── server.ts # Optional custom server entry
# Authentication
skedyul auth login
skedyul auth use <profile>
# Local development (linked mode)
skedyul dev link --workplace <subdomain>
skedyul dev install --workplace <subdomain>
skedyul build
skedyul dev serve --workplace <subdomain>
# Deploy
skedyul dev diff --workplace <subdomain>
skedyul dev deploy --workplace <subdomain>
# Agents, skills, workflows
skedyul agents deploy --file ./agents/booking.yaml --workplace <subdomain>
skedyul skills deploy --file ./skills/scheduling.yaml --workplace <subdomain>
skedyul workflows deploy --file ./workflows/reminder.yaml --workplace <subdomain>
# Testing
skedyul chat --agent booking --workplace <subdomain>
skedyul dev invoke my_tool --workplace <subdomain>
skedyul apps deployment --id dpl_... # build + provision logs
See CLI reference for every command, flag, and config file path.
pnpm install
pnpm build # Compile TypeScript + bundle with tsup
pnpm test # Node test runner
anysrc/server/route-handlerstests/ for new behaviordocs/ when adding public APIs or CLI commandsOpen a PR with a clear summary for review.
MIT
{ "mcpServers": { "skedyul": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Skedyul ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 The Skedyul SDK for Node.js