Port

io.portPublished by port.ioOfficial publisherv1.0.2Updated Oct 24, 2026

Port.io mcp server

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Port's remote MCP server connects Port.io to an IDE, LLM or agent platform, letting an assistant work with your Port.io environment through OAuth-authenticated,

What you can do
Connect an assistant to a Port.io environment through a hosted remote endpoint, authenticated with OAuth. The manifest lists no tools, so the specific actions available are not described in the supplied material. The README positions it as a secure bridge between Port.io and an IDE, LLM or agent platform. Refer to Port's own documentation for the available capabilities and setup steps.
When to use it
When you use Port.io and want an IDE, LLM or agent platform to reach your Port.io environment through a hosted MCP endpoint rather than a local package. Check Port's documentation first to confirm the available tools fit your task.
Requirements
A remote MCP endpoint at reachable over the network. OAuth authentication is required, so you need a Port.io account and must complete the OAuth authorization flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Port.io environment, so review the scopes and permissions requested during authorization. The supplied material does not describe which tools exist or whether they can read, change or delete data, so confirm this in Port's documentation before connecting.

Installation

In SourceWeft

  1. Open Port in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.port%2FPort/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "port": {
      "type": "http",
      "url": "https://mcp.port.io/v1"
    }
  }
}

README

Port Remote MCP Server

Remote MCP Server that securely connects Port.io with your IDE, LLM, or agent platform of choice.

Documentation

For full documentation, setup guides, and usage instructions, visit:

Port MCP Documentation

Support

  • Documentation: docs.port.io
  • Issues: For bugs or feature requests, please contact Port support or open an issue in this repository

Source: README.md at commit f6937bc

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Port integrations