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
Builder

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.

list_blueprints

Retrieve all blueprints in your organization. Blueprints are the building blocks that define your data model. The response is compacted, use get_blueprint with specific blueprint for full details, if needed. API Reference

get_blueprint

Get a specific blueprint by its identifier. Returns the complete blueprint configuration. API Reference

list_entities

Search and retrieve entities for a blueprint with advanced filtering, sorting, and pagination options API Reference

get_entities_by_identifiers

Get specific entities by their identifiers within a blueprint API Reference

get_scorecards

Retrieve all scorecards. The response is compacted, use get_scorecard with specific scorecard for full details, if needed. API Reference

get_scorecard

Get specific scorecard by identifier API Reference

list_actions

Get all actions. The response is compacted, use get_action with specific action for full details, if needed.

get_action

Get specific action details and input schema

track_action_run

Track action execution status

run_*Dynamic

Execute any action you have permission to run in Port. Dynamically generated for each action available in your organization. API Reference

run_actionDynamicInternal

Run any action dynamically by providing the action identifier and inputs. Used internally by the MCP server and not directly exposed to clients. API Reference

get_action_permissions

Get permissions/approval config for actions

ask_port_docs

Ask a question about Port documentation

search_port_docs_sources

Search for relevant Port documentation sources based on a query

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

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.

create_blueprint

Create blueprints (basic building blocks in Port) API Reference

list_blueprints

get_blueprint

Get a specific blueprint by its identifier. Returns the complete blueprint configuration. API Reference

update_blueprint

Update existing blueprint configuration API Reference

delete_blueprint

Delete blueprint and all its entities API Reference

create_entity

Create new entity for blueprint API Reference

list_entities

Search and retrieve entities for a blueprint with advanced filtering, sorting, and pagination options API Reference

get_entities_by_identifiers

Get specific entities by their identifiers within a blueprint API Reference

update_entity

Update an existing entity. Only the fields provided will be updated. API Reference

delete_entity

Delete entity with optional dependents API Reference

create_scorecard

Create new scorecard for blueprint API Reference

get_scorecards

Retrieve all scorecards. The response is compacted, use get_scorecard with specific scorecard for full details, if needed. API Reference

get_scorecard

Get specific scorecard by identifier API Reference

update_scorecard

Update existing scorecard API Reference

delete_scorecard

Delete scorecard by identifiers API Reference

create_action

Create new action

list_actions

Get all actions. The response is compacted, use get_action with specific action for full details, if needed.

get_action

Get specific action details and input schema

update_action

Update existing action

delete_action

Delete action by identifier

track_action_run

Track action execution status

run_*Dynamic

Execute any action you have permission to run in Port. Dynamically generated for each action available in your organization. API Reference

run_actionDynamicInternal

Run any action dynamically by providing the action identifier and inputs. Used internally by the MCP server and not directly exposed to clients. API Reference

get_action_permissions

Get permissions/approval config for actions

update_action_permissions

Update action permissions configuration

ask_port_docs

Ask a question about Port documentation

search_port_docs_sources

Search for relevant Port documentation sources based on a query

describe_user_details

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.

Cursor
VSCode
Claude

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.

Enabling specific tools in Cursor

Select which tools to use​

Select which tools to use