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.Try Port MCP now
What your agents can ask once Port MCP is connected.
Select the tools your AI agents can call
52 tools from the Port MCP schema.
Showing 52 tools
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.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Pages & Dashboards | Reading 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 widgets | Read / Write | delete_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 & Workflows | Listing 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 permissions | Read / Write | run_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 Model | Listing 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 entities | Read / Write | delete_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 |
| Integrations | Listing 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 data | Read / Write | test_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 Interfaces | Listing 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 registration | Read / Write | These 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 |
| General | Describing 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 markdown | Read | Read-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 |
| Scorecards | Listing scorecards with their complete rule configurations, creating or updating a scorecard, and deleting one | Read / Write | A 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 Logs | Searching entity audit logs with structured filters for status, operation, trigger origin, date, errors and related resources, with pagination and optional response fields | Read | Read-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.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Port
Find Port in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
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 MCP | 52 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 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 assistants | Connection & credentialsper user | Pages & Dashboards15 tools |
| Internal copilots | Tool access policiesdeny by default | Actions & Workflows14 tools |
| Workflow automations | Request & response inspectioninline | Data Model8 tools |
| Compatible MCP clients | Activity monitoringalerts and logs | All other tools15 tools |
Use Port MCP with any AI agent framework
Setup guides for the tools your team already uses.
Claude CodeAdd Port MCP to Claude Code from the terminal
CursorUse Port MCP tools inside Cursor's agent
CodexConnect Port MCP to the OpenAI Codex CLI
WindsurfGive Windsurf's Cascade access to Port MCP
Gemini CLICall Port MCP from Gemini CLI prompts
Google AntigravityLet Antigravity agents work with Port MCP
GitHub CopilotUse Port MCP in Copilot agent mode
Claude EnterpriseRoll out Port MCP across your Claude workspace
Microsoft Copilot StudioAdd Port MCP as a tool for Copilot Studio agents
Open WebUIBring Port MCP tools into Open WebUI chats
LangChainLoad Port MCP tools into LangChain agents
HaystackPlug Port MCP into Haystack agent pipelines
Strands AgentsGive Strands agents Port MCP tools
Vercel AI SDKCall Port MCP from Vercel AI SDK apps
n8nUse Port MCP in n8n AI agent workflows
Common questions about running Port MCP through TrustGate.
Other MCP servers
More servers from the catalog.
Rootly
Securely connect your AI agents to Rootly through TrustGate: incidents, alerts, on-call schedules, escalation policies, workflows, services, retrospectives, playbooks and status pages, scoped per agent and logged.
261 toolsViewBuildkite
Securely connect your AI agents to Buildkite through TrustGate: pipelines, builds and jobs, agents, clusters, queues and secrets, cache registries, artifacts, log search and Test Engine, scoped per agent and logged.
56 toolsView)
Atlan
Securely connect your AI agents to Atlan through TrustGate: catalog search and lineage, asset and custom metadata, tags, glossary, domains, quality rules, warehouse queries and knowledge, scoped per agent and logged.
41 toolsViewCube
Securely connect your AI agents to Cube through TrustGate: semantic model search and SQL, agent chat, reports and dashboards, model editing on dev branches, commits and pre-aggregations, scoped per agent and logged.
30 toolsView
Connect Port MCP instantly
Pick the tools, point your agent at TrustGate, and Port MCP is live: scoped, inspected, logged.