Feature ideas

At the moment you cannot run additional filters on calculation property. This makes creating widgets or charts impossible for those properties.

Current limitation The Port MCP server supports blueprints, entities, actions, and scorecards. It does not support pages or dashboards. As a result, AI agents such as Claude Code, Cursor, and Windsurf cannot create, update, or delete dashboard pages or widgets programmatically through the MCP interface. Use case We built a Claude usage analytics pipeline that syncs data into a Port blueprint. The goal was to create a dashboard with KPI cards, pie charts, and table widgets directly from Claude Code via the MCP server. We had to fall back to raw REST API calls, which proved brittle. During implementation we encountered undocumented constraints such as: • Maximum of two dashboard widget sections • agentIdentifier requirements • Other implicit validation rules Requested capabilities Page management • create_page to manage dashboard and catalog pages • update_page to modify existing pages • delete_page to remove pages • list_pages to discover existing pages and widget configurations Widget management • add_widget to add widgets to a page • update_widget to modify widgets • remove_widget to delete widgets Widget support • Number charts • Pie charts • Table explorers • Markdown blocks • Iframe widgets • Links Why this matters As more teams use AI agents to build and maintain internal developer portals, programmatic dashboard composition becomes essential. The REST API exists but is not exposed through MCP. The API also has undocumented limitations that make it harder to use reliably. Exposing page and widget management through MCP would enable stable, fully automated dashboard generation workflows.

Please add the ability to generate a time-series trend line chart based directly on the historical count of entities matching a custom filter. We would like to be able to: Select an entity type (e.g., Service Entity). Apply a custom filter (e.g., entities with a specific property indicating they are onboarded). Plot the total count of those filtered entities over time. This feature would allow us to easily track system adoption rates without having to build and maintain dedicated aggregation properties on parent entities just for reporting purposes.

The ability to create personal dashboards without the admin needed to modify the permissions only to me

Port today display date properties in a relative format, e,g, Last 3 months. Allow controlling the display format of specific date properties.

Let users upload or paste images in the Markdown widget.

The multi-line chart widget currently concatenates the line title (display name / legend label) with the property name to form the legend label. When the property title is already descriptive and self-explanatory, this concatenated format (for example, "Deployments — avg_cost") adds unnecessary noise instead of improving clarity. In a lot of cases, the label gets truncated. Users should have the option to display only the line/property title as the label when the full concatenated format is not needed.

We’d like a native, end‑user “favorites” capability in Port so each user can quickly access what they use most, without navigating the full catalog or self‑service hub every time. What we’re asking for Let a logged‑in user mark as favorite: Self‑service actions Specific entities (e.g., services, workloads, resources) Optionally, blueprints or pages Provide a personal favorites view/widget in the UI (e.g., on the Home page or a dedicated “Favorites” area) where users can: See all their favorite items in one place Click through directly to run an action or open an entity/page Why current options aren’t enough We know there is a “My recent actions” widget and an open idea for SSA Favorites, but “recent” usage is not the same as letting a user pin a stable set of frequently used actions. [SSA favorites] There is also an idea for favorite entities in Homepage, but this appears focused only on entities and not actions/blueprints, and is not yet generally available. [Favourite entities] The Quick Access / Links widget lets admins curate shared shortcuts to pages, but doesn’t let each user manage their own favorites across actions and entities. [Quick access widget] Value Faster access to commonly used actions and entities, especially for power users. Cleaner experience than searching or navigating long lists every time. Complements existing “recent” and quick‑access features with a true per‑user, persistent favorites experience.

Allow users to build their own interface components as widgets, with Port's catalog context at hand.

To define permissions covering that would cover all underlying pages.