calendar-event-crud-via-mcp, task-management-via-mcp, notes-storage-and-retrieval-via-mcp, mcp-server-protocol-implementation, routine-api-authentication-and-credential-management, mcp-tool-schema-definition-and-discovery

Routine

MCP ServerFree

** - MCP server to interact with [Routine](https://routine.co/): calendars, tasks, notes, etc.

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

calendar-event-crud-via-mcp

Medium confidence

Exposes Routine's calendar system through MCP protocol, enabling LLM agents and tools to create, read, update, and delete calendar events programmatically. Implements MCP resource and tool handlers that translate natural language or structured requests into Routine API calls, with support for event metadata (title, time, attendees, description). The server acts as a bridge between MCP clients and Routine's backend, handling authentication and request serialization.

Solves for

I want my AI agent to automatically schedule meetings based on natural language requestsI need to sync calendar events from an LLM-driven workflow into my calendar systemI want to query upcoming events and let an agent decide what to reschedule based on priorities

Best for

developers building LLM agents that need calendar integration

teams automating scheduling workflows with Claude or other MCP-compatible LLMs

builders creating AI assistants that manage personal or team calendars

Requires

Routine account with API access enabled

MCP client compatible with Routine server (Claude Desktop, custom MCP runners)

Node.js runtime for MCP server execution

Limitations

Requires active Routine account with API credentials

No built-in conflict detection or smart scheduling — delegates to Routine backend

MCP protocol overhead adds latency compared to direct REST API calls

What makes it unique

Implements MCP server pattern specifically for Routine's calendar system, enabling seamless LLM agent integration without requiring developers to build custom API wrappers — the MCP protocol standardizes how agents discover and invoke calendar operations

vs alternatives

Provides native MCP integration for Routine calendars, whereas generic REST API clients require developers to manually implement tool schemas and context management for LLM agents

task-management-via-mcp

Medium confidence

Exposes Routine's task/todo system through MCP tools and resources, allowing agents to create, list, update, and complete tasks with properties like priority, due dates, and descriptions. Implements MCP tool handlers that translate task operations into Routine API calls, supporting task state transitions (open, in-progress, completed) and metadata queries. Agents can query task lists, filter by status or due date, and update task progress.

Solves for

I want my AI agent to create tasks from meeting notes or email summariesI need to query my task list and have an agent prioritize or reassign workI want to mark tasks complete via natural language commands through an LLM

Best for

developers building productivity-focused AI agents

teams automating task creation from documents or conversations

solo developers integrating task management into LLM-driven workflows

Requires

Routine account with task management enabled

MCP client with task tool support

Valid Routine API credentials

Limitations

Task operations are limited to Routine's data model — no custom fields or extensions

No built-in task dependency or critical path analysis

Batch operations require sequential MCP calls, adding latency for bulk updates

What makes it unique

Wraps Routine's task API in MCP tool definitions, allowing LLM agents to discover and invoke task operations without hardcoded prompts — agents can introspect available task fields and operations at runtime

vs alternatives

Simpler than building custom task integrations with REST APIs because MCP standardizes tool discovery and invocation, reducing boilerplate in agent code

notes-storage-and-retrieval-via-mcp

Medium confidence

Exposes Routine's notes system through MCP resources and tools, enabling agents to create, read, update, and search notes with support for text content, metadata (tags, timestamps), and organization. Implements MCP resource handlers that map note IDs to content and tool handlers for note operations. Agents can store context, retrieve previous notes for reference, and organize notes with tags for later retrieval.

Solves for

I want my agent to store conversation summaries or meeting notes for later referenceI need to retrieve previous notes to provide context to an LLM agentI want to tag and organize notes so an agent can search and filter them

Best for

developers building knowledge-augmented AI agents

teams using agents for documentation and note-taking workflows

builders creating AI assistants that need persistent context storage

Requires

Routine account with notes feature enabled

MCP client supporting resource and tool handlers

Valid Routine API credentials

Limitations

Notes are stored in Routine backend — no local caching or offline access

Search is limited to Routine's indexing capabilities — no full-text semantic search without external RAG

No version history or collaborative editing features exposed via MCP

What makes it unique

Integrates Routine's notes as MCP resources, allowing agents to treat notes as first-class context sources that can be discovered and loaded dynamically — agents can reference note IDs in prompts without pre-loading all content

vs alternatives

More integrated than generic note-taking APIs because MCP resource semantics allow agents to understand note structure and metadata natively, enabling smarter retrieval patterns

mcp-server-protocol-implementation

Medium confidence

Implements the Model Context Protocol (MCP) server specification, exposing Routine capabilities as standardized MCP resources, tools, and prompts. The server handles MCP client connections, serializes requests/responses in JSON-RPC format, and manages authentication with Routine's backend. Implements MCP tool definitions with JSON schemas for calendar, task, and note operations, enabling any MCP-compatible client (Claude Desktop, custom runners) to discover and invoke Routine features.

Solves for

I want to use Routine with Claude or other MCP-compatible LLMs without custom integration codeI need a standardized interface to Routine that works across multiple AI tools and agentsI want to build custom MCP clients that can interact with Routine

Best for

developers integrating Routine into MCP-compatible AI platforms

teams standardizing on MCP for multi-tool AI workflows

builders creating custom MCP clients or runners

Requires

Node.js 16+ runtime

MCP client implementation (Claude Desktop, custom runner, etc.)

Routine API credentials

Limitations

MCP protocol overhead adds ~50-200ms per request compared to direct API calls

Server must be running to serve MCP clients — no serverless deployment model

MCP client compatibility varies — not all AI tools support MCP yet

What makes it unique

Implements full MCP server specification with tool and resource handlers, enabling Routine to be discovered and used by any MCP-compatible client — the server abstracts Routine's REST API behind MCP's standardized interface

vs alternatives

More flexible than direct API integration because MCP decouples clients from Routine's implementation details, allowing multiple tools and agents to interact with Routine through a single standardized server

routine-api-authentication-and-credential-management

Medium confidence

Handles authentication with Routine's backend API, managing credentials (tokens, OAuth) and maintaining authenticated sessions for MCP tool invocations. The server stores and refreshes credentials, implements error handling for auth failures, and ensures all downstream Routine API calls are properly authenticated. Supports credential configuration via environment variables or configuration files.

Solves for

I want to securely authenticate my MCP server with Routine without hardcoding credentialsI need my agent to maintain valid authentication across multiple Routine API callsI want to handle token refresh automatically so my agent doesn't fail mid-workflow

Best for

developers deploying MCP servers in production environments

teams managing multiple Routine accounts or credentials

builders securing agent-to-API communication

Requires

Routine API credentials (token or OAuth client ID/secret)

Environment variable or config file for credential storage

Node.js runtime with access to environment

Limitations

Credentials must be provided at server startup — no runtime credential injection

No built-in credential rotation or expiration management beyond token refresh

Credentials stored in memory — no persistent encryption or vault integration

What makes it unique

Centralizes credential management within the MCP server, allowing clients to invoke Routine operations without handling authentication directly — credentials are managed server-side, reducing exposure in client code

vs alternatives

Safer than embedding credentials in client code because the MCP server acts as a credential broker, isolating sensitive tokens from agent implementations

mcp-tool-schema-definition-and-discovery

Medium confidence

Defines JSON schemas for all Routine operations (calendar, task, notes) exposed as MCP tools, enabling clients to discover available operations, required parameters, and expected outputs at runtime. The server implements MCP's tools/list and tools/call handlers, providing schema introspection so clients can generate appropriate prompts and validate inputs before invocation. Schemas include descriptions, parameter types, and constraints.

Solves for

I want my LLM agent to discover what Routine operations are available without reading documentationI need to validate task or calendar parameters before sending them to RoutineI want to generate dynamic prompts that describe available Routine operations to the agent

Best for

developers building self-documenting AI agents

teams using schema-driven tool invocation patterns

builders creating generic MCP clients that work with multiple servers

Requires

MCP client that supports tools/list and tools/call

JSON schema validation library (optional, for client-side validation)

Node.js runtime for server

Limitations

Schemas are static — cannot reflect dynamic Routine features or custom fields

Schema validation is client-side responsibility — server does not enforce schema compliance

Complex nested schemas may be difficult for some LLM agents to parse

What makes it unique

Exposes Routine operations as discoverable MCP tools with full JSON schemas, allowing agents to understand available operations and constraints without hardcoded knowledge — schemas enable dynamic tool selection and parameter validation

vs alternatives

More flexible than static tool definitions because schema-based discovery allows agents to adapt to new Routine features or operations without code changes

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with Routine, ranked by overlap. Discovered automatically through the match graph.

MCP Server20

MintMCP

** - MCP servers for Google Calendar, Gmail, Outlook Calendar, and Outlook.

google calendar event synchronization and management via mcpoutlook calendar event synchronization and management via mcpmulti-provider calendar and email tool orchestration via mcp

3 shared capabilities

MCP Server22

Todoist

** - Full implementation of Todoist Rest API for MCP server

task-creation-via-mcp-protocoltask-update-and-modification

2 shared capabilities

MCP Server21

Project Manager

** - Hierarchical task management (ideas → epics → tasks) with CLI dashboard

mcp tool-use integration for ai-driven task managementpersistent task storage with file-based or database backend

2 shared capabilities

MCP Server24

Buildable

** - Official MCP server for Buildable AI-powered development platform. Enables AI assistants to manage tasks, track progress, get project context, and collaborate with humans on software projects.

task-management-via-mcp-protocol

1 shared capability

MCP Server26

@softeria/ms-365-mcp-server

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

calendar event querying and meeting management

1 shared capability

MCP Server43

keeper.sh

Calendar sync tool & universal calendar MCP server. Aggregate, sync and control calendars on Google, Outlook, Office 365, iCloud, CalDAV or ICS.

mcp-native calendar tool exposure for llm agents

1 shared capability

Best For

✓developers building LLM agents that need calendar integration
✓teams automating scheduling workflows with Claude or other MCP-compatible LLMs
✓builders creating AI assistants that manage personal or team calendars
✓developers building productivity-focused AI agents
✓teams automating task creation from documents or conversations
✓solo developers integrating task management into LLM-driven workflows
✓developers building knowledge-augmented AI agents
✓teams using agents for documentation and note-taking workflows

Known Limitations

⚠Requires active Routine account with API credentials
⚠No built-in conflict detection or smart scheduling — delegates to Routine backend
⚠MCP protocol overhead adds latency compared to direct REST API calls
⚠Limited to Routine's calendar feature set — cannot extend with custom fields without Routine support
⚠Task operations are limited to Routine's data model — no custom fields or extensions
⚠No built-in task dependency or critical path analysis

Requirements

Routine account with API access enabledMCP client compatible with Routine server (Claude Desktop, custom MCP runners)Node.js runtime for MCP server executionValid Routine API credentials (token or OAuth)Routine account with task management enabledMCP client with task tool supportValid Routine API credentialsNode.js runtime for server

Input / Output

Accepts: structured JSON (event objects with title, start, end, attendees), natural language requests (via LLM interpretation), event IDs for updates/deletions, structured JSON (task objects with title, priority, due date, description), natural language task descriptions, task IDs for updates/completion, plain text (note content), structured JSON (note metadata with tags, title), note IDs for retrieval/updates, JSON-RPC requests (MCP protocol format), tool invocation payloads with parameters, resource requests with IDs, API tokens or OAuth credentials, configuration files or environment variables, MCP tools/list requests, MCP tools/call requests with parameters matching schema

Produces: structured JSON (created/updated event objects), event lists with metadata, confirmation messages, structured JSON (task objects with metadata), task lists filtered by status/date, completion confirmations, plain text (note content), structured JSON (note objects with metadata), note lists with search results, JSON-RPC responses, tool results (structured JSON), resource content (text or JSON), authenticated HTTP headers for Routine API calls, auth error messages and retry signals, JSON schema definitions for each tool, tool invocation results

UnfragileRank

Adoption15%(30% weight)

Quality14%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit Routine→

About

** - MCP server to interact with [Routine](https://routine.co/): calendars, tasks, notes, etc.

Alternatives to Routine

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of Routine?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities6 decomposed

calendar-event-crud-via-mcp

Medium confidence

Solves for

Best for

developers building LLM agents that need calendar integration

teams automating scheduling workflows with Claude or other MCP-compatible LLMs

builders creating AI assistants that manage personal or team calendars

Requires

Routine account with API access enabled

MCP client compatible with Routine server (Claude Desktop, custom MCP runners)

Node.js runtime for MCP server execution

Limitations

Requires active Routine account with API credentials

No built-in conflict detection or smart scheduling — delegates to Routine backend

MCP protocol overhead adds latency compared to direct REST API calls

What makes it unique

vs alternatives

Provides native MCP integration for Routine calendars, whereas generic REST API clients require developers to manually implement tool schemas and context management for LLM agents

task-management-via-mcp

Medium confidence

Solves for

Best for

developers building productivity-focused AI agents

teams automating task creation from documents or conversations

solo developers integrating task management into LLM-driven workflows

Requires

Routine account with task management enabled

MCP client with task tool support

Valid Routine API credentials

Limitations

Task operations are limited to Routine's data model — no custom fields or extensions

No built-in task dependency or critical path analysis

Batch operations require sequential MCP calls, adding latency for bulk updates

What makes it unique

vs alternatives

Simpler than building custom task integrations with REST APIs because MCP standardizes tool discovery and invocation, reducing boilerplate in agent code

notes-storage-and-retrieval-via-mcp

Medium confidence

Solves for

Best for

developers building knowledge-augmented AI agents

teams using agents for documentation and note-taking workflows

builders creating AI assistants that need persistent context storage

Requires

Routine account with notes feature enabled

MCP client supporting resource and tool handlers

Valid Routine API credentials

Limitations

Notes are stored in Routine backend — no local caching or offline access

Search is limited to Routine's indexing capabilities — no full-text semantic search without external RAG

No version history or collaborative editing features exposed via MCP

What makes it unique

vs alternatives

More integrated than generic note-taking APIs because MCP resource semantics allow agents to understand note structure and metadata natively, enabling smarter retrieval patterns

mcp-server-protocol-implementation

Medium confidence

Solves for

Best for

developers integrating Routine into MCP-compatible AI platforms

teams standardizing on MCP for multi-tool AI workflows

builders creating custom MCP clients or runners

Requires

Node.js 16+ runtime

MCP client implementation (Claude Desktop, custom runner, etc.)

Routine API credentials

Limitations

MCP protocol overhead adds ~50-200ms per request compared to direct API calls

Server must be running to serve MCP clients — no serverless deployment model

MCP client compatibility varies — not all AI tools support MCP yet

What makes it unique

vs alternatives

routine-api-authentication-and-credential-management

Medium confidence

Solves for

Best for

developers deploying MCP servers in production environments

teams managing multiple Routine accounts or credentials

builders securing agent-to-API communication

Requires

Routine API credentials (token or OAuth client ID/secret)

Environment variable or config file for credential storage

Node.js runtime with access to environment

Limitations

Credentials must be provided at server startup — no runtime credential injection

No built-in credential rotation or expiration management beyond token refresh

Credentials stored in memory — no persistent encryption or vault integration

What makes it unique

vs alternatives

Safer than embedding credentials in client code because the MCP server acts as a credential broker, isolating sensitive tokens from agent implementations

mcp-tool-schema-definition-and-discovery

Medium confidence

Solves for

Best for

developers building self-documenting AI agents

teams using schema-driven tool invocation patterns

builders creating generic MCP clients that work with multiple servers

Requires

MCP client that supports tools/list and tools/call

JSON schema validation library (optional, for client-side validation)

Node.js runtime for server

Limitations

Schemas are static — cannot reflect dynamic Routine features or custom fields

Schema validation is client-side responsibility — server does not enforce schema compliance

Complex nested schemas may be difficult for some LLM agents to parse

What makes it unique

vs alternatives

More flexible than static tool definitions because schema-based discovery allows agents to adapt to new Routine features or operations without code changes

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to Routine

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Routine

Capabilities6 decomposed

calendar-event-crud-via-mcp

task-management-via-mcp

notes-storage-and-retrieval-via-mcp

mcp-server-protocol-implementation

routine-api-authentication-and-credential-management

mcp-tool-schema-definition-and-discovery

Related Artifactssharing capabilities

MintMCP

Todoist

Project Manager

Buildable

@softeria/ms-365-mcp-server

keeper.sh

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Routine

Are you the builder of Routine?

Get the weekly brief

Data Sources

Routine

Capabilities6 decomposed

calendar-event-crud-via-mcp

task-management-via-mcp

notes-storage-and-retrieval-via-mcp

mcp-server-protocol-implementation

routine-api-authentication-and-credential-management

mcp-tool-schema-definition-and-discovery

Related Artifactssharing capabilities

MintMCP

Todoist

Project Manager

Buildable

@softeria/ms-365-mcp-server

keeper.sh

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Routine

Are you the builder of Routine?

Get the weekly brief

Data Sources