Introduction

Neoroute is a batteries-included remote procedure call (RPC) framework for Golang, running exclusively on top of Web primitives (currently HTTP and WebSocket). With our rich tooling, you get code generation, an interactive debugger for sending requests and a lot more with minimal setup. We have everything you love about RPC and web frameworks, all in one fully integrated package and ecosystem.

Installation

To use Neoroute you need Go version 1.27 or higher. Just add it to your project using go:

go get -u github.com/Liphium/neoroute/v2@latest

Features

Use with AI

We provide the entire documentation you’re seeing right now for AI as well. It’s index is available at ai.liphium.dev/neoroute/index.md.

You can install our liphium-neoroute skill that contains this information and some rules for Neoroute using:

npx skills add liphium/dev@liphium-neoroute

Your agent will love it.

Learning resources

Neoroute is quite a simple RPC framework, but it has lots of features that you might also expect in normal Web Frameworks. This is by design, as we want Neoroute to be usable for all use cases: From game servers to web applications and even mobile apps, anything that needs a server should be able to use Neoroute.

Learning path

We provide a rich learning path that you can read through in about 30 minutes or less. It gives you a clear guide through the entire documentation and shows you what pages to read when. After going through it, you should have a really good understanding of Neoroute and its features.

Examples

There are various examples available in our main repository. Feel free to check them out to get a feel for the framework.

Contributing

We don’t have any hard rules, but please keep in mind the following:

  • No full AI PRs or issues: You should know what your code and writing contains, don’t commit straight up slop.
  • Be friendly with everyone, we’re all here working on this project in our free time.

If you then want to contribute, follow this simple process:

  1. Create an issue outlining what you want to add or the bug you found.
  2. If it’s a feature, discuss it with us and we’ll see if we add anything like it. Specify if you want to work on it or have already started working on it.
  3. If you chose contribution: Create a PR and iterate on it with us, we’ll check and review when we have time.
  4. When the feature / bug fix is out, the issue will be closed.

We really appreciate any contribution, even if it’s just fixing a little thing or improving some documentation.

Thanks to everyone who contributed to Neoroute!

Roadmap

There aren’t actually lots of things we want to add to Neoroute. The framework is already powerful enough for basically anything and the current abstractions cover about everything you would wanna build. However, there are a few central pieces still missing, but ones that don’t require you to change even a line of code.

WebTransport support

Neoroute has been built because we wanted a framework for all kinds of servers. But there is one important part still missing: Unreliable transport.

Especially for games, this is kind of important and we’ve already got a test implementation done in the main repository. The only reason we’ve not published it yet is that we want to make sure we do this right. WebTransport is a lot harder to get working than something like WebSockets because you essentially get access to raw QUIC streams.

We’ll update you when we have it ready.

Neodebug improvements

Neodebug can already be a really powerful tool when testing neoroute servers. However, there are still a few things we would like to add to it:

  • MCP Support: Find a way to let AI agents use it to test servers. Makes it a whole lot easier for them to identify problems.
  • Better mouse support: Selecting with the mouse is currently a little awkward in neodebug. We want to make it a lot easier to select text and copy it to the clipboard.
  • Debugging running connections: Just an idea, but it would be really nice to have a tool that can see what’s going on in connections and not just being limited to sending requests.

We’ll keep you posted if we add anything here.

MCP support

We know this might sound like it’s impossible, but having routes exported to a MCP server has been a dream I’ve had for a long time.

As AI gets more important this is something we’ll look into. Since we’re using MessagePack, this is probably easier said then done.

I’ve got ideas for how we could implement this, so it’s on this list, but it probably won’t be worked on for a while.