Skip to main content
Glama
soulware-studio

promethic-mcp

by soulware-studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote
README.md
# Promethic MCP

[![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/getpromethic-com-agents)

Public packaging and docs for the [Promethic](https://getpromethic.com) hosted MCP server.

Promethic is a prompt library: store versioned prompts where you set the model, switch models, and dial API-only settings (reasoning, verbosity, and other dials). Text, image, and JSON. Edit the output as you work; it tracks those edits and successful copy/download. Refine proposes the next version.

## Hosted endpoint

- URL: `https://mcp.getpromethic.com/v1`
- Transport: Streamable HTTP
- Auth: Bearer `pmk_` developer key (Claude Desktop, Cursor, Codex CLI) or OAuth (Claude iOS, claude.ai web)
- Docs: https://getpromethic.com/agents
- App: https://app.getpromethic.com

## Clients

See https://getpromethic.com/agents for Claude Desktop, Cursor, Claude iOS, claude.ai, and Codex CLI config.

## License

Documentation in this repo is provided by Soulware Studio LLC. The Promethic product itself remains proprietary.

## Local packaging

This repository includes a minimal stdio MCP server for packaging and introspection. The production MCP server is the hosted endpoint above. No real API keys are included in this repository.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: one provides connection details, the other provides a documentation URL. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow the exact same 'get_' + noun pattern, making the naming perfectly consistent and predictable.

Tool Count3/5

With only 2 tools, the server feels thin but the narrow scope (returning server info) is reasonable. The count sits at the borderline where it is acceptable but not substantial.

Completeness4/5

For the apparent purpose of providing connection and documentation information, the surface is complete. Minor additions like a status or configuration tool could be imagined, but no obvious gap exists for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources