Open MCP Server
Click on "Install 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 Serversummarize 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
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ishuru/open-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server