NeuralTrust has been recognized by Gartner → Read more

Connect Port MCP to your AI agents, securely.

One secured endpoint for every Port call your AI agents make, scoped per user, inspected, and logged.

Select the tools your AI agents can call

52 tools from the Port MCP schema.

Showing 52 tools

  • list_actionsreadLists actions and automations. Without identifiers it returns a summary; with identifiers it returns full details including complete input schemas.
  • list_workflowsreadLists workflows. With identifiers it returns full details including trigger configuration and node definitions.
  • list_self_service_triggersreadLists the self-service workflow triggers the caller can execute, with the trigger node identifier and input schema for each.
  • get_action_permissionsreadReturns the permissions and approval configuration for actions.
  • get_workflow_runreadReturns the status and details of a workflow run, including per-node execution details and timestamps.
  • track_action_runreadTracks the execution status of an action run.
  • submit_input_node_responsewriteSubmits a response to a workflow input node waiting for input, on behalf of the current user. Only responders on the node can submit.
  • trigger_runhigh riskTriggers a self-service workflow or action run and returns the run identifier and status. It covers both workflow and action runs.
  • run_actionhigh riskExecutes a self-service action or automation by identifier. Which actions it may reach can be constrained with the x-allowed-actions-to-run header.
  • upsert_actionhigh riskCreates an action if it does not exist, or updates it if it does.
  • upsert_workflowhigh riskCreates a workflow if it does not exist, or updates it if it does.
  • update_action_permissionshigh riskUpdates an action's permissions configuration, changing who is allowed to run it and what approval it requires.
  • delete_actionhigh riskDeletes an action by identifier.
  • delete_workflowhigh riskDeletes a workflow by identifier.
  • list_blueprintsreadLists blueprints. With identifiers it returns full details including property definitions, schemas and enum values.
  • list_entitiesreadQueries entities from a blueprint with filtering, sorting, pagination and includes, supporting groupBy for value distribution and countOnly for a total.
  • simulate_blueprint_permissionsreadSimulates blueprint entity permissions for a user, either listing the entities they can access or checking one specific entity.
  • upsert_entitywriteCreates an entity if it does not exist, or updates it if it does, merging by default to preserve existing fields.
  • trigger_auto_discoverywriteStarts auto-discovery to suggest or find entities for a blueprint, with optional user context and excluded blueprints.
  • upsert_blueprinthigh riskCreates a blueprint if it does not exist, or updates it if it does, reshaping the schema integrations and scorecards depend on.
  • delete_entityhigh riskDeletes an entity, optionally along with its dependents.
  • delete_blueprinthigh riskDeletes a blueprint and all of its entities.
  • search_audit_logsreadSearches entity audit logs with structured filters for status, operation, trigger origin, date, errors and related resources.
  • list_integrationsreadLists integrations. With identifiers it returns full details including the complete mapping configuration. An empty result is authoritative.
  • get_integration_kinds_with_examplesreadReturns the kinds of data an integration ingests, along with raw data examples for each kind.
  • get_integration_sync_metricsreadReturns sync metrics for an integration, including status and items handled in each pipeline phase with per-kind statistics.
  • get_integration_event_logsreadFetches event logs for an integration, defaulting to error level, with filters for levels, event ID, ETL phases and kinds.
  • test_integration_mappingwriteTests an integration mapping against raw data examples, validating it and returning the mapped results or error messages without committing.
  • get_sidebarreadReturns the software catalog sidebar structure with all pages and folders.
  • get_pagereadReturns a page by identifier with its full widget configuration, and for entity pages the tabs with their widgets and layout.
  • load_widget_schemareadReturns the JSON schema for a dashboard widget type, to be called before creating or updating a widget.
  • list_pluginsreadLists the plugins uploaded to the organization, including metadata and the custom parameters used by custom widgets. Requires Port admin permissions.
  • list_available_library_pluginsreadLists the plugins in the Port Plugins library, the curated catalog from the public repository, each with readme content and catalog prerequisites.
  • duplicate_pagewriteDuplicates a dashboard page with the same widgets, layout, filters, icon and description. Entity pages cannot be duplicated.
  • move_pagewriteMoves a page to a different location in the sidebar, inside a folder or at the root, with control over its position.
  • upsert_dashboard_pagewriteCreates or updates a dashboard or home page with widgets, layout and optional page filters.
  • upsert_widgetwriteCreates or updates a single widget on a dashboard, home or entity page, which is preferred over rewriting a whole entity page.
  • upsert_sidebar_folderwriteCreates or updates a folder in the sidebar, optionally nested under a parent folder.
  • update_entity_pagewriteUpdates an existing entity page's tabs, tab order, names, metadata or filters. Entity pages are auto-generated per blueprint and cannot be created manually.
  • delete_widgethigh riskDeletes a widget from a dashboard, home or entity page by its ID.
  • delete_sidebar_folderhigh riskDeletes a folder from the sidebar. The pages and nested folders inside it are deleted too.
  • install_library_pluginhigh riskInstalls a plugin from the Port Plugins library into the organization, after verifying catalog prerequisites. It puts custom widget code into the portal.
  • upsert_pluginhigh riskCreates or updates a plugin for custom widgets from a built plugin artifact. Requires Port admin permissions.
  • list_scorecardsreadLists scorecards. With identifiers it returns full details including complete rule configurations.
  • upsert_scorecardhigh riskCreates or updates a scorecard, changing the organization's definition of a standard for every service measured against it.
  • delete_scorecardhigh riskDeletes a scorecard, removing the measurement rather than failing it.
  • list_external_interface_appsreadLists the external interface apps registered for the organization, which are public OAuth clients using PKCE. Requires organization admin.
  • upsert_external_interface_apphigh riskCreates or updates an external interface app, a public PKCE OAuth client with no client secret, so a custom UI can be built against Port's API. Requires organization admin.
  • revoke_external_interface_apphigh riskPermanently deletes an external interface app registration. Any UI built against it immediately loses the ability to authenticate. Requires organization admin.
  • describe_user_detailsreadDescribes the connected user, the organization they belong to and the teams they are a member of.
  • load_skillreadLoads specialized guidance for a domain-specific task, giving step-by-step instructions for common workflows before the agent starts.
  • search_port_knowledge_sourcesreadSearches the official Port documentation and returns the most relevant sections with their URL and content in markdown.

