@kuracms/mcp

MCP server for kura. Lets your AI assistant (Cursor, Claude Code, Claude Desktop) manage a kura project's content schema.

The split kura is built around: the developer controls the schema through their AI assistant; the non-technical client edits content in the kura admin UI. This server is the developer half. It does schema management only - it deliberately cannot edit entries.

Tools

• list_content_types - all content types and their fields
• get_content_type - one content type's full schema
• create_content_type - create a new content type
• add_field - add a field (additive only; no rename/delete in v0.1)

Setup

Get a project API token from your kura project page (API tokens section). Then add to your AI assistant's MCP config:

{
	"mcpServers": {
		"kura": {
			"command": "npx",
			"args": ["-y", "@kuracms/mcp"],
			"env": {
				"KURA_PROJECT": "your-project-slug",
				"KURA_TOKEN": "kr_live_...",
				"KURA_BASE_URL": "https://kuracms.com"
			}
		}
	}
}

KURA_BASE_URL is optional and defaults to the hosted instance. Omit it unless self-hosting.

Then ask your assistant things like:

Add a bedroom_count integer field to the Listing type

Releasing

Publishing is tokenless via npm Trusted Publishing (OIDC) from GitHub Actions (.github/workflows/publish-mcp.yml) - no NPM_TOKEN, provenance automatic.

One-time setup (after the first publish):

1. The FIRST v0.1.0 publish is manual - npm requires the package to exist before a trusted publisher can be configured: npm publish --access public from packages/mcp with a short-lived bootstrap token, then revoke it.
2. On npmjs.com: @kuracms/mcp -> Settings -> Trusted Publisher -> GitHub Actions, with organization kuracms, repository kura, workflow filename publish-mcp.yml (must match exactly).

Cutting a release after that:

1. Bump the version in package.json.
2. Commit, then tag and push: git tag mcp-v0.1.1 && git push origin mcp-v0.1.1.
3. The Publish MCP workflow runs on the mcp-v* tag (or via workflow_dispatch), updates npm for OIDC support, npm ci, then npm publish --access public. prepublishOnly builds dist/ first; provenance is attached automatically.

Never pass --provenance or an NPM_TOKEN - trusted publishing handles both. The tag prefix is mcp-v so MCP releases don't collide with other repo tags.

Licence

MIT.