Developer Tools
pegma.dev
Provides access to a catalog of software composition components and recipes, enabling deterministic package planning based on capability tags.
ENDPOINT 1
https://pegma.dev/api/mcp
MCP server metadata
- Name
- pegma-catalog
- Version
- 1.0.0
Known tools 5
list_componentsList Pegma composition catalog components (id, summary, status, packages).
Inferred read-onlyget_componentFull catalog entry for one component: owns, refuses, dependencies, adapters, hostMustProvide, packages, links.
Inferred read-onlylist_recipesList synthetic composition recipes (id, intent, packages, fixture status).
Inferred read-onlyget_recipeFull recipe: intent, packages, adapters, host responsibilities, anti-patterns, fixture citation.
Inferred read-onlyplan_compositionDeterministic package/recipe recommendation from structured capabilityTags and optional host.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pegma-catalog]
url = "https://pegma.dev/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pegma-catalog": {
"type": "http",
"url": "https://pegma.dev/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pegma-catalog
Remote MCP URL: https://pegma.dev/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pegma-catalog": {
"url": "https://pegma.dev/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pegma-catalog": {
"type": "http",
"url": "https://pegma.dev/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pegma-catalog",
"transport": "streamable-http",
"url": "https://pegma.dev/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for pegma.dev was fetched 2026-08-03T20:24:53.069Z and is being refreshed.
pegma.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.