cor-mcp
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., "@cor-mcp list my projects"
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.
cor-mcp
MCP (Model Context Protocol) server for the COR project management platform.
Exposes COR's REST API as MCP tools so any compatible AI assistant (Claude Desktop, Claude Code, Cursor, Windsurf, etc.) can manage projects, tasks, hours, clients, teams, and users using natural language.
Setup
1. Install dependencies
npm install2. Configure authentication
Copy the example env file:
cp env.example .envOption A — Client credentials (recommended for CI/automation):
Edit .env and add your API key and client secret:
COR_API_KEY=your_api_key_here
COR_CLIENT_SECRET=your_client_secret_hereGet these from COR: Settings → Integrations → API. The server will automatically obtain a Bearer token on startup using the OAuth2 client_credentials flow and refresh it when it expires.
Option B — Interactive login:
Leave COR_API_KEY / COR_CLIENT_SECRET unset. After connecting the MCP server, call cor_login with your email and password:
cor_login(email: "you@company.com", password: "...")The access token is stored in memory for the current session. You'll need to call cor_login again each time the server restarts.
3. Build
npm run build4. Configure your MCP client
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"cor": {
"command": "node",
"args": ["/absolute/path/to/cor-mcp/dist/index.js"]
}
}
}Claude Code
claude mcp add cor -- node /absolute/path/to/cor-mcp/dist/index.jsCursor / Windsurf / VS Code (Cline)
Add to your MCP config:
{
"mcpServers": {
"cor": {
"command": "node",
"args": ["/absolute/path/to/cor-mcp/dist/index.js"]
}
}
}Related MCP server: Rytnow MCP Server
Available Tools
Authentication
Tool | Description |
| Authenticate with email + password (stores token for the session) |
Projects
Tool | Description |
| List projects (paginated, optional name search) |
| Get project details by ID |
| Create a new project |
| Update an existing project |
Tasks
Tool | Description |
| List tasks (paginated, optional project filter) |
| Get task details by ID |
| Create a task within a project |
| Update an existing task |
Hours
Tool | Description |
| List logged hours (optional date filter) |
| Log worked hours to a task |
Clients
Tool | Description |
| List clients (optional name search) |
| Get client details by ID |
Teams
Tool | Description |
| List all teams |
| Get team details by ID |
Users
Tool | Description |
| List users (optional name search) |
| Get user profile by ID |
Reference Values
Task status: nueva · en_proceso · estancada · finalizada
Task priority: 0 = Low · 1 = Medium · 2 = High · 3 = Urgent
Project status: in_process · finished · suspended
Project health: 1 = On track · 2 = At risk · 3 = Delayed · 4 = Critical
Development
Run without building (uses tsx):
npm run devAvailable Tools
17 toolscor_create_projectB
Crea un nuevo proyecto en COR. / Create a new project in COR. Requires a project name. Optionally assign a client and team.
Inputs: name (required), description, clientId, teamId, +2 more.
cor_create_taskB
Crea una nueva tarea en COR dentro de un proyecto. / Create a new task in COR within a project. Requires a name and projectId. Optionally set status, priority, assignee, and due date.
Inputs: name (required), projectId (required), description, status, +4 more.
cor_get_clientB
Obtiene los detalles de un cliente de COR por su ID. / Get COR client details by ID.
Inputs: id (required).
cor_get_projectA
Obtiene un proyecto de COR por su ID. / Get a COR project by its ID. Returns full project details including status, health, client, and team.
Inputs: id (required).
cor_get_taskA
Obtiene el detalle completo de una tarea de COR por su ID. / Get full details of a COR task by ID. Includes status, priority, assignees, hours, and more.
Inputs: id (required).
cor_get_teamA
Obtiene los detalles de un equipo de COR por su ID. / Get COR team details by ID. Includes team name and associated metadata.
Inputs: id (required).
cor_get_userB
Obtiene el perfil de un usuario de COR por su ID. / Get a COR user profile by ID.
Inputs: id (required).
cor_list_clientsA
Lista los clientes en COR. / List clients in COR. Returns all clients with their contact info. Optionally search by name.
Inputs: search, page, perPage.
cor_list_hoursA
Lista las horas registradas en COR. / List logged hours in COR. Can filter by a specific date. Returns time entries with task, project, and user info.
Inputs: date, page, perPage.
cor_list_projectsA
Lista los proyectos de COR con paginación. / List COR projects with pagination. Use this to browse all projects, optionally filter by name.
Inputs: page, perPage, search.
cor_list_tasksA
Lista las tareas en COR con paginación opcional. / List tasks in COR with optional pagination. Can filter by project ID to see tasks within a specific project.
Inputs: page, perPage, projectId.
cor_list_teamsA
Lista los equipos en COR. / List teams in COR. Returns all teams. Useful for finding the teamId needed when creating or filtering projects.
Inputs: page, perPage.
cor_list_usersA
Lista los usuarios en COR. / List users in COR. Returns team members. Optionally search by name. Useful for finding userId when assigning tasks.
Inputs: search, page, perPage.
cor_log_hoursB
Registra horas trabajadas en COR para una tarea. / Log worked hours in COR for a task. Requires taskId, hours, and date. Optionally add a description.
Inputs: taskId (required), hours (required), date (required), description.
cor_loginA
Authenticate with COR using email and password. Call this if COR_API_KEY + COR_CLIENT_SECRET are not configured. Stores the access token in memory for the current session.
Inputs: email (required), password (required).
cor_update_projectA
Actualiza un proyecto existente en COR. / Update an existing COR project. Only provide the fields you want to change.
Inputs: id (required), name, description, clientId, +3 more.
cor_update_taskA
Actualiza una tarea existente en COR. / Update an existing COR task. Only provide the fields you want to change. Useful for changing status, priority, assignee, etc.
Inputs: id (required), name, description, status, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Each tool targets a unique resource and action (e.g., cor_create_project, cor_list_hours, cor_login). No two tools have overlapping purposes, and the resource is clearly indicated in the name and description.
All tools follow a consistent verb_noun pattern with snake_case and the cor_ prefix (e.g., cor_create_project, cor_list_users, cor_update_task). The verbs are standard CRUD and listing operations.
17 tools is well-scoped for a project management and time tracking system. Each tool serves a distinct purpose, and the number is neither too few to be useful nor too many to be overwhelming.
The tool set covers core CRUD operations for projects and tasks (create, read, update, list), plus list/get for clients, teams, users, and logging hours. Missing delete operations and creation for clients/teams/users, but these are minor gaps for typical workflows.
Maintenance
Related MCP Connectors
Manage projects, tasks, time tracking, and team collaboration through natural language.
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Connect your Cormak.app account to manage projects, task boards, AI agents and creative work from your AI assistant. The server exposes up to 83 tools, limited to the OAuth permissions you choose. Organize tasks, read and update project drafts, inspect saved studio results, create product descriptions and images, and request supported photo, video, 3D, voiceover, SEO and advertising operations. Publishing saved projects requires separate owner approval. Reading and ordinary manual task management do not themselves start paid generation. AI operations use credits from your connected Cormak account and require owner confirmation, or an existing bounded spending permission for supported product operations. You can limit and revoke connections in Cormak. The MCP does not provide bank access, payment details or provider API keys. CRM, streaming website generation and business-plan generation are not exposed through this integration. Get started: https://app.cormak.app/mcp Setup guide and examples: https://cormak.app/blog/cormak-mcp-guide Privacy: https://cormak.app/privacy Support: https://cormak.app/contact
Manage Loom projects, tasks, bugs, defects, clients and phases from AI assistants
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with OpenProject's API v3 for comprehensive project management operations including work packages, projects, time tracking, users, and all other OpenProject features through natural language.4MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Rytnow project management platform, supporting task management, time tracking, plan creation, and team collaboration through natural language commands.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Clockify time tracking API to manage time entries, projects, tasks, and workspaces through natural language commands.33 npm5ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with OpenProject installations for comprehensive project management, including creating projects and work packages, managing users and assignments, creating dependencies, and generating Gantt charts through natural language commands.15-