.Prompts
com.dotprompts/dotprompts is a MCP server that connects coding agents to your centralized .prompts library over streamable HTTP.
About
com.dotprompts/dotprompts is a hosted Model Context Protocol server for.prompts, a service meant to be the single place you store and reach AI prompts from any MCP-connected assistant. developers shipping agent-heavy products often scatter prompts across README files, Notion, and repo folders, which makes behavior drift between Claude Code sessions and production prompts hard to control. Registering this remote server gives your agent a stable integration point to pull prompt definitions from dotprompts.com rather than pasting ad hoc instructions each time. It is lightweight on setup because transport is streamable-http only in the published manifest, so you add the remote URL in your client config instead of running a local Node process. It does not replace skills or workflow methodology; it is infrastructure for prompt retrieval and consistency. Use it when you already organize prompts in.prompts and want agents to reference the same catalog while you build features, docs, and automations.
- Remote streamable-http MCP endpoint at dotprompts.com/mcp (no local npm package in manifest)
- Positions itself as one home for AI prompts usable wherever MCP clients connect
- Version 0.0.1 with SVG and PNG branding assets in server metadata
- Fits teams and solos who version prompts like code but need runtime discovery from the agent
.Prompts by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http dotprompts https://dotprompts.com/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Centralize and reuse the same prompt templates across Claude Code, Cursor, and other MCP-capable agents instead of copying snippets between repos.
Who is it for?
Best when you already use dotprompts.com and want Claude Code or Cursor to fetch prompts without maintaining duplicate copies in each project.
Skip if: Skip if you only need one-off inline system prompts with no shared library or governance across agents.
What you get
After you register the remote MCP endpoint, assistants can draw from the same .prompts home so iteration stays aligned across tools and environments.
- Remote MCP registration pointing at the .prompts endpoint
- Agent sessions that can reference your centralized prompt set
- Less copy-paste drift between local tests and shared prompt definitions
By the numbers
- Server version 0.0.1 in published manifest
- 1 remote transport: streamable-http at dotprompts.com/mcp
- 0 npm/stdin packages listed (hosted-only in metadata)
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
Hosted prompt-library MCP integration, not an agent skill or local CLI generator.
FAQ
Who is com.dotprompts/dotprompts for?
It is for and small teams who manage reusable AI prompts in.Prompts and want MCP clients to access that catalog remotely.
When should I use com.dotprompts/dotprompts?
Use it during Build when you are standardizing agent instructions across repos, environments, or multiple coding assistants.
How do I add com.dotprompts/dotprompts to my agent?
Add the published remote MCP URL https://dotprompts.com/mcp as a streamable-http server in your Claude Code, Cursor, or other MCP-compatible client configuration.