Open MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Open MCP Server summarize the document at /home/user/reports/q3_summary.txt"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Open MCP Server
A modular Model Context Protocol (MCP) server with Prompts, Skills, and Workflows for personal productivity automation.
Features
Core Components
6 Prompt Templates - Reusable, parameterizable prompts for common tasks
11 Skills - Pre-defined task sequences that compose multiple tools
9 Workflows - Multi-step automation pipelines with conditionals and loops
15+ Tools - File operations, web scraping, git operations, system info, and AI summarization
Categories
Productivity: Daily planning, task prioritization, briefings
Development: Code review, project setup, refactoring guidance
Research: Topic exploration, document summarization
Document: File analysis, text summarization, word counting
Quick Start
# Install dependencies
npm install
# Build the project
npm run build
# Start the server
npm startServer Resources
Resource | Description |
| List all prompt templates |
| Get specific prompt template |
| List all available skills |
| Get specific skill details |
| List all workflows |
| Get specific workflow details |
| Server statistics and capabilities |
Available Tools
Prompt Management
list_prompts- List all prompts (optional category filter)search_prompts- Search prompts by query stringget_prompt- Get prompt template with parametersrender_prompt- Render a prompt with parametersvalidate_prompt- Validate prompt parametersget_prompt_categories- List all prompt categories
Skills (as Tools)
summarize_document- Read and summarize a fileanalyze_text- Read and analyze textsetup_project- Initialize a new projectdaily_briefing- Get daily productivity briefingproject_status- Get project status reportAnd 6 more...
Workflow Execution
execute_workflow- Execute a workflow by ID with variables
Original Tools
File:
read_file,write_file,list_directory,search_filesWeb:
fetch_url,scrape_htmlDev:
git_status,git_log,git_diff,system_info,get_timeAI:
summarize
Configuration
Command-line Arguments
node dist/index.js /path/to/workspace /home/user/documentsEnvironment Variables
GOOGLE_GENERATIVE_AI_API_KEY- Required for AI summarization features
Usage with Conductor
Add this MCP server to Conductor:
claude mcp add open-mcp -s user -- node /Users/sdluffy/conductor/workspaces/playground/san-jose/open-mcp/dist/index.jsOr add to your conductor.json:
{
"mcpServers": {
"open-mcp": {
"command": "node",
"args": ["/Users/sdluffy/conductor/workspaces/playground/san-jose/open-mcp/dist/index.js"]
}
}
}Project Structure
open-mcp/
├── src/
│ ├── index.ts # Main entry point
│ ├── core/ # Core engines
│ │ ├── prompt-manager.ts # Prompt template management
│ │ ├── skill-executor.ts # Skill execution engine
│ │ ├── workflow-engine.ts # Workflow engine with conditionals
│ │ └── registry.ts # Central component registry
│ ├── prompts/ # Prompt templates (YAML)
│ │ ├── productivity/
│ │ ├── code/
│ │ └── research/
│ ├── skills/ # Skill definitions
│ │ ├── categories/
│ │ │ ├── document.ts
│ │ │ ├── development.ts
│ │ │ └── productivity.ts
│ │ └── skills.ts # Skill registry
│ ├── workflows/ # Workflow definitions
│ │ ├── definitions/
│ │ │ ├── daily-routine.ts
│ │ │ ├── code-review.ts
│ │ │ └── project-setup.ts
│ │ └── workflows.ts # Workflow registry
│ ├── tools/ # Original tools
│ ├── types/ # TypeScript definitions
│ └── utils/ # Utilities
└── prompts/ # YAML prompt templatesForked Dependencies
We maintain forks of key dependencies for customization:
Repository | Fork | Purpose |
MCP SDK modifications | ||
OpenAI API spec |
Contributing to Forks
Make changes in your fork
Open a PR to the upstream repository
Reference the open-mcp issue you're solving
Development
# Watch mode
npm run dev
# Build
npm run build
# Run with output
npm run dev:fullAdding New Prompts
Create a YAML file in prompts/{category}/:
id: my_prompt
name: My Prompt
description: Description
category: productivity
template: |
Your template here with {{variables}}
parameters:
- name: variable
type: string
required: trueAdding New Skills
Create a skill in src/skills/categories/{category}.ts:
export const mySkill: Skill = {
id: "my_skill",
name: "My Skill",
description: "Description",
category: "my_category",
tools: [
{ tool: "tool_name", parameters: {...} }
],
inputSchema: { type: "object", properties: {...} },
outputSchema: { type: "object", properties: {...} }
};Adding New Workflows
Create a workflow in src/workflows/definitions/{name}.ts:
export const myWorkflow: Workflow = {
id: "my_workflow",
name: "My Workflow",
description: "Description",
steps: [
{ id: "step1", type: "tool", name: "Step 1", config: {...} }
]
};Architecture
┌─────────────────────────────────────────────────────────────────┐
│ MCP Client (Claude) │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ MCP Server (stdio) │
│ ┌───────────────────────────────────────────────────────────┐ │
│ │ Tool Registry │ │
│ │ ┌───────────┐ ┌───────────┐ ┌─────────────────────┐ │ │
│ │ │ Prompts │ │ Skills │ │ Workflows │ │ │
│ │ │ (Resource)│ │ (Tools) │ │ (Tools) │ │ │
│ │ └─────┬─────┘ └─────┬─────┘ └──────────┬──────────┘ │ │
│ └────────┼─────────────┼──────────────────┼─────────────────┘ │
│ │ │ │ │
│ ┌────────┼─────────────┼──────────────────┼─────────────────┐ │
│ │ ▼ ▼ ▼ │ │
│ │ ┌─────────┐ ┌─────────────┐ ┌──────────────────┐ │ │
│ │ │ Prompt │ │ Skill │ │ Workflow │ │ │
│ │ │ Manager │ │ Executor │ │ Engine │ │ │
│ │ └────┬────┘ └──────┬──────┘ └────────┬─────────┘ │ │
│ │ │ │ │ │ │
│ │ ▼ ▼ ▼ │ │
│ │ ┌─────────────────────────────────────────────────┐ │ │
│ │ │ Existing Tools │ │ │
│ │ │ file-tools | web-tools | dev-tools | ai-tools │ │ │
│ │ └─────────────────────────────────────────────────┘ │ │
│ └───────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘Security
Path validation with allowed directories whitelist
Command injection prevention
Timeout protection on HTTP requests
Directory traversal attack prevention
License
MIT License - see LICENSE for details
Links
Available Tools
19 toolsexecute_workflowC
Execute a workflow by ID with optional variables
Inputs: workflowId (required), variables.
fetch_urlD
Inputs: url (required), method, headers, body, +2 more.
get_promptB
Get a prompt template by ID with its parameters and examples
Inputs: id (required).
get_prompt_categoriesB
Get all available prompt categories
Inputs: no named parameters.
get_timeD
Inputs: timezone, format.
git_diffD
Inputs: path, cached.
git_logD
Inputs: path, maxCount.
git_statusD
Inputs: path.
list_directoryD
Inputs: path (required), includeHidden, recursive.
list_promptsC
List all available prompt templates, optionally filtered by category
Inputs: category.
read_fileD
Inputs: path (required), encoding.
render_promptC
Render a prompt template with the given parameters
Inputs: templateId (required), parameters (required).
scrape_htmlD
Inputs: url (required), extractText, extractLinks, extractImages.
search_filesD
Inputs: path (required), pattern (required), excludePatterns.
search_promptsC
Search for prompt templates by query string
Inputs: query (required).
summarizeD
Inputs: text (required), maxLength, language.
system_infoD
Inputs: include.
validate_promptB
Validate parameters against a prompt template without rendering
Inputs: templateId (required), parameters (required).
write_fileD
Inputs: path (required), content (required), encoding, createDirectories.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Most tools have distinct purposes, with clear separation between prompt management (get_prompt, list_prompts, render_prompt, validate_prompt), file operations (read_file, write_file, list_directory, search_files), git operations (git_diff, git_log, git_status), and utility functions (get_time, system_info, summarize). However, some tools like fetch_url and scrape_html could potentially overlap in web-related tasks, and the lack of descriptions for many tools creates minor ambiguity.
The naming follows a generally consistent verb_noun pattern (e.g., execute_workflow, get_prompt, list_directory, read_file), which is good. However, there are inconsistencies: some tools use underscores (git_diff) while others might imply similar patterns but lack clarity due to missing descriptions (e.g., summarize, system_info). The overall pattern is readable but not perfectly uniform.
With 19 tools, the count is on the higher side but still reasonable for a general-purpose 'Open MCP Server' aiming to cover multiple domains like workflows, prompts, file operations, git, and utilities. It feels slightly heavy, as some tools could be consolidated (e.g., multiple prompt-related tools), but it's not excessive and aligns with a broad scope.
The server covers several domains: prompt management has good coverage (list, get, render, validate, search), file operations are basic but functional (read, write, list, search), and git operations provide core commands. However, there are gaps: for workflows, only execute_workflow exists without tools for listing or managing workflows, and utility tools like fetch_url and scrape_html lack descriptions, making it hard to assess their coverage. Overall, it's moderately complete but has notable omissions.
Related MCP Connectors
AI-native project management for tasks, docs, collaboration, and agents.
Self-hosted AI prompt library: prompts, collections, tags, teams, chains. 29 MCP tools for agents.
One place to build, share, and govern the skills and tools your AI agents use at work.
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.