Alternatives
Products that do what ContextVM – Running MCP over Nostr does
Hi HN, I'm Gzuuus, the creator of ContextVM this is my first post here, hope you find it interesting! I started building ContextVM some months ago, this is an open protocol that runs the Model Context Protocol (MCP) over Nostr. In practice, it’s a transport for MCP that lets you expose remote servers without needing a domain, inbound ports, or OAuth, clients, and servers only need an outbound internet connection. The problem I ran into: When deploying a remote MCP server you can feel the pain. You usually need a domain name, a static IP, TLS certificates, port forwarding, and some way to…
- 1
- 2
- 3
- 4OM
Hey HN, we’re launching OpenMemory (https://github.com/mem0ai/mem0/tree/main/openmemory), an open source tool that lets you run a personal, portable memory layer for LLMs. Fully self-hosted and under your control. It uses standard MCP protocol and plugs into any MCP client (like Cursor, Windsurf, Claude, etc.) over Server-Sent Events (SSE). https://mem0.ai/blog/how-to-make-your-clients-more-context-a... is a complete tutorial that shows how to set it up locally, the underlying components involved, complete overview of architecture and…
2025 · github.com
- 5
- 6OS
Hello HN, I built this because I wanted to give Claude Desktop access to my Notion workspace without running a flaky local Python script via stdio. This is a Node.js/Express implementation of the Model Context Protocol (MCP) that uses SSE (Server-Sent Events) for transport. It’s designed to be stateless and deployable as a container (I'm hosting it on Apify, but it works anywhere with Node). The Stack: TypeScript + Express @modelcontextprotocol/sdk Zod for input validation Bearer Auth for security (since it exposes an HTTP endpoint) Capabilities: It allows the LLM to search pages,…
Dec 2025 · github.com
- 7OS
I built a zero-configuration tool for automatically exposing FastAPI endpoints as Model Context Protocol (MCP) tools, open to collabs and contributions!
2025 · github.com
- 8GS
Anthropic's Model Context Protocol (MCP) has made it easy to spin up servers that expose tools and data to LLMs. A lot of these MCP servers run locally because they need access to your files, shell, browser, etc. The problem: they typically run with the same privileges as your user. If a server is buggy, misconfigured, or prompt-injected, it can do anything you can do: read SSH keys, exfiltrate dotfiles, poke around in private repos, etc. Our research group is working on this by adding a security manifest (inspired by the Android app manifest) plus a local policy enforcement engine that…
Nov 2025 · guardiagent.com
- 9MG
Anthropic released the Model Context Protocol a couple weeks ago - https://www.anthropic.com/news/model-context-protocol. They have official sdks for python and typescript but nothing for go, so I wrote one! The main goal is to provide a low boilerplate sdk to write MCP servers, you can spin up a server which can give an LLM access to weather forecasts like this: https://github.com/metoro-io/mcp-golang/blob/main/examples/g... . Using it here: https://youtu.be/xaMkMl_R-0A The library handles generating all the MCP…
2024 · github.com
- 10FA
Hi HN -- Since Anthropic announced the Model Context Protocol (MCP) last week [1], I've been excited about giving Claude new capabilities through my custom servers. But while MCP is powerful, implementing the protocol correctly requires a lot of low-level boilerplate code. I found myself wanting something like FastAPI - a high-level framework that would let me focus on building features, not servers. After some hacking, I'm sharing FastMCP: a Pythonic framework for building MCP servers. FastMCP uses decorators to transform normal functions into MCP tools, resources, templates, and prompts,…
2024 · github.com
- 11IB
I've been experimenting with ROS (Robot Operating System) and the Model Context Protocol (MCP), and noticed a gap: while there were some MCP servers for ROS, most were limited. They either only supported topic communication or had hard-coded topic names, which severely limited their reusability. To address this, I built a general-purpose MCP server for ROS that allows interaction with ROS topics, services, and actions -making it more flexible and extensible than previous approaches. A key design decision was enabling communication between the MCP server and a local ROS machine by simply…
2025 · github.com
- 12AM
Author here. I built this after getting frustrated with Amazon Q and wanting a more developer-friendly way to interact with AWS infrastructure. It's a local MCP server that lets Claude safely access your AWS environment using your existing local credentials. I've tried it on cases like: - Visualize my networking setup - Prepare a thorough analysis of my AWS costs and give insights how to cut it - Find S3 buckets without encryption enabled and their total size And it works surprisingly well. Let me know what do you think!
2024 · github.com
- 13MM
Hey HN! I’m Gui from deco (decocms.com). We’ve been using this tool internally as the foundation for a few customer AI platforms, and today we’re open-sourcing it as MCP Mesh. MCP is quickly becoming the standard for agentic systems, but… once you go past a couple servers it turns into the same problems for every team: - M×N config sprawl (every client wired to every server, each with its own JSON + ports + retries) - Token + tool bloat (dumping tool definitions into every prompt doesn’t scale) - Credentials + blast radius (tokens scattered across clients, hard to audit, hard to revoke) - No…
Dec 2025 · github.com
- 14MT
Recently I was trying to use an MCP server to pull data from a service, but hit a limitation: the MCP didn't expose the data I needed, even though the service's REST API supported it. So I wrote a quick CLI wrapper around the API. Worked great, except Claude Code had no structured way to know what my CLI does or how to call it. For `gh` or `curl` the model can learn from the extensive training data, but for a tool I just wrote, it was stabbing in the dark. MCP solves this discovery problem, but it does it by rebuilding tool interaction from scratch: server processes, JSON-RPC transport,…
Feb 2026 · github.com
- 15MM
I built MCPlexor to solve a token waste problem I kept running into with MCP-based agents. The Problem: MCP (Model Context Protocol) is great for giving LLMs access to external tools. But if you connect multiple servers (GitHub, Linear, Postgres, Slack), you end up with 40-50k tokens of tool definitions injected into every request – before the agent even does anything. On a 200k context model, that's 25% gone. On smaller models, it's worse. And most runs only use 1-2 tools. The Solution: MCPlexor sits between your agent and your MCP servers. Instead of loading all tool definitions upfront:…
Feb 2026 · mcplexor.com
- 16TU
Over the past couple weeks, l've been really immersed in learning about MCP, a new protocol for equipping any LLM with a set of tools that can run on your own machine or a remote server you control and give all kinds of superpowers to Al agents to do things like search, etc. As part of that research, l've already built one very fleshed-out and useful MCP server that l've shared here (I've added much more to it recently though!), the LLM Gateway MCP Server, which lets you use a big model to delegate to a cheaper model (and many more things in addition to that, like running automated…
2025 · github.com
- 17WB
The latest CLI releases from google and anthropic are sweet, we wanted build one that can run any model. mcp-use-cli lets you `/model` hop between providers instantly. npm i -g @mcp-use/cli && you're done What's cool: - BYOK (your keys, encrypted locally) - Slash commands for everything - MCP protocol support for custom tools - Works with OpenAI, Anthropic, Google, Mistral, Groq, local Ollama... The whole thing's TypeScript and open source. Built this on top of our Python + TS mcp-use libs, so it speaks MCP out of the box. You can hook up filesystem tools, DB servers, whatever you…
2025 · github.com
- 18CD
Hey folks, I've been building AI agents that need to talk to various APIs, and I got tired of writing custom integrations for every service. So I built the MCP-OpenAPI Server to solve this problem! It's a simple bridge that lets AI agents discover and use our existing OpenAPI endpoints through the Model Context Protocol. No need to write custom code for each service - just point it at the OpenAPI specs, choose which endpoints to expose, and you're good to go. What makes this different from other MCP servers is that it uses SSE transport instead of stdio, making it work well for multi-tenant…
2025 · github.com
- 19IB
TLDR: OpenAPI-MCP is a Dockerized server that dynamically generates Model Context Protocol (MCP) tool definitions directly from your Swagger/OpenAPI documentation. It allows your AI agent to seamlessly access any API without additional coding, streamlining development and eliminating repetitive manual setup. For more details, code updates-----: GitHub: ckanthony/openapi-mcp Docker Hub: ckanthony/openapi-mcp
2025 · github.com
- 20
- 21
- 22MA
I’ve been building and using agents heavily lately. The Model Context Protocol ecosystem is growing insanely fast, but discovering and configuring new tools is still highly manual. Every time I needed to connect an agent to a new service, I had to browse registries, figure out the transport type, identify required env vars, and manually update "mcp.json" files. So I built MCPfinder. It aggregates servers from the official MCP registry, Glama, and Smithery (around 25,000 combined entries) into a deduplicated, ranked catalog. But the real twist is the DX: MCPfinder is itself an MCP server :D…
Apr 2026 · mcpfinder.dev
- 23DS
MCP (Model Context Protocol) server that lets AI assistants check domain availability in real-time. Features: - Multi-source: Porkbun, Namecheap, RDAP, WHOIS - Price comparison across registrars - Social handle checking (GitHub, Twitter, npm, etc.) - Premium domain detection with pricing insights Works with any MCP-compatible client. Install: npx -y domain-search-mcp
Dec 2025 · github.com
- 24MS
Hey, I'm Nick from Nutrient, I want to share our newly released MCP Server that enables document workflows using natural language — things like redacting, merging, signing, converting formats, or extracting data. While many MCP servers have traditionally been developer-focused, we recognized that the technology could be highly effective in promoting the adoption of tools that are often hidden from end-user interfaces. We’re really interested to see if this side of the protocol could continue to mature. One thing we struggled with was the inability to receive documents from the client (no…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →