RecipesMCPCoding

Kiro with Markup AI MCP

Coding

Overview

Connect Kiro to the hosted Markup AI MCP server at https://api.markup.ai/mcp/ to run brand-voice, clarity, persona, and other content agents. Add the remote server and log in through your browser.

You’ll need a Markup AI account to continue. Sign up at https://console.markup.ai/signup.

Add the Markup AI MCP Server to Kiro

Open your MCP config first:

  1. Go to Kiro Settings → Settings and find the Configure MCP section.
  2. Click Open Workspace MCP Config (JSON) (.kiro/settings/mcp.json) or Open User MCP Config (JSON) (~/.kiro/settings/mcp.json), depending on whether you want Markup AI in one workspace or all of them.

Then add one of the entries below.

Log in with OAuth
1

Add the server

Add the Markup AI server as a remote HTTP server, with no headers block:

{
  "mcpServers": {
    "markup-ai": {
      "url": "https://api.markup.ai/mcp/"
    }
  }
}

Merge the "markup-ai" entry into any existing mcpServers section instead of duplicating the key.

2

Authenticate

  1. Save the config file.
  2. Kiro handles the browser-based OAuth flow automatically when it connects. With no clientId configured, it registers itself with the Markup AI server using Dynamic Client Registration and opens the authorization page.
  3. Sign in to your Markup AI account and approve access. Kiro stores the token for you—there’s no key to manage.

You don’t need an oauth block. It’s optional, and it’s only for servers that require a pre-registered clientId—Markup AI supports Dynamic Client Registration, so the URL is enough. If your token expires later, Kiro triggers a new browser flow on its own without a session restart.

1

Get your API key

  1. Visit https://console.markup.ai/signup and create an account.
  2. Copy your API key from the console.

Store your key securely. Kiro supports ${ENV_VAR} interpolation in headers, so you can reference an environment variable instead of pasting the key.

2

Add the server with an Authorization header

Pass your key as a Bearer token:

{
  "mcpServers": {
    "markup-ai": {
      "url": "https://api.markup.ai/mcp/",
      "headers": {
        "Authorization": "Bearer ${MARKUP_AI_API_KEY}"
      }
    }
  }
}

Use either OAuth or an API-key header—not both. If you set an Authorization header, Kiro sends it instead of starting the login flow, so a bad key surfaces as a connection failure rather than an authorization page.

Remote MCP URLs must use HTTPS (Kiro only allows plain HTTP for localhost).

Restart & Verify

Restart Kiro and confirm the markup-ai server is connected (look for an MCP indicator or a tool list containing Markup AI tools).

Test Your Setup

  • “Check this text for brand-voice drift: [paste text]”
  • “List the available Markup AI agents.”

Troubleshooting

  • Ensure the JSON is well-formed and the entry sits under mcpServers.
  • Verify the URL is https://api.markup.ai/mcp/, including the trailing slash—without it the request redirects and Kiro can’t discover the OAuth endpoints.
  • If the authorization page doesn’t open, make sure the entry has no headers block; an Authorization header suppresses OAuth.
  • If you don’t see the tools, fully restart Kiro.