DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a remote MCP server to Cursor with mcp.json with Awesome Remote MCP Servers

Point Cursor at a hosted MCP URL by editing one JSON config file.

Who it is forA developer using Cursor or VS Code who wants a hosted MCP tool available in the editor's agent chat.

The problemSetting up each tool locally takes time and creates a local process to maintain.

The outcomeThe editor lists the remote server and can call its tools in chat.

What you need first

  • An MCP-capable client such as Claude Code, Cursor, VS Code, Claude.ai or ChatGPT
  • A server URL from the list, plus an account or API key if the entry is marked 🔐 or 🔑
  • Permission to add a URL to your client's settings

Steps

  1. Open your client's mcp.json file.
  2. Add an entry under mcpServers with a name and the server URL, for example linear pointing to https://mcp.linear.app/mcp.
  3. Save the file and restart or reload the client.
  4. Approve the OAuth sign-in if the entry is marked 🔐 in the list.

Prompt for your agent

Using the repo awesome-remote-mcp-servers, add the server <server-name> with URL <server-url> to the mcpServers block of mcp.json, then reload the client. Expected output: the server shows as connected and one of its tools runs. Verify the URL matches the README entry exactly before saving.

Caveat. Entries are only listed after the endpoint answers an MCP initialize handshake, but the list does not guarantee each tool's behavior.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page