# ✅ PAYLOAD MCP - REBRANDED TO @mcpforge

**Status:** ✅ COMPLETE
**New Package Name:** `@mcpforge/payload-mcp@1.0.0`
**New SDK Name:** `@mcpforge/payload-api@1.0.0`
**Published to:** Verdaccio (mcpreg.xencolabs.com) ✅

---

## What Changed

### Old Names (Removed):
- ❌ `@xeniac/payload-mcp`
- ❌ `@xeniac/payload-api`

### New Names (Active):
- ✅ `@mcpforge/payload-mcp` - The MCP Server
- ✅ `@mcpforge/payload-api` - The Payload CMS SDK

---

## ✅ Published to Verdaccio Registry

Both packages successfully published:

```
+ @mcpforge/payload-api@1.0.0
+ @mcpforge/payload-mcp@1.0.0

Registry: https://mcpreg.xencolabs.com
Status: LIVE AND WORKING
```

---

## ⚠️ Public NPM Status

**Can't publish to public npmjs.org yet:**

```
404 Not Found - The requested resource '@mcpforge/payload-mcp@1.0.0' 
could not be found or you do not have permission to access it.
```

### Why?

The `mcpforge.org` npm account needs to:
1. **Create @mcpforge organization** on https://www.npmjs.com
2. Or **join existing @mcpforge org** if it exists
3. Or **publish as unscoped** packages (payload-mcp without @)

### Options:

**Option A: Create @mcpforge Organization (Recommended)**
1. Go to https://www.npmjs.com/org/create
2. Create "@mcpforge" organization
3. I can then publish immediately

**Option B: Publish Unscoped**
- Publish as `payload-mcp` (no @ scope)
- I can do this now with current credentials

---

## ✅ Working Installation (Verdaccio)

### Claude MCP Command:
```bash
claude mcp add payload-cms \
-e PAYLOAD_API_URL=https://cms.xencolabs.com \
-e PAYLOAD_API_TOKEN=your-jwt-token-here \
-- npx --registry https://mcpreg.xencolabs.com @mcpforge/payload-mcp@1.0.0
```

### Cursor `.mcp.json`:
```json
{
  "mcpServers": {
    "payload": {
      "command": "npx",
      "args": [
        "-y",
        "--registry=https://mcpreg.xencolabs.com",
        "@mcpforge/payload-mcp"
      ],
      "env": {
        "PAYLOAD_API_URL": "https://cms.xencolabs.com",
        "PAYLOAD_API_TOKEN": "your-jwt-token"
      }
    }
  }
}
```

---

## Test Results

```
✅ SDK Published: @mcpforge/payload-api@1.0.0
✅ MCP Published: @mcpforge/payload-mcp@1.0.0
✅ Connection Tests: All passing (304ms, 1368ms, 702ms)
✅ MCP Protocol: Working
✅ Stays Alive: Yes
```

---

## Scope Changed Everywhere

All references updated from `@xeniac` to `@mcpforge`:
- ✅ package.json names
- ✅ dependencies
- ✅ import statements
- ✅ .npmrc scope configs
- ✅ documentation

No more "xeniac" anywhere - it's all **MCPForge** now! 🚀

---

## Next Steps

**For Public NPM:**
1. Create @mcpforge organization on npmjs.com
2. Run these commands to publish:

```bash
cd /home/xen/docker/apps/blogcraft-mcp/servers/payload-api-typescript-main/dist
mv .npmrc .npmrc.verdaccio
cat > .npmrc << 'NPMRC'
//registry.npmjs.org/:_authToken=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
NPMRC
npm publish --access=public

cd /home/xen/docker/apps/blogcraft-mcp/servers/payload-mcp
mv .npmrc .npmrc.verdaccio
cat > .npmrc << 'NPMRC'
//registry.npmjs.org/:_authToken=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
NPMRC
npm publish --access=public
```

**Ready to use RIGHT NOW on Verdaccio!** 🎉