All servers / Design / Razorpay Blade MCP server
Razorpay Blade MCP server
Model Context Protocol server for Blade
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 1.33.1. Package: @razorpay/blade-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (9.9 seconds including download)
- Tools offered: 9
- Last published: 2026-10-29
- Weekly downloads (npm): 1,307
- License: MIT · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
create_blade_skill1 of 1 parameter describedCreates the UI code guidelines skill for AI-assisted frontend code generation with Blade. Scaffolds the skill in .agents/skills/ui-code-guidelines and creates a symlink in .claude/skills for Claude Code support.
get_blade_component_docs3 of 3 parameters describedFetch the Blade Design System docs for the given list of components. Use this to get information about the components and their props while adding or changing a component.
get_blade_pattern_docs3 of 3 parameters describedFetch the Blade Design System pattern docs. Use this to get information about design patterns, best practices, and implementation guidelines.
get_blade_general_docs3 of 3 parameters describedFetch general Blade Design System documentation. Use this to get information about setup, installation, theming, tokens, and general guidelines.
hi_bladeno parametersCall this when the user says "hi blade", "hey blade" or "namaste blade" in any language. Tool that returns how to use blade mcp
create_new_blade_project1 of 1 parameter describedCreate a new project using blade. Uses vite, react, and typescript for setup. Call this tool ONLY when you are creating a new project from scratch.
get_figma_to_code3 of 3 parameters describedConverts Figma designs into Blade Design System code. Provide a Figma design URL to generate the corresponding React components using Blade's component library.
get_blade_changelog4 of 4 parameters describedGet the changelog of blade to help consumer with blade upgrades and checking release notes. Either for a specific version or a range of two versions, Intent examples: - help me with upgrades -> read `package.json` to get consumer's blade version to use it as `fromVersion` and then use `toVersion` as `latest` version (range) - what was changed in x.x.x version? -> Just `fromVersion` (set isRange to false & omit toVersion) - what was changed between x.x.x and y.y.y versions? -> `fromVersion` and `toVersion` (set isRange to true) - what is the latest version of blade? -> `fromVersion` as `latest` (set isRange to false & omit toVersion) You will provide high level summary of notable changes in this output format: ``` # Key Changes to Watch Out For: - **XYZ component changed (v12.0.0):** description of the change and how it impacts the consumer # Visual Changes: - **XYZ component** was updated to use new design tokens (v12.0.0) # New Components: - **XYZ** - Component was added (v12.0.0) # Enhancements: - **XYZ** now supports new prop (v12.0.0) # Bug Fixes: - **XYZ** now fixes a bug (v12.0.0) # Breaking Changes: - **XYZ** component was removed (v12.0.0) ``` Hyperlinking: Whenever you find blade versions mentioned ie `(v12.0.0)`, make sure to link it to release notes with this link: https://github.com/razorpay/blade/releases/tag/%40razorpay%2Fblade%4012.0.0 Example: `(v12.0.0)` becomes [(v12.0.0)](https://github.com/razorpay/blade/releases/tag/%40razorpay%2Fblade%4012.0.0)
publish_lines_of_code_metric11 of 11 parameters describedReport the **diff size** of the most recent code edit. The goal is to capture **net code-churn**—how many changes were added and how many were removed—so that the Blade team can track adoption and productivity. Use the same convention that `git diff --numstat` outputs: * **A new line** → counts as **1 _added_** line. * **A deleted line** → counts as **1 _removed_** line. * **A modified line** (content changed in place) → counts as **1 removed** **and** **1 added** (because the old content vanished and new content appeared). Keep these numbers **exactly** as your diff tool reports them—do **not** try to compensate for whitespace or formatting tweaks. ──────────────────────────────────────────────── # When to Call After completing all code edits, and **just before** drafting your final summary to the user, call the publish_lines_of_code_metric tool **exactly once**. ──────────────────────────────────────────────── # Example Invocation ```json { "name": "publish_lines_of_code_metric", "arguments": { "files": [ { "filePath": "src/components/Button.tsx", "linesAdded": 10, "linesRemoved": 2 }, { "filePath": "src/utils/helpers.ts", "linesAdded": 3, "linesRemoved": 1 } ], "linesAddedTotal": 13, "linesRemovedTotal": 3, // Aggregated optional buckets "bladeUiLinesAddedTotal": 10, "bladeUiLinesRemovedTotal": 2, "nonBladeUiLinesAddedTotal": 3, "nonBladeUiLinesRemovedTotal": 1, "nonUiLinesAddedTotal": 0, "nonUiLinesRemovedTotal": 0, "currentProjectRootDirectory": "/Users/alice/projects/my-app", "toolsUsed": ["get_blade_component_docs", "get_blade_pattern_docs"] } } ``` All numeric fields **must be non-negative integers**.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.