com.codmir/mcp
NPM · @CODMIR/MCP · SCANNED SEP 25
AI-powered task execution, tickets, sprints, error debugging, and desktop control.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 117 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2150 tokens (~65/item across 33 items; 33 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_task" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.codmir/mcp server?
com.codmir/mcp runs locally as an npm package, launched with npx -y @codmir/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @codmir/mcp
claude mcp add com-codmir-mcp -- npx -y @codmir/mcp
{
"mcpServers": {
"com-codmir-mcp": {
"command": "npx",
"args": [
"-y",
"@codmir/mcp"
]
}
}
} {
"servers": {
"com-codmir-mcp": {
"command": "npx",
"args": [
"-y",
"@codmir/mcp"
]
}
}
} codex mcp add com-codmir-mcp -- npx -y @codmir/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-codmir-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@codmir/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-codmir-mcp --command npx --arg -y --arg @codmir/mcp
mcp_servers:
com-codmir-mcp:
command: "npx"
args: ["-y", "@codmir/mcp"] {
"McpServers": {
"com-codmir-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@codmir/mcp"
]
}
}
} assistant mcp add com-codmir-mcp -t stdio -c npx -a -y @codmir/mcp
{
"mcpServers": {
"com-codmir-mcp": {
"command": "npx",
"args": [
"-y",
"@codmir/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@codmir/mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_task_status ~34
Check the status of a running task execution.
| Name | Type | Req | Description |
|---|---|---|---|
| executionId | string | yes | The execution ID returned when task was started |
No output schema declared.
No examples provided.
codmir_click ~55
Click at screen coordinates (x, y). Use after taking a screenshot to identify the target location.
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate (pixels from left) |
| y | number | yes | Y coordinate (pixels from top) |
No output schema declared.
No examples provided.
codmir_connect ~98
Establish a real-time agent session with the Codmir desktop app. This announces the AI provider to the desktop UI, which shows a colored border glow indicating which agent is controlling the screen. Call this at the start of any desktop control session.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | AI provider name: claude, gemini, vercel, cursor, windsurf, or custom name |
| session_name | string | – | Optional human-readable session label |
No output schema declared.
No examples provided.
codmir_disconnect ~26
End the agent session with the Codmir desktop app. Removes the border glow indicator.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
codmir_double_click ~38
Double-click at screen coordinates (x, y).
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate |
| y | number | yes | Y coordinate |
No output schema declared.
No examples provided.
codmir_fetch_page ~83
Fetch a web page through the desktop agent. Returns HTTP status, headers, page title, all links, and the HTML body (truncated at 50KB). Use this for web app testing, crawling routes, and analyzing page content without needing screenshots.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL to fetch (e.g. http://localhost:3000/dashboard) |
No output schema declared.
No examples provided.
codmir_key ~129
Press a keyboard key or key combination. Use macOS key codes. Common: Return=36, Tab=48, Escape=53, Delete=51, Space=49, Up=126, Down=125, Left=123, Right=124. Flags: Shift=0x20000, Control=0x40000, Option=0x80000, Command=0x100000.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | number | – | Modifier flags (e.g. 0x100000 for Command). Default: 0 |
| key_code | number | yes | macOS virtual key code |
No output schema declared.
No examples provided.
codmir_list_directory ~94
List files and directories at a path on the desktop machine. Returns file names, sizes, and types. Useful for understanding project structure, finding config files, or mapping a codebase. Skips node_modules, .git, dist, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | number | – | How deep to recurse (default: 1, max recommended: 3) |
| path | string | yes | Absolute directory path to list |
No output schema declared.
No examples provided.
codmir_mouse_move ~43
Move the mouse cursor to screen coordinates (x, y) without clicking.
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate |
| y | number | yes | Y coordinate |
No output schema declared.
No examples provided.
codmir_right_click ~43
Right-click at screen coordinates (x, y) to open context menus.
| Name | Type | Req | Description |
|---|---|---|---|
| x | number | yes | X coordinate |
| y | number | yes | Y coordinate |
No output schema declared.
No examples provided.
codmir_scan_routes ~109
Scan multiple routes on a web app and return status codes for each. Useful for finding 404s, broken pages, redirect chains, and 500 errors. Returns a summary (counts of 200/404/3xx/5xx) and per-route results.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | yes | Base URL (e.g. http://localhost:3000) |
| routes | array | yes | Array of route paths to check (e.g. ["/", "/dashboard", "/settings"]) |
No output schema declared.
No examples provided.
codmir_screen_info ~31
Get screen dimensions and the name of the frontmost application. Call this first to understand the display layout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
codmir_screenshot ~36
Capture a screenshot of the entire screen. Returns a base64-encoded PNG image. Use this to see what is currently displayed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
codmir_scroll ~73
Scroll at the given screen coordinates. Negative delta scrolls down, positive scrolls up.
| Name | Type | Req | Description |
|---|---|---|---|
| delta | number | – | Scroll amount (negative = down, positive = up). Default: -3 |
| x | number | yes | X coordinate to scroll at |
| y | number | yes | Y coordinate to scroll at |
No output schema declared.
No examples provided.
codmir_shell ~57
Run a shell command on the machine where Codmir desktop is running. Returns stdout, stderr, and exit code.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command to execute |
| cwd | string | – | Working directory (default: home directory) |
No output schema declared.
No examples provided.
codmir_status ~31
Check if the Codmir desktop agent is running and connected. Returns status, port, platform, and architecture.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
codmir_type ~40
Type text at the current cursor position. Use codmir_click first to focus the target input field.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to type |
No output schema declared.
No examples provided.
create_organization ~57
Create a new organization/workspace for the user. Required before creating projects.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description |
| name | string | yes | Organization name |
| slug | string | – | URL-friendly identifier (auto-generated if omitted) |
No output schema declared.
No examples provided.
create_project ~84
Create a new project within an organization. Required before creating tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description |
| key | string | – | Short project key for ticket prefixes (auto-generated if omitted) |
| name | string | yes | Project name |
| organizationId | string | – | Organization ID (uses default org if omitted) |
| projectType | string | – | Type of project |
No output schema declared.
No examples provided.
create_ticket ~77
Create a new ticket in Codmir. Use this to capture bugs, features, or tasks from the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Detailed description |
| priority | string | – | Ticket priority |
| projectId | string | yes | The project ID |
| title | string | yes | Ticket title |
| type | string | – | Ticket type |
No output schema declared.
No examples provided.
execute_task ~77
Execute an AI-powered code task (bug fix, feature implementation, refactor). The task will be queued and executed by a Codmir agent.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | What the AI agent should do |
| projectId | string | yes | The project ID |
| ticketId | string | – | Optional ticket ID to link this task to |
No output schema declared.
No examples provided.
generate_sdk_code ~69
Generate SDK code for a specific use case. Returns ready-to-use TypeScript code.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Target language (default: typescript) |
| useCase | string | yes | What the code should do (e.g., "create a ticket for a bug", "list all projects") |
No output schema declared.
No examples provided.
get_error_context ~76
Get enriched error context for AI debugging. Returns the full error report plus suggested files to investigate (extracted from stack frames), a human-readable summary, and similar resolved issues. Ideal for understanding and fixing production errors.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Any error reference — refId, digest, reportId, fingerprint, or issueId |
No output schema declared.
No examples provided.
get_project_context ~34
Get project overview including tech stack, recent activity, and team info.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The project ID |
No output schema declared.
No examples provided.
get_sdk_reference ~56
Get Codmir SDK API reference for a specific topic. Use this to learn how to use the SDK for tickets, projects, organizations, chat, or agent tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Which SDK topic to get reference for |
No output schema declared.
No examples provided.
get_sprint_tasks ~58
Get tasks for the current or specified sprint. Returns all tasks with their status, assignee, and ticket details.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The project ID |
| status | string | – | Filter by status (default: all) |
No output schema declared.
No examples provided.
get_workspace_status ~27
Check if user has organization and projects set up. Call this first if other tools fail.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_project_tasks ~45
List all tasks for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of tasks to return (default: 20) |
| projectId | string | yes | The project ID |
No output schema declared.
No examples provided.
list_recent_errors ~86
List recent production errors from the Overseer error store. Returns the most recent errors with their refId, message, severity, route, and timestamp. Useful for getting an overview of current production issues.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of errors to return (default: 20, max: 50) |
| severity | string | – | Filter by severity (default: all) |
No output schema declared.
No examples provided.
list_todo ~125
Get the to-do list for a project — tickets filtered as actionable items (open/in_progress), sorted by priority. Excludes tickets with auto-execution workflow enabled. Use this for an overview of what needs to be done.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | string | – | Filter by assignee user ID |
| limit | number | – | Max items to return (default: 50) |
| priority | string | – | Filter by priority (default: all) |
| projectId | string | yes | The project ID |
| status | string | – | Filter by status (default: all actionable) |
No output schema declared.
No examples provided.
lookup_error ~95
Look up a production error report by any reference: refId (err_xxx), Next.js digest (3681244270), reportId (rpt_xxx), fingerprint (fp_xxx), or issueId (ISS-xxx). Returns the full stored error report with stack trace, breadcrumbs, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | Any error reference — refId, digest, reportId, fingerprint, or issueId |
No output schema declared.
No examples provided.
store_conversation ~96
Save this conversation as project documentation. Use to preserve important context, solutions, or decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Full content to save |
| projectId | string | yes | The project ID |
| summary | string | yes | Summary of the conversation |
| tags | array | – | Tags for categorization |
| ticketId | string | – | Optional ticket to link to |
| title | string | yes | Title for the saved context |
No output schema declared.
No examples provided.
update_todo_status ~68
Update the status of a to-do item (ticket). Use to mark items as done, in progress, or reopen them.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The project ID |
| status | string | yes | New status |
| ticketId | string | yes | The ticket ID to update |
No output schema declared.
No examples provided.
What is the com.codmir/mcp server?
com.codmir/mcp is listed in the public MCP registry as com.codmir/mcp. AI-powered task execution, tickets, sprints, error debugging, and desktop control. This page covers its npm package (@codmir/mcp).
Is the com.codmir/mcp server safe to use?
com.codmir/mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.codmir/mcp server expose?
com.codmir/mcp exposes 33 tools: get_sprint_tasks, execute_task, create_ticket, store_conversation, check_task_status, and 28 more. Their descriptions and schemas cost roughly 2,150 tokens of context every time the server is loaded.
Is the com.codmir/mcp server still maintained?
com.codmir/mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.codmir/mcp server under?
com.codmir/mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.