@latellu/atlas-mcp 1.0.6 → 1.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +21 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,6 +5,8 @@
|
|
|
5
5
|
|
|
6
6
|
MCP (Model Context Protocol) server for Atlas CMS — enables AI agents to manage content.
|
|
7
7
|
|
|
8
|
+
**Docs & dashboard:** concepts and API reference live at **[docs.atlas.latellu.com](https://docs.atlas.latellu.com)**; the app where you create workspaces, content, and API keys is **[cms.atlas.latellu.com](https://cms.atlas.latellu.com)**.
|
|
9
|
+
|
|
8
10
|
## Overview
|
|
9
11
|
|
|
10
12
|
This MCP server exposes Atlas CMS content management operations as tools for AI agents (Claude, Cursor, etc.). It enables AI agents to:
|
|
@@ -14,6 +16,19 @@ This MCP server exposes Atlas CMS content management operations as tools for AI
|
|
|
14
16
|
- Create, update, publish, and delete content
|
|
15
17
|
- Upload media files from local filesystem
|
|
16
18
|
|
|
19
|
+
Building a custom app instead of wiring up an AI agent? Use the [`@latellu/atlas-sdk`](https://www.npmjs.com/package/@latellu/atlas-sdk) TypeScript SDK — this server only exposes tools for MCP clients (Claude Desktop, Cursor, etc.), it isn't a general-purpose HTTP client.
|
|
20
|
+
|
|
21
|
+
## Core Concepts
|
|
22
|
+
|
|
23
|
+
New to Atlas? A **workspace** is your tenant — it owns all content types, entries, pages, media, and API keys, isolated from other workspaces. Within a workspace:
|
|
24
|
+
|
|
25
|
+
- **[Content type](https://docs.atlas.latellu.com/docs/content-types)** — a schema (e.g. "Article") defining the fields an entry can have.
|
|
26
|
+
- **[Entry](https://docs.atlas.latellu.com/docs/entries)** — a record of a content type, with a **draft → published → archived** lifecycle.
|
|
27
|
+
- **[Page](https://docs.atlas.latellu.com/docs/pages)** — like an entry, but composed of ordered **blocks** and carries its own SEO metadata.
|
|
28
|
+
- **[Locale](https://docs.atlas.latellu.com/docs/localization)** — a language variant; localized fields fall back to the workspace's default locale when untranslated.
|
|
29
|
+
|
|
30
|
+
See the [Getting Started guide](https://docs.atlas.latellu.com/docs/getting-started) for the full picture.
|
|
31
|
+
|
|
17
32
|
## Features
|
|
18
33
|
|
|
19
34
|
### Schema & Discovery
|
|
@@ -63,10 +78,9 @@ atlas-mcp
|
|
|
63
78
|
|
|
64
79
|
### Getting an API Key
|
|
65
80
|
|
|
66
|
-
1. Open
|
|
67
|
-
2.
|
|
68
|
-
3.
|
|
69
|
-
4. Copy the key — it is only shown once
|
|
81
|
+
1. Open **[cms.atlas.latellu.com/dashboard/api-keys](https://cms.atlas.latellu.com/dashboard/api-keys)** (sidebar: **Developer → API Keys**)
|
|
82
|
+
2. Click **Create API Key**, give it a name, pick its scopes, and save
|
|
83
|
+
3. Copy the key — it is only shown once
|
|
70
84
|
|
|
71
85
|
**Key types:**
|
|
72
86
|
- `atlas_live_*` — Delivery API key. Required for every **read** tool (`get_workspace_schema`, `list_*`, `get_*`).
|
|
@@ -74,6 +88,8 @@ atlas-mcp
|
|
|
74
88
|
|
|
75
89
|
The backend enforces one key type per route group — a management key cannot read `/api/v1/public/*`, and a delivery key cannot write to `/api/v1/manage/*`. **For the full tool set (read + write), configure both keys.** A single key only unlocks the half of the tools matching its type; calling a tool that needs the other key type returns a clear error naming the missing env var.
|
|
76
90
|
|
|
91
|
+
See [docs.atlas.latellu.com/docs/authentication](https://docs.atlas.latellu.com/docs/authentication) for how scopes work and the full authentication reference.
|
|
92
|
+
|
|
77
93
|
### Environment Variables
|
|
78
94
|
|
|
79
95
|
| Variable | Required | Description |
|
|
@@ -183,7 +199,7 @@ AI: → Calls upload_media with file_path='/Users/you/Pictures/tokyo.png'
|
|
|
183
199
|
|
|
184
200
|
### Best Practices
|
|
185
201
|
|
|
186
|
-
1. **Scope API keys**: For management keys, grant only the scopes each tool needs — `content:write` for create/update/delete/reorder, `content:publish` for publish/unpublish/archive/schedule, `media:write` for uploads/deletes. Leave unused scopes off.
|
|
202
|
+
1. **Scope API keys**: For management keys, grant only the scopes each tool needs — `content:write` for create/update/delete/reorder, `content:publish` for publish/unpublish/archive/schedule, `media:write` for uploads/deletes. Leave unused scopes off. Scopes are picked when you create the key at [Developer → API Keys](https://cms.atlas.latellu.com/dashboard/api-keys); see the [scope reference](https://docs.atlas.latellu.com/docs/authentication) for the full list.
|
|
187
203
|
2. **Restrict upload paths**: Only allow necessary directories
|
|
188
204
|
3. **Rotate keys**: Regularly rotate API keys
|
|
189
205
|
4. **Monitor usage**: Review MCP tool calls for suspicious activity
|