Skip to main content
Contentstack MCP profile hub is in general availability!
ChatGPT Image Jun 17, 2026, 03_32_00 PM.png

Add one URL to your client

Profile Hub runs at a single address. Add it to your client as a remote MCP server.

https://mcp-profile-hub.contentstack.com/api/mcp
  1. Add the URL to your AI client.
  2. Pick your region and sign in to Contentstack.
  3. Choose a profile and, if it needs one, a stack.

You do not install anything or paste an API key. Your client lists the profile's tools once sign-in completes. Steps for each client are in the docs, or use the form on the right to build a ready-made install command.

Or configure your MCP here

Optionally create a pre-configured MCP URL here. This way you can connect your stack, brandkit, or launch projects directly in the URL.

Optional configuration

Leave a field blank to keep the stack default. Blank values are left out of the URL.

MCP related writing on our engineering blog

All posts
ai-generated-build-context-aware-mcps-not-api-wrappers-1770908929372.png
BLOG

Build context-aware MCPs, not API wrappers

Discover why simply wrapping APIs isn't enough for Model Context Protocol (MCP) servers. Learn how adding project and user context can transform MCPs into dynamic, efficient engines that enhance AI reasoning, reduce errors, and scale across complex environments.

aiapimcp
cttibncdlwrwxeozwqbj.jpg
BLOG

MCP fragmentation, context efficiency, and the rise of curated skills

This article explores the fragmentation of the Model Context Protocol (MCP) in the AI ecosystem, highlighting challenges with context window efficiency, the complexity developers face, and emerging solutions like curated tool subsets and Claude Skills. It offers insights into protocol-layer issues, strategies for improving reliability, and the pragmatic necessity for adaptable system architectures amid ongoing standards wars.

aiautomationopinion
AI will not live in one place, but trust has to
BLOG

AI will not live in one place, but trust has to

This article discusses the tension between rapidly expanding enterprise AI capabilities and the need for strong governance, introducing a two-layer architecture: off-platform AI for experimental reach and on-platform AI for trusted, governed execution. It explains how combining both layers allows organizations to benefit from flexible, distributed AI while maintaining oversight, brand integrity, and risk management.

aimcpagent skills...
We don't test our MCP profiles. We test the agent.
BLOG
Level: Advanced

We don't test our MCP profiles. We test the agent.

How we test MCP Profile Hub for AI agents: a deterministic tool matrix plus behavior evals for grounding, safety, and correct tool use, gated on every change.

mcpautomation

What your agent can do

Across the Contentstack APIs and products, an agent connected through a profile can:

  • Read, create, update, publish and unpublish entries and assets in plain language.
  • Inspect audit logs, version history and workflow stages.
  • Trigger Launch deployments, check logs and revalidate the CDN cache.
  • Draft copy in an approved brand voice with Brand Kit.
  • Review audiences, experiences and experiment results in Personalize and Lytics.
  • Manage Marketplace apps and OAuth settings in Developer Hub.
  • Pull API usage and cache performance from Analytics.

What it can actually do depends on the profile. A read-only profile cannot publish.

Build a profile for your team

When no system profile fits, build your own in the MCP Profile Hub Marketplace app. Pick the tools a job needs from the catalog, connect the stack, and copy the install snippet. That is three steps: tool selection, configuration, installation.

The connector URL is safe to share. Identity comes from each person's own sign-in, so a shared profile never gives anyone extra access.

Your Automate workflows and Agent OS agents with an HTTP trigger show up as tools too. One call can run a whole workflow.

Build a custom profile

Moving from the @contentstack/mcp package

Profile Hub replaces the local @contentstack/mcp package. Both cover the same products. They differ in how you install them and how many tools your agent ends up with:

@contentstack/mcp package

MCP Profile Hub

Installation

Runs locally via npx, configured per machine with credentials or an OAuth session

Hosted at mcp-profile-hub.contentstack.com. Nothing to install, add a URL to your client

Transport

stdio, so it only works in clients that can run a local process

Streamable HTTP, so it also works in browser-based clients like claude.ai and ChatGPT

Tool selection

Tool groups (cma, launch, and so on). Each group loads its full toolset, up to 77 tools for CMA alone

Curated per profile. You expose exactly the tools a job needs, nothing more

Your permissions stay yours

Profile Hub signs you in with standard OAuth 2.1 and PKCE. There are no API keys to paste, share or rotate. Every call runs with your own Contentstack roles, so a profile can narrow what you can do but never widen it.

Every tool call is logged. The Executions view in the Marketplace app shows the status, tool, timing and any error for each call.

Frequently asked questions

  • Do I need to install the Marketplace app?

    No. The public URL works on its own. You need the app to build custom profiles, save configuration or review executions.

  • Do I need an API key?

    No. You sign in through the browser with OAuth.

  • Is the connector URL a secret?

    No. profile_id and org_uid are identifiers. A stack API key on the URL does not grant access without your sign-in.

  • Can a shared profile give someone extra access?

    No. Each person connects with their own login and roles.

  • How is this different from the @contentstack/mcp package?

    The package runs locally over stdio and loads full tool groups. Profile Hub is hosted, uses Streamable HTTP and exposes only the tools a profile needs.

  • How do I switch profile or stack?

    Change the URL parameters, or remove the server from your client and add it again to choose new ones at sign-in.