MCP servers by AI client
MCP servers with VS Code setup.
18 MCP servers whose documentation includes setup steps for VS Code. Counts servers whose own documentation gives setup steps for that client. A server without them may still work with any client that supports its transport.
- MCP servers
- 18
- run locally
- 18
- offer a hosted endpoint
- 4
- Repositories and docs last checked
- Sept 2026
Active filters
1 MCP server match your filters
Showing 1 to 1 of 1, ordered by recently updated
How results are ordered
By the date the server's source repository last changed, newest first. Hosted servers without a public repository use the date we last read their documentation. This is a measure of recent activity, not quality.
There are no paid placements in the MCP directory, and no ratings.
Razorpay MCP Server
Officialby Razorpay
Official Razorpay MCP server exposing payments, orders, refunds, payment links, QR codes, settlements, payouts and checkout integration tools to AI clients.
Razorpay
Tasks: Orders · Payments · Customers · Store development
- Runs
- Local or hosted · stdio, HTTP
- Auth
- API key, Token
- Setup for
- Claude Desktop, Cursor, VS Code
- Install
- Docker
From the ecommerceguide dataset
MCP servers with VS Code setup in numbers
Calculated from all 18 servers on this page's list. Each figure opens the list filtered to it.
- MCP servers listed
- 18
- Published by the connected platform
- 8 44%
- Can run locally
- 18
- Offer a hosted endpoint
- 4 22%
- Ask for an API key
- 15 83%
- Support OAuth sign-in
- 3 17%
Where a server's documentation lists its tools, 14 can create or change data and 3 only read it. The other 1 do not list their tools clearly enough to say.
What to check before connecting an MCP server
An MCP server acts with the access you give it to your store, payments or marketing accounts.
What it can access
Check which tools it exposes and whether any create, change or delete data, issue refunds or send messages. Profiles record read-only or read and write only where the documentation lists the tools.
Where it runs
A local server runs on your machine with the credentials you give it. A hosted server runs on the maintainer's infrastructure, so your requests pass through it.
Hosted serversHow it authenticates
Local servers usually read an API key or access token from a config file. Hosted servers can use OAuth, where you sign in to the platform and approve the access requested.
Servers with OAuthWho maintains it
Official servers come from the platform's own company. A community server is not endorsed by the platform it connects to, even when its name suggests otherwise.
8 official serversWhether your client supports it
Clients differ in which transports they support. Check the transport a server uses against your client's documentation before installing.
How active it is
Each profile shows when the source repository last changed. Archived repositories are not listed here.
Understand MCP and agentic commerce
- Choosing an MCP Ecommerce ServerHow to choose an MCP server for ecommerce. Vetting criteria, storefront vs admin coverage, marketing execution, and backend orchestration.
- MCP vs. API for Ecommerce: Choosing Your Agent StrategyWhen to use the Model Context Protocol versus traditional REST APIs for ecommerce agents. Dynamic tool discovery, deterministic payments, and the hybrid integration path.
- Agentic Commerce Protocols: How the Competing Standards DifferAgentic commerce protocols differ on who holds the payment credential and who owns the order. Compare the four axes, and see which commitments reverse.
- Product Feeds for AI Agents: What Machines Need to CompareProduct feeds for AI agents need typed prices, identifiers and availability. Why advertising feeds fall short, and what to fix before integrating.
How this directory works
Where listings come from
Candidates are found on public MCP directories (PulseMCP, mcpservers.org, MCP Market, Build with Claude), on vendor sites, and through submissions. A directory listing is only a lead; nothing is listed from it alone.
How each one is checked
We read the source repository through the GitHub API (README, file tree, package manifests, licence, archive status), the npm package where one is named, the official MCP Registry, and the vendor's documentation for hosted servers. Last full check: Sept 2026.
What gets listed
Only MCP servers, or plugins that install one, that connect to a commerce platform, perform store operations, or serve a business function ecommerce teams use (SEO, ads, analytics, support, accounting). Duplicates are merged into one listing.
What “official” means
Published by the company whose product the server connects to, from that company's GitHub organisation or own domain. Anything else is labelled third-party company or community.
What is extracted, and how
Integrations, tasks, transport, authentication and the clients a server documents setup for are extracted by a language model from that evidence, with the evidence kept for review. Commands are shown as documented and are not tested by us.
What is not listed
Of 219 candidates reviewed, 48 were plugins, skills or libraries without an MCP server, 45 were not about running a store, 11 were duplicates and 17 had an archived, missing or unverifiable source.
Corrections: hello@ecommerceguide.com.