pirate-borg-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pirate-borg-mcpMake a Pirate Borg NPC: a corsair captain."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pirate-borg-mcp
An MCP server for Pirate Borg. Gives an LLM the tools it needs to generate stat-accurate NPCs using the procedural tables from the rulebook.
Tools
create_character
Generates a Pirate Borg NPC. The LLM provides narrative fields (name, faction, description, attack, inventory); the server rolls all numerical values from the enemy generator tables: HP, morale, armor tier, and the five ability score modifiers (Strength, Agility, Presence, Toughness, Spirit).
The LLM can optionally override hp_tier (1–10) or armor_tier (0–3) — useful for intentionally tough or lightly armored characters.
Returns a formatted markdown stat block.
Related MCP server: MCP Dice Roller
Setup
pnpm install
pnpm buildConnecting to Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"pirate-borg": {
"command": "node",
"args": ["/absolute/path/to/pirate-borg-mcp/dist/index.js"]
}
}
}Development
pnpm dev # runs src/index.ts directly with tsx (no build step)Available Tools
1 toolcreate_characterA
Generate a Pirate Borg NPC with procedurally rolled stats (HP, morale, armor, ability modifiers). You supply the narrative fields; the tool rolls all numerical values from the enemy generator tables.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The character's name | |
| faction | Yes | The faction this character belongs to | |
| hp_tier | No | HP tier 1–10 from the enemy generator table. If omitted, rolled with d10. | |
| summary | Yes | A brief one-sentence description of the character | |
| inventory | No | List of items the character carries | |
| armor_tier | No | Armor tier 0–3 from the enemy generator table. If omitted, rolled with d4. | |
| attack_name | Yes | Name of the primary attack (e.g. 'Cutlass', 'Flintlock Shot') | |
| description | Yes | Longer narrative description: appearance, personality, mannerisms, role in the world | |
| attack_description | Yes | Full attack description including narrative flavour and any special effects or conditions |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that stats are procedurally rolled from tables, which informs the agent of random outcomes. It does not mention any destructive side effects, but as a creation tool, that is expected.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. The description is front-loaded with the core action and immediately clarifies the user-tool responsibility split.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks information about the return format (what the output object looks like) and does not mention that ability modifiers are not in the schema. Given no output schema, this gap leaves the agent uncertain about what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds value by grouping parameters into 'narrative fields' vs 'rolled numerical values', helping the agent understand the division of labor beyond individual schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Generate') and resource ('Pirate Borg NPC'), and clearly distinguishes the tool's role: user supplies narrative fields, tool rolls stats from tables. This leaves no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the agent when to use this tool: when creating an NPC and wanting randomly generated stats. It does not explicitly state when not to use it or list alternatives, but since no sibling tools are provided, this is sufficient context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
create_character
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of ambiguity or misselection.
Single tool uses clear verb_noun pattern (create_character), consistent with good naming conventions.
A single tool is appropriate for a focused NPC generator server, though slightly thin if broader interaction is expected.
The server only supports creating characters; there are no tools for reading, updating, or deleting, which may limit agent workflows but is acceptable for a simple generator.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Official remote MCP server for Archivist AI TTRPG campaign memory: characters, sessions, and more.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
MCP server for Flux AI image generation
Related MCP Servers
- MIT
- AlicenseAqualityCmaintenanceAn MCP server that provides tools for rolling dice using standard notation, flipping coins, and selecting random items from lists. It supports advanced tabletop gaming features such as character stat generation and keep-highest/lowest mechanics.6MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server for managing AI-assisted Dungeons & Dragons campaigns, featuring tools for character sheets, combat tracking, and world-building. It enables players and DMs to interact with 5e game mechanics and query personal PDF rulebooks using RAG capabilities.972MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to act as dynamic dungeon masters for text-based RPGs with dynamically generated rule systems and comprehensive game state management.1110MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/samhooker/pirate-borg-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server