Add Russian business and marketplace API MCP servers: hh.ru, VK, Diadoc, SBIS, Chestny ZNAK, marketplaces - #2327
Open
ilyautov wants to merge 2 commits into
Open
Conversation
hh.ru (job board), VK (social network), Diadoc and SBIS (the two legally-binding EDI operators) and Chestny ZNAK (state product marking). Each ships the API as a YAML catalog behind three generic tools, so a 373-method service still costs 14 tool slots in the prompt. Categories: hh.ru follows the Keywordise precedent in Developer Productivity, VK goes to Social Media, and the three document services sit in Finance & Crypto next to the other e-invoicing and accounting entries. Move any of them if triage disagrees.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ilyautov
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Five MCP servers for Russian business APIs. They are separate installs sharing one core, because a recruiter has no use for a product-marking catalog and an accountant has no use for a job board.
Why they do not eat the context window. Each server exposes 14 tools regardless of catalog size:
<svc>_search_methodssearches the catalog in plain Russian or English,<svc>_describe_methodreturns one method's card,<svc>_call_methodexecutes it, plus a catalog map and credential cabinets. One tool per endpoint would put 373 schemas into every VK prompt.Where the catalogs come from. Generated from the official API specifications and shipped inside the package as YAML that the server actually executes, so the documented method list cannot drift from the callable one.
Safety. Every method carries an access class. Reads run immediately; writes and irreversible actions require confirmation. The authorization header never leaves the service's own domains, even when a raw path is called. Keys stay on the user's machine in
~/.ru-mcp/cabinets.json(chmod 600) and no tool ever returns them.Housekeeping. MIT, Python,
uvx-installable from PyPI, listed in the official MCP Registry, CI green. The shared core is a separate package, schema-mcp-core, so a security fix lands in all five at once.On categories. hh.ru follows the Keywordise precedent already in Developer Productivity. The three document services sit in Finance & Crypto next to the e-invoicing and accounting entries. Happy to move any of them wherever triage prefers.
🤖 Generated with Claude Code