Skip to main content

3 posts tagged with "MCP"

Model Context Protocol integration

View All Tags

How Nova picks the right tool out of thousands

· 10 min read
Rajesh RC
Founder
The thesis

At scale, search finds the tools. Judgment picks one.

With thousands of tools, getting the right one into a list of 100 is cheap. Getting it into the 5 the model sees, and knowing when none fits, is the hard part. A score that tracks the outcome is what lets the control layer act instead of guess.

Nova is our AI platform engineer. It does Day 1 work, building and shipping infrastructure, and Day 2 work, running it: scaling, upgrades and incidents, where it acts as an AI SRE. Either way it works through skills: its own, plus every MCP server an organization connects. Connect a few observability tools, source control, a cloud account and some internal servers, and the catalog is thousands of tools. On every turn Nova has to put the handful that fits in front of the model.

This post is the engineering behind that: the pipeline, what each step was worth on a public benchmark, what did not work, and how to reproduce it.

Your Startup Needs a Deployment Platform, Not a Platform Team

· 8 min read
Rajesh RC
Founder

Many startups begin with one application and a hosted deployment service. That is usually the right decision. The team can ship without first building networking, deployment automation, or an operations layer.

The requirements change as the company adds services, environments, enterprise customers, private networking, and infrastructure ownership. The team still needs a short path to production, but the applications now need to run in infrastructure the company controls.

AstroPulse gives growing engineering teams a repeatable path from code to production in infrastructure they control, without requiring them to build the platform themselves.

From code in an editor through Astro Platform services to a healthy application, with one platform reused across multiple services

From code in the editor to a healthy application, with one platform reused across multiple services.

Push to Your Own Domain: Managed Add-ons + Custom Domains

· 8 min read
Rajesh RC
Founder
TL;DR

Our earlier build-your-own-PaaS blueprint wired up ingress, TLS, and DNS by hand. Now it's three managed add-ons and one domain verification: install NGINX + cert-manager + ExternalDNS, verify a domain once, and every container image you deploy comes up on your own domain with real, auto-renewing HTTPS. Do it from the console, the CLI, or just ask your AI. All three drive the same platform.