Available tools

The Port MCP Server exposes different sets of tools based on your role and use case. The tools you see will depend on your permissions in Port.

Developer

Developers are typically users who consume and interact with the developer portal - querying services, running actions, and analyzing data. These tools help you get information and execute approved workflows.

Actions & workflows7 tools

get_action_permissions

Get permissions/approval config for actions.

get_workflow_run

Get the status and details of a workflow run by its identifier. Use after trigger_workflow_run to poll for completion, or to inspect any previously-triggered run. Returns status, result, per-node execution details, and timestamps. API Reference

list_actions

List actions in your organization. Without identifiers, returns a summary list. With identifiers, returns full action details including complete input schemas.

list_workflows

List workflows in your organization. Without identifiers, returns a summary list. With identifiers, returns full workflow details including trigger configuration and node definitions. API Reference

run_actionDynamic

Execute any action you have permission to run in Port. Provide the action identifier and inputs to run the action. This unified tool handles all actions in your organization, reducing the total number of tools available. API Reference

track_action_run

Track action execution status.

trigger_workflow_run

Trigger a self-service workflow run by its workflow identifier. Accepts optional input parameters matching the workflow's trigger schema. Returns the workflow run identifier and status so you can track progress. API Reference

Data model3 tools

list_blueprints

List blueprints in your organization. Without identifiers, returns a summary list. With identifiers, returns full blueprint details including property definitions, schemas, and enum values. API Reference

list_entities

Query entities from a blueprint with filtering, sorting, and pagination. Supports identifiers for specific entities, groupBy for value distribution, and countOnly for counting without retrieving data. API Reference

simulate_blueprint_permissions

Simulate blueprint entity permissions for a user. Use list mode to return entities the user can access for a blueprint; use detail mode with entityIdentifier to check permissions for a specific entity. API Reference

General3 tools

describe_user_details

Describe the user, which organization he is connected to and what teams he is a member of and more information regarding the user. Can be useful for questions that relate to the user or when looking up for related entities to the user API Reference

load_skill

Load specialized guidance for a domain-specific task. Skills provide step-by-step instructions for common workflows like troubleshooting integrations. Load a skill before starting a specialized task to ensure consistent, thorough handling. Documentation

search_port_knowledge_sources

Search the official Port documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Port knowledge.

Pages & dashboards3 tools

get_pageBeta

Get a specific page by identifier. Returns full page details including widgets configuration. API Reference

get_sidebarBeta

Get the software catalog sidebar structure including all pages and folders. API Reference

load_widget_schemaBeta

Get the JSON schema for a specific dashboard widget type. Call this before upsert_dashboard_page or upsert_widget to understand the required structure for the widget you want to create.

Scorecards1 tool

list_scorecards

List scorecards in your organization. Without identifiers, returns a summary list. With identifiers, returns full scorecard details including complete rule configurations. API Reference

Builder

Builders are platform engineers or admins who design and configure the developer portal - creating blueprints, setting up scorecards, and managing the overall structure. These tools help you build and maintain the portal.

Builders have access to all the tools available to Developers, plus additional management tools for creating and configuring the portal.

Actions & workflows12 tools

delete_action

Delete action by identifier.

delete_workflow

Delete workflow by identifier. API Reference

get_action_permissions

Get permissions/approval config for actions.

get_workflow_run

Get the status and details of a workflow run by its identifier. Use after trigger_workflow_run to poll for completion, or to inspect any previously-triggered run. Returns status, result, per-node execution details, and timestamps. API Reference

list_actions

List actions in your organization. Without identifiers, returns a summary list. With identifiers, returns full action details including complete input schemas.

list_workflows

List workflows in your organization. Without identifiers, returns a summary list. With identifiers, returns full workflow details including trigger configuration and node definitions. API Reference

run_actionDynamic

Execute any action you have permission to run in Port. Provide the action identifier and inputs to run the action. This unified tool handles all actions in your organization, reducing the total number of tools available. API Reference

track_action_run

Track action execution status.

trigger_workflow_run

Trigger a self-service workflow run by its workflow identifier. Accepts optional input parameters matching the workflow's trigger schema. Returns the workflow run identifier and status so you can track progress. API Reference

update_action_permissions

Update action permissions configuration.

upsert_action

Create or update an action. Updates if the action exists, creates if it does not.

upsert_workflow

Create or update a workflow. Updates if the workflow exists, creates if it does not.

Data model8 tools

delete_blueprint

Delete blueprint and all its entities. API Reference

delete_entity

Delete entity with optional dependents. API Reference

list_blueprints

List blueprints in your organization. Without identifiers, returns a summary list. With identifiers, returns full blueprint details including property definitions, schemas, and enum values. API Reference

list_entities

Query entities from a blueprint with filtering, sorting, and pagination. Supports identifiers for specific entities, groupBy for value distribution, and countOnly for counting without retrieving data. API Reference

simulate_blueprint_permissions

Simulate blueprint entity permissions for a user. Use list mode to return entities the user can access for a blueprint; use detail mode with entityIdentifier to check permissions for a specific entity. API Reference

trigger_auto_discovery

Start auto-discovery to suggest or find entities for a blueprint. Call list_blueprints first to obtain the exact blueprint identifier before invoking this tool. Supports optional user context and excluded blueprints as supported by the tool. API Reference

upsert_blueprint

Create or update a blueprint. Updates if the blueprint exists, creates if it does not. API Reference

upsert_entity

