Create a profile

View as Markdown
Intermediate6 min readLast updated November 6, 2026

Overview

Build a profile in the MCP Profile Hub app to give an AI client a scoped set of Contentstack tools. You choose the tools, select the Contentstack projects they run against, and copy the connector URL that you add to the client.

Where to start

Log in to Contentstack and open MCP Profile Hub from the App Switcher. The app opens on the Profiles screen.

Click to enlarge

The app builds a profile through a three-step wizard: tool selection, configuration, and installation. You can start the wizard from the Profiles screen in two ways:

  • Custom profile: start from Step 1: Select tools.
  • System profile: open a ready-made profile from the System profiles section, complete Configuration by selecting a stack, and continue to Installation. You do not select tools.

Prerequisites

Decide the one job this profile should support before you start. See Keep a profile focused. You also need:

  • Access to the MCP Profile Hub Marketplace app in your Contentstack organization. See Installing Apps, or ask a user whose product role permits installing Marketplace apps to install it.
  • At least one Contentstack stack for the profile to operate on.

Step 1: Select tools

In the Tool selection step, you name the profile and choose its tools. The name is the only required field.

  1. On the Profiles screen, click + New Profile.

    Click to enlarge

  2. Enter a Profile name (required) and an optional Description of the job the profile supports.

    Click to enlarge

  3. Under Tools, click Browse catalog.

  4. Select the Contentstack APIs, Automations, or AI agents tab, then a catalog or project on the left, then search or filter within it.

  5. Select the tools this profile should expose, then save your selection with the Add button, which shows the number of tools you selected, for example Add 11 tools.

  6. Click Save & Continue.

Tip If the profile you need already exists in another organization, import it instead of rebuilding it. Export it as JSON from that organization, then import it here.

What the tool browser shows:

  • The browser opens on the Contentstack APIs tab, which lists the Content Management API (CMA) and Content Delivery API (CDA) catalogs among others.
  • The CMA and CMA Extended tools share one row, Content Management.
  • The Automations tab appears when your organization has automations, and its count is the number of automations that qualify as tools. The AI agents tab appears when your organization has agents.

Each tool you add affects sign-in and tool selection.

Contentstack derives the required Open Authorization (OAuth) scopes from your selection. Each extra tool can add scopes to the consent screen at sign-in, and gives the model one more tool to choose from on each request. Select only the tools the job needs, and create a separate profile for unrelated tools.

Warning A profile contains at most 200 tools. The tool browser and the Tool selection step show your count, for example 150 of 200 tools selected, and you cannot save a selection over the cap. Split the work across two profiles before you reach it.

To clear every tool of one catalog from the selection, click Remove all on that catalog's card in the Tool selection step.

Click to enlarge

Additional Resources: For more information on what each catalog contains and where the tabs get their tools, refer to the Profiles and catalogs documentation. For more information on what qualifies an automation or an agent to appear, refer to the Automations and agents as tools documentation.

Step 2: Configure

The Configuration step lists one connection per Contentstack product your tools use. A connection is a dropdown where you select the project that product's tools act on. The wizard requires only Stack. Select a project in each connection your tools need, then click Save & Continue. Contentstack stores only the project ID.

Click to enlarge

The wizard shows a connection only when your tool selection needs it, as the table below shows:

ConnectionRequiredAppears when the profile includes
StackYesCMA, CMA Extended, CDA, or Developer Hub tools
LaunchNoLaunch tools
PersonalizeNoPersonalize tools
Brand KitNoBrandKit tools
AutomateNo, but see Skipping an optional connectionAutomate catalog tools
LyticsNoLytics tools

If none of your tools need a project, the step reports that it needs no connections.

Skipping an optional connection

The Required column in the connection table above shows which connections the wizard requires, not which connections the tools need at run time. The table below gives the outcome per connection:

ConnectionWhen you select no project
PersonalizeThe call fails before it reaches Contentstack, with the No Personalize project selected message
Brand KitThe call fails before it reaches Contentstack, with the No Brand Kit selected message
LyticsThe call fails before it reaches Contentstack, with the No Lytics project selected message
LaunchThe runtime sends the call without a project ID, and Contentstack rejects it
AutomateSame as Launch, unless the call includes a project_uid argument

Warning Select a project in each Personalize, Brand Kit, and Lytics connection that the profile shows.

Delete tools need an explicit project. A delete tool in the Launch or Automate catalog never uses the configured project. Every delete call needs a project_uid argument, even when you select a project here.

The message states the fix. The Brand Kit and Lytics messages follow the same pattern and include their own parameter. Personalize returns the message below:

No Personalize project selected for this profile. Choose a Personalize project in
the MCP Profile Hub configuration, or add personalize_project_uid to the MCP endpoint URL.

URL parameters set the same values. Each connection has a matching connector URL parameter, for example lytics_project_uid for Lytics. See MCP URL parameters.

Step 3: Install

Contentstack now hosts the profile at its own endpoint. The Installation step shows a ready-to-paste snippet for each supported client, plus the raw connector URL. Copy the connector URL, or copy the generated config snippet for your client, then paste it into the client you use. For client-specific steps, follow the matching section in Connect a client to MCP Profile Hub.

Click to enlarge

The wizard has no branch, environment, or locale field. Set those values as connector URL parameters instead, as the example below shows:

https://mcp-profile-hub.contentstack.com/api/mcp?profile_id=<PROFILE_ID>&branch=release-2&environment=production&locale=en-us

If you omit the branch parameter from the connector URL, the runtime runs operations against the stack's default branch. The runtime lists the stack's branches in the tool definitions, so the AI client can specify a different branch on each call.

Edit a profile

Reopen a profile to change its name, description, tools, or connections. The profile_id and connector URL do not change when you edit the profile, so a connected client continues to reach the profile after you edit it.

A connected client keeps its old tool list.

Contentstack does not notify a client that the list changed. The client shows the list it fetched until it reconnects or you refresh it, while calls run against the current profile. A tool you removed therefore fails with Tool not found on a client that has not re-listed.

A catalog can fail to load while you edit a profile.

The wizard then reports the number of saved tools it could not read, in the message below:

<N> saved tools could not be loaded

Either the tool manifests fail to load, or a catalog key changes after you save those tools to the profile. In both cases, Contentstack keeps the tools on the profile, and the tools remain callable. Reload the page to request the manifests again.

Next Steps

  • MCP URL parameters: every connector URL parameter, including branch, environment, and locale, and the rules for combining them.
  • Manage profiles: duplicate, export, import, and delete profiles.
  • Monitor tool calls: confirm the profile's tool calls reach Contentstack.