What Port MCP exposes

Port MCP groups its 52 tools into 8 categories, each with a suggested starting policy.

All 52 tools as JSON, ready to paste.

CategoryCoversAccessSuggested policy
Pages & DashboardsReading the catalog sidebar and individual pages with their widget configuration, widget JSON schemas, creating and updating dashboard pages, widgets, sidebar folders and entity page tabs, duplicating and moving pages, deleting widgets and folders, and listing, installing and upserting plugins for custom widgetsRead / Writedelete_sidebar_folder takes the pages and nested folders inside it with it. install_library_plugin and upsert_plugin put custom widget code into the portal and need Port admin permissions, so treat them as code deployment rather than configuration
Actions & WorkflowsListing actions, automations, workflows and the self-service triggers the caller can execute with their input schemas, triggering a workflow or action run, tracking its status and per-node details, submitting a response to a waiting input node, creating, updating and deleting actions and workflows, and reading or updating action permissionsRead / Writerun_action and trigger_run execute the organization's real self-service actions, which provision infrastructure and deploy. Constrain them with the x-allowed-actions-to-run header rather than relying on tool-level approval, and gate update_action_permissions separately since it changes who may run what
Data ModelListing blueprints with their property definitions and schemas, querying entities with filtering, grouping and counts, simulating a user's entity permissions, triggering auto-discovery of entities for a blueprint, and creating, updating or deleting blueprints and entitiesRead / Writedelete_blueprint removes the blueprint and all of its entities. upsert_blueprint reshapes the schema every integration and scorecard depends on, so a change here propagates further than the object it names
IntegrationsListing integrations with their full mapping configuration, the kinds of data each ingests with raw examples, sync metrics across extract, transform, load and delete phases, event logs defaulting to errors, and testing a mapping against raw dataRead / Writetest_integration_mapping validates without committing, which makes it the safe way to iterate on a mapping. An empty result from list_integrations is authoritative, so do not infer installation from existing blueprints
External InterfacesListing the external interface apps registered for the organization, creating or updating one as a public PKCE OAuth client with no client secret, and permanently revoking a registrationRead / WriteThese create and destroy OAuth clients. Revoking one immediately removes any custom UI's ability to authenticate, and both writes require organization admin permissions, so they belong behind a named human approval
GeneralDescribing the connected user, their organization and team memberships, loading a specialized skill with step-by-step guidance for a domain task, and searching official Port documentation with the content returned in markdownReadRead-only. load_skill shapes how the agent then uses the write tools, so what it loads is upstream of the actions it takes, and worth logging alongside the tool calls that follow
ScorecardsListing scorecards with their complete rule configurations, creating or updating a scorecard, and deleting oneRead / WriteA scorecard is the organization's definition of a standard, so editing one changes what compliant means for every service measured against it. Deleting one removes the measurement entirely rather than failing it
Audit LogsSearching entity audit logs with structured filters for status, operation, trigger origin, date, errors and related resources, with pagination and optional response fieldsReadRead-only and the record of what changed in the catalog and who changed it. Allow it freely: it is how an agent's own earlier writes can be checked after the fact

Connect Port MCP to your AI agent

Four steps, under ten minutes.

  1. 01

    Sign in to NeuralTrust

    Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.

    Sign in to NeuralTrust
  2. 02

    Choose your agent

    When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.

    Choose your agent
  3. 03

    Connect Port

    Find Port in the tool list and connect it.

    Connect Port
  4. 04

    Connect your agent

    Follow the steps on screen to add the config to your agent, then send the test prompt.

    Connect your agent

Permissions down to the single tool

You do not allow Port MCP or block it. You allow the exact tools each agent can call, one by one.

Port MCP52 TOOLS AVAILABLE
Code review agent4 tools, read only
Issue triage bot9 tools
Platform team assistantall 52 tools
  • Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
  • Default denyA tool you have not enabled is never exposed to the agent.
  • Approval on writesTools that change or delete things can require a human to confirm.

Is Port MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.NeuralTrustApply controls based on your configuration.Port MCP52 tools in the Builder set; the Developer set is a read-and-execute subset of around twenty, and which tools appear depends on the caller's Port permissions. Two headers control the surface: x-read-only-mode set to 1 hides every write tool from the listing, and x-allowed-actions-to-run takes a comma-separated allowlist of action identifiers that run_action may execute, with an empty string allowing none.
Coding assistantsConnection & credentialsper userPages & Dashboards15 tools
Internal copilotsTool access policiesdeny by defaultActions & Workflows14 tools
Workflow automationsRequest & response inspectioninlineData Model8 tools
Compatible MCP clientsActivity monitoringalerts and logsAll other tools15 tools
FAQ

Common questions about running Port MCP through TrustGate.

Connect Port MCP instantly

Pick the tools, point your agent at TrustGate, and Port MCP is live: scoped, inspected, logged.