This chapter wires up two servers: Markdown Convert MCP, a local stdio server run with npx, and the public ysskrishna MCP server over HTTP. The steps are the same for any server.
Claude Code
Local (stdio) server:
claude mcp add markdown-convert -- npx -y @ysskrishna/markdown-convert-mcpEverything after -- is the command Claude Code runs. Add -s user (scope) to make it available in every project instead of just this one.
Remote (HTTP) server:
claude mcp add --transport http --scope user ysskrishna https://www.ysskrishna.space/mcp
Check:
claude mcp listThen, inside a session, run /mcp to see each server's status and its tools.
Cursor
Cursor reads ~/.cursor/mcp.json (global) and .cursor/mcp.json (project). Both use an mcpServers object:
{
"mcpServers": {
"markdown-convert": {
"command": "npx",
"args": ["-y", "@ysskrishna/markdown-convert-mcp"]
},
"ysskrishna": {
"url": "https://www.ysskrishna.space/mcp"
}
}
}Save, then open Cursor Settings → MCP and make sure each server is enabled. A green status and a tool count mean it connected.
On Windows, some hosts need the command wrapped: "command": "cmd" with "args": ["/c", "npx", "-y", "@ysskrishna/markdown-convert-mcp"].
Step by step: connect, then prove it works
- Add Markdown Convert MCP with the config for your host.
- Restart the host or reload MCP servers.
- List tools:
/mcpin Claude Code, or the MCP settings page in Cursor. You should seemarkdown_to_slack,markdown_to_teams,markdown_to_jira,markdown_to_plaintext. - Ask the agent: "Convert this to Slack mrkdwn using the markdown-convert tool: Deploy finished. See logs."
- Approve the tool call when prompted. The result should use Slack's syntax:
*Deploy*for bold and<https://example.com|logs>for the link.
Test a server without an agent
The MCP Inspector is a small web UI that connects to a server directly. Use it to see tools, call them with your own inputs and read raw responses:
npx @modelcontextprotocol/inspector npx -y @ysskrishna/markdown-convert-mcpIf a tool works in the Inspector but not in your host, the problem is host config or approvals, not the server.
When a server will not start
| Symptom | Likely cause | Fix |
|---|---|---|
| Status red, "command not found" | npx or node not on the PATH the host sees | Use the full path to npx, or launch the host from a shell where node -v works |
| Starts, zero tools | Wrong package or args | Run the same command in a terminal; it should wait for input, not exit |
| Works in terminal, not in host | Host started before you installed Node, or a stale config | Restart the host fully |
| Remote server 401/403 | Server needs auth headers | Add the headers your server documents to the config |
| Tools never called | Vague request or too many tools enabled | Name the tool in your request; disable servers you do not need |
Project or user scope?
- Project (
.cursor/mcp.json, orclaude mcp addwithout a user scope): servers the whole team needs for this repo. Commit the file, but never commit secrets; use environment variables. - User: personal tools you want everywhere, such as a converter or a docs server.
Quick check
-
In Claude Code, what does everything after
--inclaude mcp add name -- …mean?It is the command (and arguments) Claude Code runs to start the stdio server. -
What is the top-level key in Cursor's mcp.json?
mcpServers. -
A tool works in the MCP Inspector but your agent never calls it. Where is the problem?In the host: config, enable switch, approvals, or the request not matching the tool description. The server itself is fine.






