Contentstack MCP profile Hub gives teams a practical way to bring AI into their Contentstack workflows. Create focused profiles for specific jobs, connect them to the AI tools your team already uses and keep access aligned with existing Contentstack permissions.
We’re excited to announce MCP Profile Hub, a new way to work with Contentstack with the AI tools your team has already implemented, including Claude, ChatGPT, Cursor and VS Code.
Why AI access needs more context
The Model Context Protocol (MCP) is quickly becoming a common way for AI agents to connect with the tools and systems people use every day.
Connecting an AI tool to Contentstack can unlock a lot of useful workflows. An agent can look up entries, inspect content models, check publishing status, support asset management and more. The challenge comes when an agent has access to all of those capabilities at once.
For developers working on their own, having access to a broad set of tools can be useful. But for a larger team, it can make AI harder to use and more difficult to govern.
A few challenges we’ve seen:
- Too many tools can slow things down. When an agent has a large number of tools available, it has more decisions to make. That can affect accuracy, increase context usage and make simpler models less effective.
- The tools need to understand your Contentstack setup. Your content models, locales, branches and environments are specific to your organization. Generic API access doesn’t provide that context automatically.
- Teams need clear boundaries. An AI agent should only be able to perform the tasks someone is already authorized to do, with a record of what happened.
That’s where MCP Profile Hub comes in.
Meet MCP Profile Hub
MCP Profile Hub is a Contentstack Marketplace app for creating profiles, which are focused collections of Contentstack tools designed around a particular job or workflow.
You choose the tools a profile should have access to, then connect that profile to an MCP-compatible AI tool. Each person using the profile signs in with their existing Contentstack account, so their Contentstack roles continue to determine what they can actually access.
For example, you could create a profile for a:
- Regional publishing team that needs to review and publish content in specific environments
- Content operations team that regularly audits entries and checks publishing status
- Campaign team preparing content for a product launch
- Developer who wants Contentstack context directly in their IDE
Profiles are intentionally focused. An AI Agent only sees the tools that have been included in the profile, which gives it a smaller and more relevant set of capabilities to work with.
Profiles also take your Contentstack environment into account, including your content models, locales, branches and environments.
How it works
Setting up a profile takes three steps.
1. Build a profile for a specific job
Use the guided workflow in the MCP Profile Hub to select the Contentstack tools you want to make available. The OAuth scopes needed for those tools are handled automatically, so there’s no need to configure them manually.
You can create as many profiles as you need for different teams, workflows or use cases.
2. Connect your AI assistant
Each profile gets its own hosted endpoint. Add that endpoint to an MCP-compatible tool such as Claude, ChatGPT, Cursor, VS Code, Claude Code or a terminal-based agent.
When you connect, you sign in through OAuth with your Contentstack account. There are no API keys to copy into configuration files or distribute across your team.
3. Start working in the tools you already use
Once connected, your AI assistant can work with the Contentstack capabilities included in the profile.
Depending on the tools you selected, that could mean finding entries, checking publish status, inspecting content models, working with assets or publishing content to approved environments.
You can also start with one of the ready-to-use system profiles included with MCP Profile Hub:
- Asset Librarian
- Content Explorer
- Content Modeler
- Campaign Go-Live
- Broken Reference Checker
Choose a stack, connect your AI tool and you can start experimenting without building a profile from scratch.
Built with governance in mind
Giving AI access to business systems requires more than connecting an endpoint. MCP Profile Hub uses the permissions and authentication your team already relies on in Contentstack.
Permissions follow the user
A profile can restrict what someone can do, but it cannot give them permissions they don’t already have in Contentstack. If someone doesn’t have access to a particular environment or action, connecting to a profile doesn’t change that.
OAuth keeps authentication simple
Profiles use OAuth to authenticate users, with short-lived tokens rather than shared API keys. Your team doesn’t have to manage credentials across different AI assistants or store sensitive keys in configuration files.
Actions are logged
MCP Profile Hub keeps an audit trail of activity within the app, including who performed an action, which tool was used, the result, the permission outcome and when it happened.
Who MCP Profile Hub is for
MCP Profile Hub can support different teams depending on how they use Contentstack and AI.
- Content editors can use focused profiles to look up content and complete approved tasks from the AI tools they already use.
- Developers can bring Contentstack context into their IDE or terminal, making it easier to work with content models, entries and other platform capabilities while they build.
- Content operations teams can create profiles around repeatable workflows, such as content audits, publishing checks or campaign preparation.
- Admins can give teams access to specific Contentstack capabilities while keeping existing user permissions and an audit trail in place.
What's next
We’re continuing to expand what teams can do with MCP Profile Hub. That includes deeper connections with other parts of the Contentstack platform, including Automate and Agent OS.
As these capabilities come together, profiles can become a foundation for more sophisticated AI-assisted workflows across Contentstack. We’ll share more as those capabilities develop.
Get started
MCP Profile Hub is available now in the Contentstack Marketplace.
To try it:
Install MCP Profile Hub from the Marketplace.
- Choose a ready-made system profile or create your own using the guided workflow.
- Connect the profile to your preferred AI tool, sign in with OAuth and start asking it to work with your Contentstack data.
- A simple first prompt is: “List the assets in my stack.”
For setup instructions and the complete tool catalog, visit the MCP Profile Hub documentation.
We’re looking forward to seeing how teams use MCP Profile Hub to bring Contentstack into the AI workflows they’re already building.
