Use BestMCPServers Tools with Cursor and MCP

How Cursor can use the Tool API today

Cursor can consume BestMCPServers in two stages. Today, developers can call the HTTP endpoints directly from scripts, shell commands, or project automation. The OpenAPI contract defines the same tool names that will be exposed by a future remote MCP endpoint.

This is useful for coding workflows where Cursor needs to inspect JWT payloads, format pasted JSON, validate configuration files, or encode and decode Base64 strings without opening a browser tool page.

curl -X POST https://bestmcpservers.com/api/base64/decode \
  -H "Content-Type: application/json" \
  -d '{"content":"QmVzdE1DUFNlcnZlcnM="}'

Future remote MCP configuration

The intended remote MCP endpoint is https://bestmcpservers.com/mcp. Once shipped, Cursor should discover tools such as format_json, validate_json, encode_base64, decode_base64, and decode_jwt from that endpoint. The current REST API already uses the same core tool functions, so the MCP layer can be added without changing tool behavior.

Until the remote MCP endpoint is live, treat the OpenAPI spec and docs page as the canonical contract. Teams can wrap the HTTP endpoints inside their own local MCP server if they need Cursor-native tool discovery immediately.

{
  "mcpServers": {
    "bestmcpservers": {
      "url": "https://bestmcpservers.com/mcp"
    }
  }
}

Tool names and endpoints

Use stable tool names in prompts and wrappers: format_json maps to /api/json/format, validate_json maps to /api/json/validate, encode_base64 maps to /api/base64/encode, decode_base64 maps to /api/base64/decode, and decode_jwt maps to /api/jwt/decode.

Keeping the tool names close to endpoint names helps AI clients choose the correct operation. It also makes migration from OpenAPI or HTTP tools to MCP tools easier.

Safety notes for coding agents

Do not ask an AI coding agent to paste production secrets, private JWTs, session cookies, or customer data into any hosted endpoint unless your team policy allows it. The current API does not store data, but sensitive inputs still deserve careful handling.

For local-only sensitive workflows, use the browser tool pages or a local wrapper. For public or low-risk developer data, the HTTP API is suitable for fast agent workflows.

FAQ