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

How to connect a hosted Linear MCP server to Claude Code with Awesome Remote MCP Servers

Add a remote MCP server to Claude Code with one command and no local install.

Who it is forA developer who uses Claude Code and wants it to read and update Linear issues from the terminal.

The problemRunning an MCP server locally means installing packages and keeping them updated.

The outcomeClaude Code lists the Linear server as connected and can call its tools after sign-in.

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. Install and open Claude Code in a terminal.
  2. Run claude mcp add --transport http linear https://mcp.linear.app/mcp.
  3. Start a Claude Code session and run the first Linear tool request.
  4. Complete the OAuth sign-in in the browser window that opens on first use.

Prompt for your agent

Using the repo awesome-remote-mcp-servers, add the remote Linear MCP server to Claude Code with the README command, then ask it to list <my open Linear issues>. Expected output: a list of issue titles and IDs. Verify the Linear server appears as connected before reporting.

Caveat. The list links to third-party hosted endpoints, so review each provider's data handling before you sign in or send data.

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