Who it is forA non-developer who uses Claude.ai or ChatGPT and wants a hosted tool, such as Linear, available in chat.
The problemLocal MCP setup requires a terminal and config files that most chat users avoid.
The outcomeThe chat app can use the connected server's tools after one 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
- Open Settings in Claude.ai or ChatGPT and go to Connectors.
- Add the server URL from the list, for example https://mcp.linear.app/mcp.
- Sign in through the OAuth window if the entry is marked 🔐.
- Start a new chat and ask for a task that uses the connected tool.
Prompt for your agent
Using the repo awesome-remote-mcp-servers, add the URL <server-url> under Settings → Connectors in my chat app, then ask it to <task>. Expected output: a reply that uses the connected server. Verify the connector shows as active before testing.
Caveat. The README does not say which connector features each chat app supports, so confirm the server works in your plan before relying on it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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