worldai-mcp-server-usage
Guide and workflow for WorldArchitect.AI MCP Server Usage. Use when you need WorldArchitect.AI MCP Server Usage.
What this skill does
# WorldArchitect.AI MCP Server Usage
## Overview
The WorldArchitect.AI MCP server uses **JSON-RPC 2.0** protocol over HTTP POST.
## Endpoints
### Local Development Server
```
POST http://localhost:8081/mcp
Content-Type: application/json
```
### GCP Preview/Production Server
```
POST https://<deployment-url>.run.app/mcp
Content-Type: application/json
```
**Note:** GCP preview URLs are provided in PR comments. The MCP endpoint is always `/mcp` appended to the base URL.
**Example GCP Preview:**
- Base URL: `https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app`
- MCP Endpoint: `https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/mcp`
- Health Check: `https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/health`
**Finding GCP Preview URL:**
```bash
gh pr view <PR_NUMBER> --comments | grep "MCP Endpoint" | grep -E 'https://.*\.run\.app'
```
## Authentication Bypass (Local Dev)
Use the `X-Test-User-ID` header for local testing without Firebase auth:
```bash
-H "X-Test-User-ID: <firebase_uid>"
```
**Finding the user ID:** Check server logs for `user=<uid>` entries:
```bash
grep "user=" /tmp/worldarchitect.ai/*/flask-server.log | tail -10
```
## Available Tools
```bash
# List all tools
curl -s -X POST http://localhost:8081/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "method": "tools/list", "params": {}, "id": 1}' | jq '.result.tools[].name'
```
Tools:
- `create_campaign` - Create a new campaign
- `get_campaign_state` - Get current campaign state
- `process_action` - Send player action and get response
- `update_campaign` - Update campaign settings
- `export_campaign` - Export campaign data
- `get_campaigns_list` - List user's campaigns
- `get_user_settings` - Get user preferences
- `update_user_settings` - Update user preferences
## JSON-RPC Request Format
```json
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "<tool_name>",
"arguments": {
"<arg1>": "<value1>",
"user_id": "<firebase_uid>"
}
},
"id": 1
}
```
## Common Operations
### Get Campaign State
```bash
cat > /tmp/req.json << 'EOF'
{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "get_campaign_state", "arguments": {"campaign_id": "<campaign_id>", "user_id": "<uid>"}}, "id": 1}
EOF
curl -s -X POST http://localhost:8081/mcp \
-H "Content-Type: application/json" \
-H "X-Test-User-ID: <uid>" \
-d @/tmp/req.json | jq '.result'
```
### Process Player Action
```bash
cat > /tmp/req.json << 'EOF'
{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "process_action", "arguments": {"campaign_id": "<campaign_id>", "user_id": "<uid>", "user_input": "I attack the goblin", "mode": "character"}}, "id": 1}
EOF
curl -s -X POST http://localhost:8081/mcp \
-H "Content-Type: application/json" \
-H "X-Test-User-ID: <uid>" \
-d @/tmp/req.json | jq '.result | {dice_rolls, narrative: .narrative[0:200]}'
```
### List Campaigns
```bash
cat > /tmp/req.json << 'EOF'
{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "get_campaigns_list", "arguments": {"user_id": "<uid>"}}, "id": 1}
EOF
curl -s -X POST http://localhost:8081/mcp \
-H "Content-Type: application/json" \
-H "X-Test-User-ID: <uid>" \
-d @/tmp/req.json | jq '.result.campaigns'
```
## Debugging Tips
### Check Server Logs
```bash
# Real-time log monitoring
tail -f /tmp/worldarchitect.ai/*/flask-server.log
# Check for dice roll processing
grep -E "NATIVE|Phase|tool_call|dice" /tmp/worldarchitect.ai/*/flask-server.log | tail -20
# Find user IDs for campaigns
grep "user=" /tmp/worldarchitect.ai/*/flask-server.log | tail -10
```
### GCP Preview Server Endpoints
### Finding GCP Preview URL from PR Comments
```bash
# Get latest GCP preview URL for a PR
gh pr view <PR_NUMBER> --comments | grep "MCP Endpoint" | grep -E 'https://.*\.run\.app' | head -1 | sed -E 's/.*(https:\/\/[^)]+).*/\1/'
```
### GCP Endpoint Structure
- **Base URL**: `https://<deployment-id>.run.app`
- **MCP Endpoint**: `https://<deployment-id>.run.app/mcp` (always `/mcp` appended)
- **Health Check**: `https://<deployment-id>.run.app/health`
### Example: PR #3491 GCP Preview
```bash
# Base URL
https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app
# MCP Endpoint
https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/mcp
# Health Check
https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/health
```
### Testing GCP Preview Endpoint
```bash
# Test MCP endpoint is working
curl -s -X POST https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq '.result.tools[].name'
# Test create_campaign tool
curl -s -X POST https://mvp-site-app-s1-i6xf2p72ka-uc.a.run.app/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"create_campaign","arguments":{"user_id":"test_user","title":"Test"}}}'
```
**Note:** GCP preview servers may have transient issues. If you get HTTP 404, verify the endpoint URL is correct and try again.
### Test Execution Notes
- **`test_agent_selection_classifier.py`**: Comprehensive integration test that exercises all 7 agents with real LLMs. This test can take 15-20 minutes to complete due to multiple LLM calls per test case. Use a longer timeout (1200 seconds / 20 minutes) when running this test.
- Other tests (`test_classifier_model_loading_failure.py`, `test_json_parsing_failure.py`) complete faster (~1-2 minutes each).
## Common Issues
1. **Campaign not found**: Use correct Firebase UID (not email)
2. **Method not allowed (405)**: Use POST to `/mcp` endpoint
3. **Empty dice_rolls**: LLM may skip tool calls - check Phase 1/2 logs
4. **HTTP 404 on GCP**: Verify endpoint URL is correct (should end with `/mcp`). May be transient - retry.
5. **Port confusion**: GCP preview servers don't use ports - use full URL with `/mcp` path
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.