Port Getting Started
Set up Port and connect it to your coding agent: sign up for a Port account, install Port's MCP server, and optionally the Port CLI. Use when asked to 'get started with Port', 'set up Port', 'connect Port MCP', 'install the Port MCP server', 'how do I use Port from Claude Code/Cursor/VS Code', or before using any other skill in this repo for the first time.
Install
$ agentstack add skill-port-labs-port-skills-port-getting-started ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-port-labs-port-skills-port-getting-started) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Getting started with Port
Every other skill in this repo produces correct Port config either way, but without Port's MCP server connected, you're copying that config in by hand. With it connected, the agent can read your live account and apply changes directly. Do this once, first.
Prerequisites
None. This is the first skill to run.
How to get started
- Sign up for a Port account at app.port.io if
you don't have one yet.
- Find your Port region. Check your Port app's base URL: if it
contains us, you're on the US region; otherwise you're on EU.
| Region | MCP server URL | |---|---| | EU | https://mcp.port.io/v1 | | US | https://mcp.us.port.io/v1 |
- Connect Port's MCP server to your coding agent, using the URL for
your region from the table above:
| Client | How to connect | |---|---| | Cursor | [Install EU](cursor://anysphere.cursor-deeplink/mcp/install?name=port-eu&config=eyJ1cmwiOiJodHRwczovL21jcC5wb3J0LmlvL3YxIn0=) or add an MCP server manually with your region's URL | | Claude (claude.ai / Claude Desktop) | Install from the Claude directory, then enter your region's MCP server URL when prompted | | VS Code | Add port-eu or port-us as an MCP server using the URL for your region | | Claude Code (CLI) | claude mcp add --transport http port-eu https://mcp.port.io/v1 (or port-us / https://mcp.us.port.io/v1) | | Any other MCP-compatible agent | Point it at your region's URL, or follow the manual install docs |
This repo's own .mcp.json already ships both port-eu and port-us servers, so installing this plugin gets you both — disable whichever region doesn't apply to your account.
- Optional: install the Port CLI.
Beyond MCP, it covers day-to-day resource management from the terminal, and port skills sync pulls any skills your org has already configured in Port straight into your coding agent's skill directory.
- Once connected, prefer Port's own tools over guesswork. Every skill
in this repo notes where it can call Port's MCP tools directly (to read live state or apply a change) instead of just handing you config to copy in. If a skill doesn't cover something you need, search Port's documentation from inside the agent with the search_port_knowledge_sources MCP tool rather than guessing.
Common pitfalls
| Symptom | Cause | Fix | |---|---|---| | MCP server added but no Port tools show up | Most agents need a session restart after adding an MCP server | Restart the coding agent | | The Cursor/VS Code install link does nothing when clicked | Some browsers block custom URI schemes by default | Use the manual install docs instead | | claude mcp add command not found | That command is Claude Code's own CLI, not Claude Desktop or claude.ai | Use the Claude directory link for Desktop/claude.ai instead | | Tools work for one teammate but not another | Each person connected to the wrong region's server for their account | Re-check the Port app base URL and connect to that region's server instead |
Quick reference
- Sign up: app.port.io
- MCP server URL (EU):
https://mcp.port.io/v1 - MCP server URL (US):
https://mcp.us.port.io/v1 - Manual install docs: docs.port.io/agent-management/port-mcp-server/installation
- Port CLI: github.com/port-experimental/port-cli
- Search Port's docs from inside a connected agent: the
search_port_knowledge_sourcesMCP tool
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: port-labs
- Source: port-labs/port-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.