nowfound

Alternatives

Products that do what Nodeblue does

Built by engineers. Built for production

  1. 1

    Build production-grade data pipelines with just a prompt

    2025

  2. 2

    The official Elevenlabs MCP Server

    2025

  3. 3

    Open source, free, local debugger for AI agents

    May 2026 · raindrop.ai

  4. 4

    Create your custom MCP-Server in seconds

    2025

  5. 5
    MCPCore80

    Build AI-powered MCP servers in the cloud

    Mar 2026 · mcpcore.io

  6. 6

    Easily build AI agents that connect to any service, no-code

    2025

  7. 7

    13,000+ MCP servers, skills & plugins for AI coding agents

    Jul 2026 · codexmarketplaces.com

  8. 8
    AutoMCP150

    Easily deploy your existing AI agent projects as MCP servers

    2025

  9. 9
    N8N2MCP137

    Turn your N8N workflow to MCP servers with just 3 clicks

    2025

  10. 10SS

    I built MCP servers for my oscilloscope and SPICE simulator so Claude Code can close the loop between simulation and real hardware.

    Apr 2026 · lucasgerads.com

  11. 11MA

    Hey HN, I spent my xmas break building an agent framework called mcp-agent [1](https://github.com/lastmile-ai/mcp-agent) for Model Context Protocol [2]. It makes it easy to build AI apps with MCP servers, and implements every pattern from the popular Building Effective Agents blog [3] as well as OpenAI’s Swarm [4]. I’m sharing it early to get community feedback on where to take it from here, and to ask for contributions. For those who aren’t familiar with MCP, I think of it as a standardized interface to let AI communicate with software via tool calls, resources and…

    2025 · github.com

  12. 12WP

    Hey HN, we just shipped a browser with an inbuilt MCP server! We're a YC startup (S24) building BrowserOS — an open‑source Chromium fork. We're a privacy‑first alternative to the new wave of AI browsers like Dia, Perplexity Comet. Since launching ~3 months ago, the #1 request has been to expose our browser as an MCP server. -- Google beat us to launch with chrome-devtools-mcp (solid product btw), which lets you build/debug web apps by connecting Chrome to coding assistants. But we wanted to take this a step further: we packaged the MCP server directly into our browser binary. That gives…

    Oct 2025 · github.com

  13. 13AP

    Hey all! I recently gave a workshop talk at PyCon Greece 2025 about building production-ready agent systems. To check the workshop, I put together a demo repo: (I will add the slides too soon in my blog: https://www.petrostechchronicles.com/) https://github.com/Aherontas/Pycon_Greece_2025_Presentation_... The idea was to show how multiple AI agents can collaborate using FastAPI + Pydantic-AI, with protocols like MCP (Model Context Protocol) and A2A (Agent-to-Agent) for safe communication and orchestration. Features: - Multiple agents running in containers -…

    Sep 2025 · github.com

  14. 14NT

    Today we're releasing Nanobot an open-source framework for building AI agents on top of the Model Context Protocol (MCP). MCP servers are a great way to expose structured tools, but they’re usually just that—collections of functions. Nanobot makes it simple to wrap any MCP server with reasoning, a system prompt, and orchestration so it behaves like a real agent. Even better, Nanobot fully supports MCP-UI, so agents can pass rich interactive components (forms, dashboards, even mini-apps) directly into chat. A simple example: if you had a Blackjack MCP server with tools like deal, bet, and…

    Sep 2025 · nanobot.ai

  15. 15AC

    We built a reference MCP server that lets your editor/agent learn a codebase directly from source (signatures, types, AST, comments). Docs are optional. The reference impl runs on our open-source project’s codebase. Why we built it Docs are important, but they add another abstraction layer between your code and your users. Keeping them at the right quality is hard (especially at a startup), and LLM-generated docs are often mediocre until you invest real polish. Exposing code to the model in a structured way keeps answers grounded and current, and it’s always available. You can even…

    Sep 2025 · github.com

  16. 16AL

    Most of the MCP servers that I’ve seen are tools implemented in standalone projects. To onboard more tools (especially agents and multi-agent workflows) to MCP, I’ve been thinking it’s important to allow AI engineers to continue to prototype in their existing agent frameworks and deploy with minimal conversion when ready. We created the automcp library, which you can add as a dependency to existing projects (CrewAI, LangGraph, Llama Index, OpenAI Agents SDK, Pydantic AI, mcp-agent currently supported but more coming soon). You just need to run a CLI command to create a run_mcp.py file, make…

    2025 · github.com

  17. 17HM

    We built a Rust MCP server, which wraps the excellent headless terminal (HT)[1] to makes it available for agentic coding tools. Most agentic coding tools struggle with blocking, interactive terminal tools (all the boilerplate generator, infra CLI tools etc). This is because many existing CLI dev tools are built for humans and require interactive input. We built this so agentic coding tools (Claude Code, Cursor, Memex, etc) can “see” and “interact” with terminals exactly like humans do. In our demo video [2], you'll see it operating vim/emacs just as a human would - selecting options,…

    2025 · github.com

  18. 18

    MCP server exposing labgrid hardware-in-the-loop device operations to LLM agents — 47 tools over coordinator gRPC + labgrid's client-side driver stack (power/console/io/flash/mux/SSH). Standalone, coordinator-agnostic. - onurcelep/labgrid-mcp

    Aug 2026 · github.com

  19. 19

    More than a decade ago, I adopted the self-imposed rule, if I answer a question more than once, the third time I need to be able to answer with a URL. Today, I published one very large URL - a book distilling what I learned from helping people work remotely at GitHub, and I wanted to rethink my rule for the age of AI. What if, instead of a URL, I could create an interactive experience that could tailor the guidance to your particular situation? What I ended up building was an Open and Async Advisor MCP server. To install (in claude or any other AI): > claude mcp add open-async -- npx -y…

    Jul 2026 · github.com

  20. 20RM

    We’ve open-sourced the Robot MCP Server, a tool that lets large language models (LLMs) talk directly to robots running ROS1 or ROS2. What it does - Connects any LLM to existing ROS robots via the Model Context Protocol (MCP) - Natural language → ROS topics, services, and actions (And the ability to read any of them back) - Works without changing robot source code Why it matters - Makes robots accessible from natural language interfaces - Opens the door to rapid prototyping of AI-robot applications - We are trying to create a common interface for safe AI ↔ robot communication This is too big…

    Sep 2025 · github.com

  21. 21AF

    I built an unofficial CLI and MCP server for Lambda cloud GPU instances. The main idea: your AI agents can now spin up and manage Lambda GPUs for you. The MCP server exposes tools to find, launch, and terminate instances. Add it to Claude Code, Cursor, or any agent with one command and you can say things like "launch an H100, ssh in, and run big_job.py" Other features: - Notifications via Slack, Discord, or Telegram when instances are SSH-ready - 1Password support for API keys - Also includes a standalone CLI with the same functionality Written in Rust. MIT licensed. Note: This is an…

    Jan 2026 · github.com

  22. 22CM

    I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…

    Feb 2026 · github.com

  23. 23AL

    Hi HN friends, we're Nima (nimabanai) and Craig (cbschind) from Assemble Labs (https://assemblelabs.co) building the hardware context layer for AI to help you write better firmware faster. We’ve built an MCP server that plugs into any AI tool you’re using (Cursor, Claude Code, Gemini, etc.) and brings complete hardware context (schematics, datasheets, etc.) to your existing environment (new app fatigue is real...) with accuracy and in real time. Our goal is to make writing and debugging firmware on custom hardware faster and easier. Try out the free beta release:…

    Oct 2025

  24. 24AA

    I'm Mike, Head of Eng/Product at Alloy Automation. We built MCP by Alloy Automation to give your AI agents structured access to business-critical systems without the integration headache. We've built MCP servers covering thousands of tools across platforms like Quickbooks, Xero, Notion, HubSpot, and Salesforce. Pick the tools you need, provision a server, and ship faster. Need more control? Our Connectivity API gives you programmatic access to all the same tools for custom integrations beyond MCP. Everything runs with scoped auth utilizing our battle-tested credential management system…

    Oct 2025 · ai.runalloy.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →