MCP

The Nimles MCP server lets an AI assistant work with your tenants: look up and change content, products and orders, upload media, publish pages. It is hosted at:

https://mcp.nimles.com/mcp

It speaks the Model Context Protocol over Streamable HTTP with OAuth. You sign in as yourself, with your Nimles account, and every call runs as you: the services check your own roles, exactly as in the portal. The server never has more rights than you.

Connect

Claude Code

claude mcp add --transport http nimles https://mcp.nimles.com/mcp

Then run /mcp in Claude Code to sign in. Add --scope user to use it in every project.

VS Code

Add the server to .vscode/mcp.json in a workspace, or to your user configuration with MCP: Open User Configuration:

{
  "servers": {
    "nimles": { "type": "http", "url": "https://mcp.nimles.com/mcp" }
  }
}

VS Code opens the Nimles sign-in in your browser the first time a tool runs.

Other clients

Any MCP client that supports Streamable HTTP with OAuth, dynamic client registration and a loopback redirect URI (localhost, 127.0.0.1 or [::1]) can connect to https://mcp.nimles.com/mcp.

Claude Desktop and claude.ai

Remote connectors added in claude.ai or Claude Desktop (Settings → Connectors) do not work yet: they finish sign-in on a claude.ai redirect URI, and the server accepts loopback redirect URIs only. Claude Desktop will work through the npm package below.

The npm package (coming soon)

A stdio version, @nimles/mcp, for clients that run local servers (such as Claude Desktop) is coming soon. It is not on npm yet.

Using it

Ask in plain language: “List the pages in my tenant”, “Create a product called … with these variants”, “Publish the About page”. A few things help:

• Tenant and resource group. Every call goes to one tenant, and most content lives in a resource group. The assistant starts with get_context; tell it which tenant and resource group to use (set_context), or it uses your home tenant. Creates never guess a resource group.
• Curated tools do multi-step jobs: create_product (images, variants, publishing), publish_cms_page (markdown to a CMS page or post, then publish), upload_media and get_order_overview.
• Generic tools (list_resources, get_resource, create_resource, update_resource, patch_resource, delete_resource, run_action) work on every type in the resources reference.
• Safety. Deletes and consequential actions (payments, order transitions that notify the customer, unpublishing) need an explicit confirmation, and the assistant should ask you first. Secrets are masked in answers.

Accounts

You sign in with the account you use in the portal. To work in a tenant, you need a role there: as the creator of a tenant you are its Owner. API clients (OAuth 2.0 clients that exchange a client id and secret for a short-lived access token) are for backends and are not used with MCP.