ADK-Rust
← MCP server registry
Business operationsPublic source

Scheduling MCP Server

Global scheduling engine for ADK-Rust Enterprise agents. Provides 32 MCP tools covering appointments, shifts, resource booking, availability, conflict detection, 22-country holidays, multi-timezone overlap, waitlists,…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Conflict-free — rejects double-bookings automatically, respects time off and blackouts.

02

Globally aware — 22-country holidays, 40+ timezones, cultural work weeks (Mon-Fri, Sun-Thu, Mon-Sat).

03

Multi-timezone meetings — find overlapping working hours across Nairobi, NYC, and Singapore.

04

Feature parity — matches Calendly + Cal.com (waitlists, round-robin, booking links, group bookings).

05

Backend sync — bidirectional sync with Google Calendar, Outlook, Cal.com, Calendly.

06

Zero configuration — starts immediately. Integrations activate when env vars are set.

Architecture

How Scheduling MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Scheduling MCP Server

Validates the request and owns 32 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Scheduling MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

15 named tools shown from 32 documented tools

resource_create

Create schedulable resource

internal write
resource_list

List resources

read only
booking_create

Create booking with conflict check

internal write
booking_cancel

Cancel booking

internal write
booking_reschedule

Reschedule booking

internal write
booking_list

List bookings

read only
availability_check

Check available slots

read only
find_slot

Find first available slot

read only
shift_create

Schedule a shift

internal write
shift_update

Update shift status

internal write
shift_list

List shifts

read only
time_off_request

Request time off

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

8 internal write7 read only
  • The registry manifest declares internal write, read only tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Resources
ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-scheduling
MCP client configuration
{
  "mcpServers": {
    "scheduling": {
      "command": "mcp-scheduling",
      "env": {
        "GOOGLE_CALENDAR_TOKEN": "ya29.xxx (optional)",
        "CALCOM_API_KEY": "cal_xxx (optional)"
      }
    }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.mdCHANGELOG ↗CHANGELOG.mdIssues and support ↗github.com issues

Keep exploring

More in business operations.

Ads MCP ServerA digital advertising platform for ADK-Rust Enterprise sales & marketing agents. 19 MCP tools covering campaigns, ad groups, ads/creatives, budgets and bids, audiences, daily performance metrics with derived KPIs…19 toolsAnalytics MCP ServerGoverned analytics platform for AI agents — metrics, dashboards, funnels, cohorts, anomaly detection, forecasting, and policy enforcement. 28 tools with full audit trail.28 toolsBanking MCP ServerUnified banking MCP server with 15 tools across 3 backends — Plaid (US/Canada/EU), Mono (Africa), and Open Banking (UK/EU PSD2). Accounts, transactions, balances, payments, identity, and statements.15 tools

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.4.0
License
Apache-2.0
Tools
32
Revision
7126f397b6a1
Updated
May 27, 2026
Transportsstdio