by mquan
Routine is workflow automation software that lets you create and manage automated approval and multi-step workflows to s
Connects to the Routine productivity app to access and manage your tasks, calendar events, documents, and contacts through AI assistants.
Routine is a community-built MCP server published by mquan that provides AI assistants with tools and capabilities via the Model Context Protocol. Routine is workflow automation software that lets you create and manage automated approval and multi-step workflows to s It is categorized under productivity, developer tools.
You can install Routine in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Routine is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
According to our notes, Routine benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Routine into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Routine reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Routine against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Routine for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Routine surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Routine is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: Routine is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Routine into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Routine benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 30
🌅🍳☕️📰🚗💼 MCP Routine is a MCP server that lets you create custom tools on the fly. It stitches actions executed by multiple MCP tools into a reusable routine.
If you perform the same sequence of tool calls over and over, a routine will save you time and remove prompting inconsistencies. A routine includes full context of the exact set of tools and inputs needed to execute a full task.
Copy the following into your MCP client's JSON file
{
"mcpServers": {
"myRoutines": {
"command": "npx",
"args": ["-y", "mcp-routine"],
"env": {
"FILENAME": "/path/to/your/mcp-routines.json"
}
}
}
}
The MCP server includes the following tools to manage routines
create-routine
load-routines
update-routine
delete-routine
Research a topic, then write the result into a new page in a given folder.
**User**: "add an Onboarding page to the Getting started page
**AI**: I'll help you add an "Onboarding" page to the Getting Started page. First, I'll need to find the Getting Started page ID.
Let me search for it:
Great, I found the Getting Started page. Now I'll create a new "Onboarding" page under it:
I've successfully created a new page titled "Onboarding" under the Getting Started page. The page has been created with a basic title, and you can now access it at the URL provided in the response. Would you like me to add any specific content to this new Onboarding page?
**User**:Yes, add some placeholder information for a standard onboarding experience
**AI**: I'll add some structured placeholder content to the Onboarding page to outline a standard onboarding experience.
**User**: now convert all these steps into a route to insert a page into a parent page
**AI**: I'll create a routine that captures the steps we just performed to insert a page into a parent page with structured content. This will make it reusable for future similar tasks.
I've created a routine called insert_structured_page that captures the workflow we used. The routine has three main steps:
1. Search for the parent page using its title to get the page ID
2. Create a new page under the found parent page
3. Add structured content to the new page with sections and bullet points
The routine is parameterized so you can customize:
- parent_page_title: The title of the parent page to search for
- new_page_title: The title for the new page
- welcome_message: Introduction text for the page
- section1_title: Title for the first section (can add more sections as needed)
- bullet_point1, bullet_point2, bullet_point3: Bullet points under sections
- help_message: The help/support message at the bottom
To use this routine, you would just need to provide these parameters with your desired content, and it will create a structured page with consistent formatting.
Build
npm run build
Execute
npx -y --prefix /path/to/local/mcp-routine routine
Publish
npm publish --access public
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.