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.

Query and analysis tools

• get_blueprints: Retrieve a list of all blueprints from Port.
• get_blueprint: Retrieve information about a specific blueprint by its identifier.
• get_entities: Retrieve all entities for a given blueprint.
• get_entity: Retrieve information about a specific entity.
• get_scorecards: Retrieve all scorecards from Port.
• get_scorecard: Retrieve information about a specific scorecard by its identifier.
• describe_user_details: Get information about your Port account, organization, and user profile details.
• search_port_docs_sources: Search through Port documentation sources for relevant information.
• ask_port_docs: Ask questions about Port documentation and get contextual answers.

Action execution tools

• run_<action_identifier>: Execute any action you have permission to run in Port.

AI agent tools

• invoke_ai_agent: Invoke a Port AI agent with a specific prompt.

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.

All Developer tools Builders have access to all the tools available to Developers (listed above), plus the additional management tools below.

Blueprint management tools

• create_blueprint
• update_blueprint
• delete_blueprint

Entity management tools

• create_entity
• update_entity
• delete_entity

Scorecard management tools

• create_scorecard
• update_scorecard
• delete_scorecard

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

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.