com.mcparmory/miro
PYPI · MCPARMORY-MIRO · 2 COMPONENTS · SCANNED SEP 20
Create and manage collaborative boards, items, and diagrams programmatically
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 Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 26826 tokens (~152/item across 176 items; 176 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 32 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 176 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/miro MCP server?
com.mcparmory/miro runs locally as a PyPI package, launched with uvx mcparmory-miro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-miro
claude mcp add com-mcparmory-miro -- uvx mcparmory-miro
{
"mcpServers": {
"com-mcparmory-miro": {
"command": "uvx",
"args": [
"mcparmory-miro"
]
}
}
} {
"servers": {
"com-mcparmory-miro": {
"command": "uvx",
"args": [
"mcparmory-miro"
]
}
}
} codex mcp add com-mcparmory-miro -- uvx mcparmory-miro
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-miro": {
"type": "local",
"command": [
"uvx",
"mcparmory-miro"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-miro --command uvx --arg mcparmory-miro
mcp_servers:
com-mcparmory-miro:
command: "uvx"
args: ["mcparmory-miro"] {
"McpServers": {
"com-mcparmory-miro": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-miro"
]
}
}
} assistant mcp add com-mcparmory-miro -t stdio -c uvx -a mcparmory-miro
{
"mcpServers": {
"com-mcparmory-miro": {
"command": "uvx",
"args": [
"mcparmory-miro"
]
}
}
} 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.
- 20 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.
- 19 Sept 26 −2
- Stability: pass → 0.83 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.77 functional
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 20 Sept 2026 · Analysed pypi/mcparmory-miro@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| 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 →
update_case Update Case ~141
Update case details such as name and description to keep case information accurate and aligned with the evolving scope of a legal matter. This operation is restricted to eDiscovery Admins and requires the Enterprise Guard add-on.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | The numeric ID of the case to be edited. |
| description | string | – | An optional description providing additional context or details about the case, such as scope, focus, or internal documentation standards. |
| name | string | yes | The updated name for the case. This field is required and helps maintain clarity and consistency across stakeholders. |
| org_id | string | yes | The numeric ID of the organization containing the case to be edited. |
No output schema declared.
No examples provided.
update_connector Update Connector ~603
Modify a connector's visual styling, path shape, and attachment points on a board. Update properties like line color, stroke style, captions, and connection endpoints to customize how the connector appears and connects items.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the connector to update. |
| captions | array | – | Text labels to display on the connector. Supports up to 20 caption blocks. |
| color | string | – | Hex color code for caption text (e.g., #9510ac). |
| connector_id | string | yes | The unique identifier of the connector to update. |
| endItemId | string | – | The unique identifier of the item to attach the connector's end point to. Frames are not supported. |
| endItemSnapTo | string | – | Which side of the end item to attach the connector: auto (automatic placement), top, right, bottom, or left. Cannot be combined with position-based attachment. Defaults to auto if not specified. |
| endStrokeCap | string | – | The decorative end cap style for the connector's endpoint: none, stealth, rounded_stealth, diamond, filled_diamond, oval, filled_oval, arrow, triangle, filled_triangle, or ERD notation styles (erd_on… |
| fontSize | string | – | Font size for captions in density-independent pixels, between 10 and 288. |
| shape | string | – | The connector line path type: straight (direct line), elbowed (right angles), or curved (smooth bends). Defaults to curved. |
| startItemId | string | – | The unique identifier of the item to attach the connector's start point to. Frames are not supported. |
| startItemSnapTo | string | – | Which side of the start item to attach the connector: auto (automatic placement), top, right, bottom, or left. Cannot be combined with position-based attachment. Defaults to auto if not specified. |
| startStrokeCap | string | – | The decorative start cap style for the connector's starting point: none, stealth, rounded_stealth, diamond, filled_diamond, oval, filled_oval, arrow, triangle, filled_triangle, or ERD notation styles… |
| strokeColor | string | – | Hex color code for the connector line (e.g., #2d9bf0). |
| strokeStyle | string | – | The line pattern style: normal (solid), dotted, or dashed. |
| strokeWidth | string | – | Line thickness in density-independent pixels, between 1 and 24. |
| textOrientation | string | – | Caption orientation relative to the connector line: horizontal (fixed orientation) or aligned (follows line curvature). |
No output schema declared.
No examples provided.
update_document_item Update Document Item ~185
Update a document item on a board by modifying its properties such as title, URL, dimensions, and rotation angle.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the document item to update. |
| height | number | – | The height of the item in pixels, specified as a decimal number. |
| item_id | string | yes | The unique identifier of the document item to update. |
| rotation | number | – | The rotation angle of the item in degrees relative to the board. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| title | string | – | A short text header to identify the document. |
| url | string | – | The URL where the document is hosted (e.g., a link to a PDF or other document file). |
| width | number | – | The width of the item in pixels, specified as a decimal number. |
No output schema declared.
No examples provided.
update_document_item_with_file Update Document Item with File ~248
Replace a document item on a board with a new file uploaded from your device. The file must not exceed 6 MB in size.
| Name | Type | Req | Description |
|---|---|---|---|
| altText | string | – | Optional alt-text description to improve accessibility and help viewers understand the document content. |
| board_id_PlatformFileUpload | string | yes | The unique identifier of the board containing the document item you want to update. |
| height | number | – | Optional height of the item in pixels. Specify as a decimal number. |
| item_id | string | yes | The unique identifier of the document item you want to replace with a new file. |
| resource | string | yes | Base64-encoded file content for upload. The file to upload from your device. Maximum file size is 6 MB. Provide the file as binary data. |
| rotation | number | – | Optional rotation angle in degrees, relative to the board. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| title | string | – | Optional title for the document (e.g., 'foo.png'). If not provided, the existing title is retained. |
| width | number | – | Optional width of the item in pixels. Specify as a decimal number. |
No output schema declared.
No examples provided.
update_embed_item Update Embed Item ~198
Updates an embed item on a board, allowing you to modify its display mode, preview image, source URL, and dimensions. Requires boards:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the embed item to update. |
| height | number | – | The height of the embed item in pixels. |
| item_id | string | yes | The unique identifier of the embed item to update. |
| mode | string | – | Controls how the embedded content displays on the board: 'inline' shows content directly on the board, while 'modal' displays it in an overlay. |
| previewUrl | string | – | URL of an image to use as the preview thumbnail for the embedded item. |
| url | string | – | A valid URL (HTTP or HTTPS) pointing to the content resource to embed on the board, such as a video or web page. |
| width | number | – | The width of the embed item in pixels. |
No output schema declared.
No examples provided.
update_frame Update Frame ~229
Update a frame's properties on a board, including its title, appearance, dimensions, and content visibility. Requires boards:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the frame to update. |
| fillColor | string | – | The fill color for the frame, specified as a hexadecimal color code. Supported colors include neutral grays, greens, teals, blues, purples, yellows, oranges, reds, and pinks. |
| format | string | – | The frame format type. Currently, only custom frames are supported. |
| height | number | – | The height of the frame in pixels. |
| item_id | string | yes | The unique identifier of the frame to update. |
| showContent | boolean | – | Whether to show or hide the content inside the frame. This feature is available on Enterprise plans only. |
| title | string | – | The title displayed at the top of the frame. |
| type | string | – | The frame layout type. Currently, only freeform frames are supported. |
| width | number | – | The width of the frame in pixels. |
No output schema declared.
No examples provided.
update_group Update Group ~130
Replaces an existing group on a board with new content. The original group is completely replaced and assigned a new ID.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the group to update. |
| description | string | – | Optional description providing additional context about the user group. |
| group_id | string | yes | The unique identifier of the group to replace. |
| id | string | yes | The unique identifier for the new user group. |
| name | string | yes | The name of the user group. |
| type | string | yes | The object type, which must be set to 'user-group'. |
No output schema declared.
No examples provided.
update_group_members Update Group Members ~130
Bulk add and remove members from a user group in a single request. Specify users to add and/or remove by email address.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the user group to modify. |
| membersToAdd | array | – | List of user email addresses to add to the group. Each email must correspond to an existing user in the organization. |
| membersToRemove | array | – | List of user email addresses to remove from the group. Each email must correspond to a current member of the group. |
| org_id | string | yes | The unique identifier of the organization containing the group. |
No output schema declared.
No examples provided.
update_group_members_and_details Update Group Members and Details ~158
Updates an existing group (team) by adding, removing, or replacing members, and modifying group properties like display name. Only specified attributes are updated; unchanged attributes remain as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| Operations | array | yes | An array of patch operations to perform on the group. Each operation specifies an action (add, remove, or replace), a target path, and values. Multiple users can be added or removed in a single reque… |
| id | string | yes | The unique server-assigned identifier for the group (team) to update. |
| schemas | string | yes | Must be set to the PatchOp schema identifier to indicate this is a patch operation request. |
No output schema declared.
No examples provided.
update_group_org Update Group ~120
Updates the name and/or description of a user group within an organization. This operation is restricted to Enterprise plan users with Company Admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new description for the group. Can be empty or up to 300 characters long. |
| group_id | string | yes | The unique identifier of the user group to update. |
| name | string | – | The new name for the group. Must be between 1 and 60 characters long. |
| org_id | string | yes | The unique identifier of the organization containing the group to update. |
No output schema declared.
No examples provided.
update_image_item Update Image Item ~170
Update an image item on a board by modifying its URL, title, dimensions, or rotation angle. Requires boards:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the image item to update. |
| height | number | – | The height of the image item in pixels. |
| item_id | string | yes | The unique identifier of the image item to update. |
| rotation | number | – | The rotation angle of the image in degrees relative to the board. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| title | string | – | A short text header to identify the image on the board. |
| url | string | – | The URL pointing to the image resource to display. |
| width | number | – | The width of the image item in pixels. |
No output schema declared.
No examples provided.
update_image_item_from_file Update Image Item from File ~275
Replace an image on a board with a new file from your device. Supports updating the image file itself along with optional metadata like title, alt text, dimensions, and rotation.
| Name | Type | Req | Description |
|---|---|---|---|
| altText | string | – | Optional alt text describing the image content for accessibility purposes. Helps users understand what the image depicts. |
| board_id_PlatformFileUpload | string | yes | The unique identifier of the board containing the image item you want to update. |
| height | number | – | Optional height of the image in pixels. Specify as a decimal number to set or adjust the vertical dimension. |
| item_id | string | yes | The unique identifier of the image item on the board that you want to replace or modify. |
| resource | string | yes | Base64-encoded file content for upload. The image file to upload from your device. Maximum file size is 6 MB. This replaces the existing image on the item. |
| rotation | number | – | Optional rotation angle in degrees. Use positive values to rotate clockwise and negative values to rotate counterclockwise. |
| title | string | – | Optional display name for the image (e.g., 'foo.png'). If not provided, the existing title is retained. |
| width | number | – | Optional width of the image in pixels. Specify as a decimal number to set or adjust the horizontal dimension. |
No output schema declared.
No examples provided.
update_item_position_or_parent Update Item Position or Parent ~226
Reposition an item on a board or move it to a different parent container. Use this operation to reorganize board layout or change item hierarchy.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the item to update. |
| id | string | – | Unique identifier (ID) of the parent frame for the item. |
| item_id | string | yes | The unique identifier of the item whose position or parent you want to change. |
| x | number | – | X-axis coordinate of the location of the item on the board. By default, all items have absolute positioning to the board, not the current viewport. Default: `0`. The center point of the board has `x:… |
| y | number | – | Y-axis coordinate of the location of the item on the board. By default, all items have absolute positioning to the board, not the current viewport. Default: `0`. The center point of the board has `x:… |
No output schema declared.
No examples provided.
update_legal_hold Update Legal Hold ~238
Update an existing legal hold to adjust preservation scope as case requirements evolve. Modify the hold's name, description, and add or remove users and boards to ensure accurate data preservation throughout the legal process.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | The numeric ID of the case containing the legal hold. Must be a numeric string. |
| description | string | – | Optional description providing additional context or details about the legal hold and its scope. |
| legal_hold_id | string | yes | The numeric ID of the legal hold to update. Must be a numeric string. |
| name | string | yes | The name assigned to the legal hold. Used to identify the hold within the case. |
| org_id | string | yes | The numeric ID of the organization containing the legal hold. Must be a numeric string. |
| scope | object | yes | The scope criteria determining which content items are preserved under this hold. Currently supports the `users` variant to place specific users under hold. Provide a complete list of all users to be… |
No output schema declared.
No examples provided.
update_project Update Project ~105
Update project details such as the project name. This operation is available only for Enterprise plan users with Company Admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new name for the project. Must be between 1 and 60 characters. |
| org_id | string | yes | The unique identifier of the organization containing the project. |
| project_id | string | yes | The unique identifier of the project to update. |
| team_id | string | yes | The unique identifier of the team that owns the project. |
No output schema declared.
No examples provided.
update_project_member_role Update Project Member Role ~233
Update a project member's role within a team's project space. This enterprise-only operation allows Company Admins to modify member permissions such as changing them from viewer to editor or assigning ownership roles.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The member ID whose role you want to update. Use the numeric member identifier (e.g., 307445734562315000). |
| org_id | string | yes | The organization ID that contains the team and project. Use the numeric organization identifier (e.g., 3074457345618265000). |
| project_id | string | yes | The project (Space) ID where the member's role will be updated. Use the numeric project identifier (e.g., 3074457345618265000). |
| role | string | – | The new role to assign to the project member. Valid roles are: owner, coowner, editor, commentator, or viewer. Determines the member's access level and permissions within the project. |
| team_id | string | yes | The team ID that owns the project. Use the numeric team identifier (e.g., 3074457345619012000). |
No output schema declared.
No examples provided.
update_shape_item Update Shape Item ~510
Modify a shape item's geometry, styling, and text content on a board. Updates only the properties you specify; omitted properties remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the shape item to update. |
| borderColor | string | – | The hex color code for the shape's border outline. |
| borderOpacity | string | – | The transparency level of the border, from 0.0 (fully transparent) to 1.0 (fully opaque). |
| borderStyle | string | – | The visual style of the border: solid (normal), dotted, or dashed. |
| borderWidth | string | – | The thickness of the border in display pixels, ranging from 1 to 24. |
| color | string | – | The hex color code for the text displayed within the shape. |
| content | string | – | The text content to display on the shape. Note: Changing the shape type to flow_chart_or or flow_chart_summing_junction will clear any existing content. |
| fillColor | string | – | The hex color code for the shape's fill background. Supports predefined palette colors or custom hex values. |
| fillOpacity | string | – | The transparency level of the fill color, from 0.0 (fully transparent) to 1.0 (fully opaque). |
| fontFamily | string | – | The typeface for text rendering. Choose from a curated set including sans-serif (Arial, Open Sans, Roboto), serif (Georgia, Times New Roman), and decorative fonts. |
| fontSize | string | – | The size of the text in display pixels, ranging from 10 to 288. |
| height | number | – | The height of the shape in pixels. |
| item_id | string | yes | The unique identifier of the shape item to update. |
| rotation | number | – | The rotation angle in degrees. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| shape | string | – | The geometric shape type to render. Choose from basic shapes (rectangle, circle, triangle, etc.), flowchart shapes (flow_chart_process, flow_chart_decision, etc.), or specialized shapes (cloud, star,… |
| textAlign | string | – | The horizontal alignment of text within the shape: left, right, or center. |
| textAlignVertical | string | – | The vertical alignment of text within the shape: top, middle, or bottom. |
| width | number | – | The width of the shape in pixels. |
No output schema declared.
No examples provided.
update_shape_item_flowchart Update Shape Item Flowchart ~554
Update a flowchart shape item on a board by modifying its geometry, styling, content, and layout properties. Changes are applied immediately to the specified shape.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the shape to update. |
| borderColor | string | – | The color of the shape's border, specified as a hex value. |
| borderOpacity | string | – | The transparency level of the border, from 0.0 (fully transparent) to 1.0 (fully opaque). |
| borderStyle | string | – | The visual style of the border: normal (solid), dotted, or dashed. |
| borderWidth | string | – | The thickness of the border in display pixels, ranging from 1 to 24. |
| color | string | – | The color of the text within the shape, specified as a hex value. |
| content | string | – | The text content to display on the shape. Note that changing the shape type to flow_chart_or or flow_chart_summing_junction will clear any existing content. |
| fillColor | string | – | The fill color of the shape, specified as a hex value. Supports standard palette colors like #8fd14f, #23bfe7, #ff9d48, and others. |
| fillOpacity | string | – | The transparency level of the fill color, from 0.0 (fully transparent) to 1.0 (fully opaque). |
| fontFamily | string | – | The font family for text within the shape. Choose from standard fonts (Arial, Georgia, Times New Roman) or design-focused options (Abril Fatface, Bangers, Permanent Marker, etc.). |
| fontSize | string | – | The font size for text in the shape, in display pixels, ranging from 10 to 288. |
| height | number | – | The height of the shape in pixels. |
| item_id | string | yes | The unique identifier of the shape item to update. |
| rotation | number | – | The rotation angle of the shape in degrees, relative to the board. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| shape | string | – | The geometric shape type to render. Choose from basic shapes (rectangle, circle, triangle, etc.), flowchart-specific shapes (flow_chart_decision, flow_chart_process, etc.), or arrow/callout variants.… |
| textAlign | string | – | The horizontal alignment of text within the shape: left, right, or center. |
| textAlignVertical | string | – | The vertical alignment of text within the shape: top, middle, or bottom. |
| width | number | – | The width of the shape in pixels. |
No output schema declared.
No examples provided.
update_sticky_note Update Sticky Note ~242
Modify the content, appearance, and layout of a sticky note item on a board. Update text, colors, alignment, shape, and dimensions as needed.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the sticky note to update. |
| content | string | – | The text content to display in the sticky note. |
| fillColor | string | – | The background color of the sticky note. Choose from 15 preset colors including gray, yellows, greens, blues, pinks, and more. |
| height | number | – | The height of the sticky note in pixels. |
| item_id | string | yes | The unique identifier of the sticky note item to update. |
| shape | string | – | The geometric shape of the sticky note: square (default) or rectangle, which affects the aspect ratio of the item's dimensions. |
| textAlign | string | – | The horizontal alignment of text within the sticky note: left, center, or right. |
| textAlignVertical | string | – | The vertical alignment of text within the sticky note: top, middle, or bottom. |
| width | number | – | The width of the sticky note in pixels. |
No output schema declared.
No examples provided.
update_tag Update Tag ~164
Updates an existing tag on a board by modifying its title and/or fill color. Note that changes made via the REST API will not appear in real-time on the board; you must refresh the board to see updates.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the tag you want to update. |
| fillColor | string | – | The fill color for the tag. Choose from: red, light_green, cyan, yellow, magenta, green, blue, gray, violet, dark_green, dark_blue, or black. |
| tag_id | string | yes | The unique identifier of the tag you want to update. |
| title | string | – | The text label for the tag, case-sensitive and must be unique within the board. Maximum 120 characters. |
No output schema declared.
No examples provided.
update_team Update Team ~83
Updates an existing team's properties within an organization. Requires Enterprise plan access and Company Admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The new name for the team. Must be between 1 and 60 characters long. |
| org_id | string | yes | The unique identifier of the organization containing the team. |
| team_id | string | yes | The unique identifier of the team to update. |
No output schema declared.
No examples provided.
update_team_boards_classification_bulk Update Team Boards Classification in Bulk ~177
Bulk update data classification labels for boards within a team. Optionally target only unclassified boards or apply the classification to all boards in the team.
| Name | Type | Req | Description |
|---|---|---|---|
| labelId | string | – | The numeric ID of the data classification label to assign to the boards. This label must be valid for the organization. |
| notClassifiedOnly | boolean | – | When true, applies the classification label only to boards that are not yet classified. When false or omitted, applies the label to all boards in the team regardless of current classification status. |
| org_id | string | yes | The unique identifier of the organization. This is a numeric ID that identifies which organization owns the team. |
| team_id | string | yes | The unique identifier of the team whose boards will be updated. This is a numeric ID that identifies the specific team within the organization. |
No output schema declared.
No examples provided.
update_team_member_role Update Team Member Role ~148
Update a team member's role within a team. This operation allows Company Admins to change a team member's permissions between standard member and admin roles. Available only for Enterprise plan users.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The unique identifier of the team member whose role should be updated. |
| org_id | string | yes | The unique identifier of the organization containing the team. Use the organization ID provided in your Enterprise account. |
| role | string | – | The new role to assign to the team member. Choose 'member' for standard team member permissions or 'admin' to grant team management capabilities. |
| team_id | string | yes | The unique identifier of the team containing the member to update. |
No output schema declared.
No examples provided.
update_text_item Update Text Item ~437
Modify the content, styling, and layout of a text item on a board. Update text content, colors, fonts, alignment, rotation, and dimensions as needed.
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | string | yes | The unique identifier of the board containing the text item to update. |
| color | string | – | Hex color code for the text itself (e.g., '#1a1a1a' for dark text). |
| content | string | yes | The text content to display in the item (e.g., 'Hello'). |
| fillColor | string | – | Hex color code for the background fill of the text item (e.g., '#e6e6e6' for light gray). |
| fillOpacity | string | – | Transparency level of the background color, ranging from 0.0 (completely transparent) to 1.0 (completely opaque). |
| fontFamily | string | – | Font family for the text. Choose from: arial, abril_fatface, bangers, eb_garamond, georgia, graduate, gravitas_one, fredoka_one, nixie_one, open_sans, permanent_marker, pt_sans, pt_sans_narrow, pt_se… |
| fontSize | string | – | Font size in display pixels. Must be at least 1 pixel. |
| item_id | string | yes | The unique identifier of the text item to update. |
| rotation | number | – | Rotation angle in degrees. Use positive values for clockwise rotation and negative values for counterclockwise rotation. |
| textAlign | string | – | Horizontal alignment of the text content: left, right, or center. |
| width | number | – | Width of the item in pixels. Minimum width is 1.7 times the font size (e.g., font size 14 requires minimum width of 24). |
No output schema declared.
No examples provided.
update_user Update User ~488
Replace an existing user resource with updated information. Note that deactivated users cannot have their userName, userType, or roles modified, and email updates for deactivated users are silently ignored. Only active organization members (non-guests) can be updated.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Boolean flag indicating whether the user is active or deactivated in the organization. |
| costCenter | string | – | The cost center associated with the user, up to 120 characters maximum. |
| department | string | – | The department within the organization to which the user belongs, up to 120 characters maximum. |
| displayName | string | – | A human-readable display name for the user, typically their full name. |
| division | string | – | The division within the organization to which the user belongs, up to 120 characters maximum. |
| emails | array | – | An array of email address objects, each containing a value, display name, and primary flag. Updates to this field are ignored for deactivated users. |
| employeeNumber | string | – | A unique identifier for the user within the organization, up to 20 characters maximum. |
| familyName | string | – | The user's last name or surname. |
| givenName | string | – | The user's first name. |
| groups | array | – | An array of group/team objects the user belongs to, each containing the team's id and display name. |
| id | string | yes | The unique server-assigned identifier for the user being updated. |
| organization | string | – | The name of the organization the user belongs to, up to 120 characters maximum. |
| photos | array | – | An array of profile picture objects, each specifying a type. |
| preferredLanguage | string | – | The user's preferred language, specified in locale format (e.g., en_US for English). |
| roles | array | – | An array of role objects assigned to the user, each containing role type, value, display name, and primary flag. Cannot be updated if the user is deactivated. |
| userName | string | – | The unique username or login identifier, typically an email address format. |
| userType | string | – | A free-form string indicating the user's license type within the organization (e.g., 'Full'). Cannot be updated if the user is deactivated. |
| value | string | – | The manager ID value. Must be numeric; non-numeric values are ignored by the system. |
No output schema declared.
No examples provided.
update_user_partial Update User ~201
Partially update a user resource by applying SCIM patch operations. Only specified fields are modified; unmodified fields remain unchanged. The user must be an active organization member (not a guest) to be updated.
| Name | Type | Req | Description |
|---|---|---|---|
| Operations | array | yes | Array of patch operations to apply to the user. Each operation specifies an action (Replace, Add, Remove), a target path, and a value. Supports operations for: activation status, display name, user t… |
| id | string | yes | The unique server-assigned identifier for the user being updated. |
| schemas | array | yes | Schema identifier array that designates this request as a SCIM PatchOp. Must include the SCIM patch operation schema. |
No output schema declared.
No examples provided.
What is the com.mcparmory/miro MCP server?
com.mcparmory/miro is an MCP server listed in the public MCP registry as com.mcparmory/miro. Create and manage collaborative boards, items, and diagrams programmatically. This page covers its PyPI package (mcparmory-miro).
Is the com.mcparmory/miro MCP server safe to use?
com.mcparmory/miro scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.mcparmory/miro MCP server expose?
com.mcparmory/miro exposes 176 tools: get_access_token_info, list_audit_logs, update_team_boards_classification_bulk, get_board_data_classification, create_markdown_doc, and 171 more. Their descriptions and schemas cost roughly 26,826 tokens of context every time the server is loaded.
Is the com.mcparmory/miro MCP server still maintained?
com.mcparmory/miro is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.