Create or update an entity. Updates if the entity exists, creates if it does not. Uses merge by default to preserve existing fields. API Reference

General3 tools

describe_user_details

Describe the user, which organization he is connected to and what teams he is a member of and more information regarding the user. Can be useful for questions that relate to the user or when looking up for related entities to the user API Reference

load_skill

Load specialized guidance for a domain-specific task. Skills provide step-by-step instructions for common workflows like troubleshooting integrations. Load a skill before starting a specialized task to ensure consistent, thorough handling. Documentation

search_port_knowledge_sources

Search the official Port documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Port knowledge.

Integrations5 tools

get_integration_event_logs

Fetch event logs for an integration. Supports pagination to read logs page by page. You can paginate by using the timestamp and log_id from the previous response. API Reference

get_integration_kinds_with_examples

Fetch all kinds (data types) that an integration ingests, along with raw data examples for each kind. For example, a GitHub integration might have kinds like "pull_request", "issue", and "repo".

get_integration_sync_metrics

Fetch sync metrics for an integration. Returns detailed metrics including status, number of items handled in each phase of the integration pipeline (extract, transform, load, delete), and per-kind statistics. API Reference

list_integrations

List integrations in your organization. Without identifiers, returns a summary list. With identifiers, returns full integration details including complete config with mapping configuration. Empty result is authoritative: no integrations are installed. Do not infer prior installation from existing blueprints. API Reference

test_integration_mapping

Test an integration mapping against raw data examples. Validates the mapping, checks for errors, and returns the mapped results or error messages.

Pages & dashboards11 tools

delete_sidebar_folderBeta

Delete a folder from the sidebar. Pages inside the folder are moved to the sidebar root. API Reference

delete_widgetBeta

Delete a widget from a dashboard or home page by its ID. API Reference

get_pageBeta

Get a specific page by identifier. Returns full page details including widgets configuration. API Reference

get_sidebarBeta

Get the software catalog sidebar structure including all pages and folders. API Reference

load_widget_schemaBeta

Get the JSON schema for a specific dashboard widget type. Call this before upsert_dashboard_page or upsert_widget to understand the required structure for the widget you want to create.

move_pageBeta

Move a page to a different location in the sidebar. Use "parent" to place the page inside a folder (or null for sidebar root) and "after" to control its position within that level. API Reference

upsert_dashboard_pageBeta

Create or update a dashboard page with widgets and layout. The dashboard-widget container is auto-generated. Use load_widget_schema to get the schema for a specific widget type before building widgets. API Reference

upsert_sidebar_folderBeta

Create or update a folder in the sidebar. Folders can be nested by specifying a parent folder identifier. Use "after" to control position. API Reference

upsert_widgetBeta

Create or update a widget on a dashboard or home page. If a widget with the given ID exists it will be updated, otherwise a new one is created. Call load_widget_schema first to get the full schema for the target widget type. API Reference

list_plugins

List plugins uploaded to your organization (Port admin permissions required). Without identifiers, returns a summary list. With identifiers, returns full plugin details including metadata and custom parameters used by custom widgets. API Reference

upsert_plugin

Create or update a plugin for custom widgets (Port admin permissions required). Updates if the plugin identifier exists, creates if it does not. Use after you have a built plugin artifact and metadata (for example identifier, title, optional params). Documentation

Scorecards3 tools

delete_scorecard

Delete scorecard by identifiers. API Reference

list_scorecards

List scorecards in your organization. Without identifiers, returns a summary list. With identifiers, returns full scorecard details including complete rule configurations. API Reference

upsert_scorecard

Create or update a scorecard. Updates if the scorecard exists, creates if it does not. API Reference

Client Support

Tool support in external MCP clients depends on whether the client implements the tools feature according to the MCP specification. Most MCP clients support tools. Check the MCP client documentation to see which features your client supports.

Select which tools to use

By default, when you open a chat with Port MCP, all available tools (based on your permissions) are loaded and ready to use. However, you can customize which tools are available if you want to focus on specific workflows.

For example, if you only want to query data from Port without building or modifying anything, you can limit the tools to just the read-only ones. This helps reduce complexity and ensures you don't accidentally make changes.

Using headers to control tool availability

You can use headers when configuring your MCP server connection to control which tools are available:

Read-only mode - The x-read-only-mode header controls whether write tools are available. Set it to 1 to restrict the MCP server to only expose read-only tools, completely hiding write tools from the available tools list. Set it to 0 (default) to allow all tools based on your permissions.

Control actions - The x-allowed-actions-to-run header controls which actions are available through the run_action tool. This header accepts a comma-separated list of action identifiers. Only the specified actions will be available. If the header is not specified, all actions you have permission to run will be available. If set to an empty string, no actions will be allowed to run.

Examples:

• x-allowed-actions-to-run: "create_github_issue,create_incident" - Allows only the specified GitHub and incident actions.
• x-allowed-actions-to-run: "create_service,deploy_to_production" - Allows only the specified deployment actions.
• x-allowed-actions-to-run: "" - No actions will be allowed to run.

See the token-based authentication guide for examples of how to configure these headers.

Using client UI to select tools

Cursor

In Cursor, you can customize which tools are available through the UI after connecting to Port MCP. Once connected, you can select specific tools as shown below.

VSCode

In VSCode, you can choose the tools through the UI after connecting to Port MCP.

Claude

When creating a custom connector in Claude, you can specify exactly which tools to expose instead of enabling everything.

Refer to the Claude custom connector documentation for detailed instructions.