Superpowers MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-superpower-commandC | Run a superpowers command |
| list-superpower-skillsC | List all available superpowers skills |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists available superpower skills, and the other runs commands, with no overlap in functionality that could cause confusion.
Both tools follow a consistent verb_noun pattern with hyphens (list-superpower-skills, run-superpower-command), though the slight variation in the noun part ('skills' vs 'command') is a minor deviation from perfect consistency.
With only 2 tools, the server feels thin for a 'Superpowers' domain, as it lacks essential operations like creating, updating, or deleting superpowers, which limits its usefulness for typical agent workflows.
The tool set is severely incomplete for a superpowers domain; it only supports listing and running commands, missing basic CRUD operations (e.g., create, update, delete superpowers) and other expected functionalities like managing users or permissions.