Rombik
app.rombikPublished by rombik.appOfficial publisherv1.1.1Updated Oct 24, 2026
Code → ДСТУ/GOST 19.701-90 (ISO 5807) flowcharts: 10 languages, 8 export formats, OAuth
Overview
Rombik turns code into ДСТУ/GOST 19.701-90 (ISO 5807) flowcharts, supporting 10 languages and 8 export formats via a remote OAuth endpoint.
- What you can do
- Rombik is a remote MCP server that converts source code into flowcharts following the ДСТУ/GOST 19.701-90 standard, which corresponds to ISO 5807. According to its registry description, it handles 10 programming languages and offers 8 export formats. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
- When to use it
- Use it when you need standards-compliant flowcharts generated from code, especially for documentation or deliverables that must follow ДСТУ/GOST 19.701-90 or ISO 5807 conventions. It is a remote service, so it suits users who prefer not to run a local process.
- Requirements
- A remote MCP client that supports streamable HTTP, plus OAuth authentication against the Rombik endpoint at rombik.app. No packages, environment variables, or headers are declared. Network access to the remote endpoint is required.
Installation
In SourceWeft
- Open Rombik in the dashboard and add it to a workspace.
- Connect the required 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/app.rombik%2Frombik/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"rombik": {
"type": "http",
"url": "https://rombik.app/mcp"
}
}
}Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
56% 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
- 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.