A library to convert+deploy existing agent projects as MCP servers
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…
In plain words
automcp is a library that lets AI engineers convert existing agent projects into MCP servers with minimal changes. It integrates with popular frameworks including CrewAI, LangGraph, Llama Index, OpenAI Agents SDK, and Pydantic AI. Developers add automcp as a dependency, run a CLI command to generate a configuration file, make edits, and start the server locally. The library streamlines deploying multi-agent workflows and tools to MCP without rebuilding projects from scratch.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
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 some edits and run it to start the server locally. You can think of run_mcp.py like Heroku’s Procfile, Codespaces configs, Pulumi/AWS CDK style IaC. We also created a demo of a deployment platform where you can enter the GitHub URL of your project, deploy with one click, and get a URL for the hosted sse server that can be used with MCP clients like Cursor. Think of it like Vercel for MCP servers. There are still a few manual steps for the user that can be further automated, but curious to hear whether people think it’s useful? There are some interesting directions automcp could go in in future like automatically creating MCP servers for each orchestrator, agent and tool in a project (rather than one monolithic MCP server). Website: https://auto-mcp.com automcp repo: https://github.com/NapthaAI/automcp Deployment platform: https://labs.naptha.ai/ Demo: https://www.youtube.com/watch?v=El5YvBQ5py0
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 16d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, April 2025
the whole month →- IB
Hi everyone, I built PyXL — a hardware processor that executes a custom assembly generated from Python programs, without using a traditional interpreter or virtual machine. It compiles Python -> CPython Bytecode -> Instruction set designed for direct hardware execution. I’m sharing an early benchmark: a GPIO test where PyXL achieves a 480ns round-trip toggle — compared to 14-25 micro seconds on a MicroPython Pyboard - even though PyXL runs at a lower clock (100MHz vs. 168MHz). The design is stack-based, fully pipelined, and preserves Python's dynamic typing without static type restrictions.…
Dev tools · 2025 · runpyxl.com
- UC
Life & fun · 2025 · filiph.github.io
- IB
https://the-pocket.github.io/Tutorial-Codebase-Knowledge/
AI · 2025 · github.com
