pulsemcp Safe content atomic mcp-remote

Meta-Prompting

This MCP server implements the Meta-Prompting technique from the paper 'Meta-Prompting: Enhancing Language Models with Task-Agnostic Scaffolding', transforming a standard language model into a dynamic multi-agent system where the LM adopts two key roles: a Conductor that analyzes complex problems and breaks them into subtasks, and specialized Experts that execute each subtask. Built with Python using FastMCP and supporting multiple LLM providers (OpenAI, Anthropic, Google), the implementation simulates collaborative workflows within a single model through guided system prompts, allowing the model to reason, act, and self-critique for more robust solutions. The server provides tools for meta_model_prompt activation and expert_model consultation, with a fallback mechanism for clients that don't support ctx.sample(), making it valuable for complex problem-solving workflows, architectural decisions, and building AI assistants that benefit from structured multi-perspective reasoning without the overhead of managing separate model instances.

Cognium trust score

50%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: ai-ml
Source: PulseMCP
Repository: github.com/tisu19021997/meta-prompt-mcp-server
Author type: human
Updated: 2026-04-25

View source Find related skills

MCP

Resolve Meta-Prompting from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"