ПромтЛаб — библиотека AI-промптов
ru.promtlabsPublished by promtlabs.ruOfficial publisherv2.0.0Updated Oct 28, 2026
Self-hosted AI prompt library: prompts, collections, tags, teams, chains. 29 MCP tools for agents.
Overview
Remote MCP server for a self-hosted AI prompt library, giving assistants access to prompts, collections, tags, teams and chains via 29 tools.
- What you can do
- Work with stored AI prompts: browse, retrieve and manage prompt entries.
- Organize prompts with collections and tags.
- Share and coordinate prompt work across teams.
- Build and use prompt chains that combine prompts into sequences.
- All of this is exposed through 29 MCP tools, though the individual tool names are not listed.
- When to use it
- Useful when a team keeps its AI prompts in a shared library and wants an assistant to pull the right prompt, organize it, or assemble multi-step prompt chains instead of retyping them.
- Requirements
- A remote MCP endpoint at promtlabs.ru over streamable HTTP. A required bearer API key sent in the Authorization header, in the form Bearer followed by a key created in the account settings on promtlabs.ru. No local package or environment variables are declared.
Installation
In SourceWeft
- Open ПромтЛаб — библиотека AI-промптов in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ru.promtlabs%2Fpromptvault/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ai": {
"type": "http",
"url": "https://promtlabs.ru/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.