Skip to main content

Connect skills to your stack

Connect the Contentstack MCP server so skills can create content types, entries and compositions in your stack with your own login. Do it once per editor, before you ask an agent to build anything in the stack.

The example is the team blog, whose stack is in North America.

Prerequisites​

  • The skills installed. See Install the skills.
  • The stack's API key. The agent asks for it once. It reads your organization from your login.
  • Your stack's region. It's one of NA, EU, AU, AZURE_NA, AZURE_EU, GCP_NA or GCP_EU.

What this is and what you get​

The Contentstack MCP server gives skills tools for the Contentstack Management API. They call it with your OAuth login, so you never paste a token into the chat. The skill install-contentstack-mcp sets it up.

Connect the Contentstack MCP server​

  1. Ask your agent: "Install the Contentstack MCP server."

    The agent checks whether the server is already set up in your editor. If it isn't, it asks for your region and offers to set it up.

  2. Run the login command the agent gives you. The login needs your terminal and a browser, so the agent can't run it for you. For the blog's stack in North America, the command is:

    CONTENTSTACK_REGION=NA npx @contentstack/mcp --auth

    In the menu, choose Authorization, then Login, and sign in to Contentstack in the browser window that opens.

  3. Restart your editor, so the agent picks up the server's tools.

  4. Give the agent the blog stack's API key. It reads the stack's content types to prove the connection works, then tells you which skills now run through the server.

Always put the region in the login command. Without it, the login signs in to North America without a warning.

Let skills check Studio in a browser​

To let skills open Studio and your canvas in a browser and check what they see, ask your agent: "Install Playwright MCP." It's optional. Without it, skills ask you to click through a step and tell them what you see.

If it doesn't work​

  • A call fails with a 401 and error_code 105. Your login has expired. It lasts an hour. Run the login command again.
  • A call fails with a 403. Your login works, but not for that stack. Either the stack belongs to a different organization, or your role can't do that there. Logging in again doesn't fix it. Use a stack in your organization, or switch your default organization in Contentstack and log in again.
  • The login fails with Unknown region. Use one of the region codes listed under Prerequisites.
  • The login stops at once with User force closed the prompt. It ran without a terminal it could use. Run it yourself in a terminal window.
  • The agent says the server is connected, but no Contentstack tools work. Restart your editor. The tools load only when a session starts.
  • Everything succeeds, but nothing appears in your stack. The login ran without a region and signed in to North America. Run it again with your region.

Report a problem with this page