OSS 120B Autonomous Project Manager MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (optional) | info |
| OSS_MODEL | Yes | OSS model name (required) | gpt-oss:120b |
| GITHUB_TOKEN | No | GitHub token (optional) | |
| MEM0_API_KEY | Yes | API key for Mem0 (required) | |
| MOTION_API_KEY | No | API key for Motion (optional) | |
| NOTION_API_KEY | No | API key for Notion (optional) | |
| OLLAMA_BASE_URL | Yes | Base URL for Ollama server (required) | http://localhost:11434 |
| AUTO_SYNC_ON_START | No | Enable auto sync on start (optional) | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_projectC | Analyze a GitHub repository and extract project information autonomously |
| sync_projectsB | Run autonomous synchronization between GitHub, Notion, and Motion |
| detect_patternsC | Detect patterns in project management activities and suggest optimizations |
| populate_fieldsB | Autonomously populate missing Notion fields based on GitHub data |
| generate_summaryC | Generate daily/weekly summary report of PM activities |
| self_optimizeB | Run self-optimization analysis and get improvement recommendations |
| query_pmC | Query the PM agent with natural language for any project management task |
| get_prime_directiveA | Retrieve the current prime directive and operational parameters |
| set_automation_rulesB | Configure automation rules and thresholds |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct purpose, though 'query_pm' could overlap with specific tools like 'analyze_project' or 'generate_summary' if used broadly. Overall, boundaries are clear.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., 'analyze_project', 'sync_projects', 'set_automation_rules'. No deviations observed.
9 tools is well within the optimal range for a project management server. Each tool serves a clear function without redundancy or unnecessary expansion.
The set covers core autonomous PM activities like analysis, sync, configuration, and query. Minor gaps exist, such as no explicit tool for manual issue creation, but 'sync_projects' and 'query_pm' may address these.