Projects

Group related assets — MCP servers, agent cards, and REST APIs — into a named project. Projects are org-scoped, so every member of your organization can see and work with them without any extra sharing step.

Overview

A project is a lightweight container that spans asset types. Instead of hunting across the MCP Servers, Agent Cards, and REST APIs lists to find the pieces that make up one initiative, you gather them under a single project and open everything from one place.

Key properties:

• Org-scoped — a project belongs to one organization and is visible to all of its members. There is no per-project access list; sharing within the org is automatic.
• Cross-type — a single project can hold MCP servers, agent cards, and REST APIs together.
• Non-destructive — adding an asset to a project references it; removing it (or deleting the project) never deletes the underlying asset.

Working in the UI

Open Projects in the main navigation (between Dashboard and Design Lab) to:

• Browse your organization’s projects as tiles, each showing how many MCP servers, agent cards, and REST APIs it contains
• Create a new project with a name and optional description
• Open a project to see its assets grouped by type
• Rename or delete a project, or edit its description

Project names are unique within an organization.

On a project’s detail page, assets are grouped into three collapsible sections — REST APIs, MCP servers, and Agent cards — each shown expanded by default. Collapse a section to focus on the others; the layout remembers what you toggle while the page is open. Each asset is shown as its full Design Lab tile — the same card you see in the Design Lab, with its compliance status, type and publish badges, per-environment test-coverage bars, item counts, and created and last-updated dates — carrying the same quick actions: open in the Design Lab, copy its endpoint URL, download its spec, publish to Exchange, and (for REST APIs) convert to an MCP server.

Two distinct removal actions sit at the end of each tile’s toolbar:

• Unlink (remove from project) detaches the asset from this project only. The asset itself is untouched and stays in your organization.
• Delete permanently deletes the underlying asset for your whole organization — the same delete you’d perform from the Design Lab — which also removes it from every project it belonged to. This cannot be undone.

Searching, filtering, and saved views

Each project’s detail page has its own search-and-filter bar so you can narrow a large project down to the assets you care about:

• Search by asset name
• Filter by asset type (MCP server, agent card, REST API) and by status
• Save a view — capture the current search and filters as a named preset, then reapply it later from the Views menu, or Reset back to no filters

Saved views are per project: a view you create inside one project stays with that project and does not appear in another. Views are org-scoped, so any member of your organization sees the same saved views for a given project. Within a single project you can mark one view as the default; different projects keep their defaults independently.

Adding assets to a project

From a project’s detail page, choose Add asset. You can:

• Attach existing assets — select one or more org assets that are not already in the project. Switching between asset types (MCP servers, agent cards, REST APIs) keeps your running selection, so you can add several assets across different types in a single pass.
• Create a new asset — jump to the Design Lab to author a new MCP server, agent card, or REST API, then attach it to the project.

Each asset appears under its type heading as its full Design Lab tile. Use the unlink action to detach an asset from the project — the asset itself remains in your organization — or the delete action to permanently remove the underlying asset org-wide.

Permissions and isolation

Projects and their memberships are protected by row-level security. Reads and writes are scoped to the acting user’s organization, and an asset can only be attached to a project when both belong to the same organization. Assets from other organizations can never be referenced, even by id.

Platform MCP tools

Projects have full parity with the UI through the Platform MCP server, so an agent can manage them programmatically with the same org isolation. The available tools are:

• list_projects — list every project in the organization, each with per-type member counts
• get_project — fetch one project and its members, enriched with each asset’s name, description, and status
• create_project — create a project (names must be unique within the org)
• update_project — rename a project and/or change its description
• delete_project — remove a project and its groupings (the underlying assets are kept)
• add_asset_to_project — attach an existing org asset (MCP server, agent card, or REST API) to a project
• remove_asset_from_project — detach an asset from a project without deleting the asset

Like every Platform MCP tool, these are scoped to the organization resolved from your API key; a project or asset in another organization can never be read or modified.

Scope and limitations

• Projects are v1: they group assets and are shared org-wide. Cross-organization sharing is out of scope.
• There is no per-project access list — visibility is all-or-nothing within the organization.

Next Steps

• MCP Servers — Design the MCP servers you group into projects
• Agent Cards — Author agent cards to include in a project
• REST APIs — Build REST API mocks to add to a project
• Organization & Members — Understand org-scoped visibility

Use projects to keep everything for one initiative — servers, cards, and APIs — in a single org-wide view.