Skip to main content

2 posts tagged with "ai"

View all tags

Announcing mcp.projectbluefin.io

· 2 min read
Jorge O. Castro
Jorge O. Castro
Director of Dinosaurs

Model Context Protocol (MCP) is an open protocol for LLMs and agents to talk to each other. We're now serving the Project Bluefin organization knowledge base and live factory state at https://mcp.projectbluefin.io/mcp.

Right now hive.projectbluefin.io exposes an API that has things that are useful for agents. We use it to dole out work to volunteers and to get review tasks. This is what's letting us scale out in ways we haven't been able to before. Hive has a nice Knowledge Base that it exposes, so this initial cut is to search that knowledge. This is mostly useful to connect whatever agent you use to our stuff and get context for your agent. So if you want to do Bluefin things you just add this. I've updated the Agentic Contributor Guide, note that our hive API endpoints are published, so if you're building a deep integration it probably makes sense to work with the Hive API directly. Feedback and usage notes welcome!

Endpoint Details​

  • URL: https://mcp.projectbluefin.io/mcp
  • Transport: Streamable HTTP / Server-Sent Events (SSE)
  • Authentication: None (public, read-only)
  • Health Check: https://mcp.projectbluefin.io/health

Available Tools​

Here's what's exposed:

ToolDescriptionParameters
search_knowledgeSearch Project Bluefin knowledge base: engineering patterns, test coverage gaps, CI conventions, and repo findings across projectbluefin/*.query (string, required)
limit (integer 1–25, default 10)
get_factory_statusLive factory status from Hive: hub health, active contributors, actionable items, per-tier limits.None
get_work_queueLive work queue and triage state from Hive: issues ready to implement and triage grouping.limit (integer 1–25, default 10)
get_index_statusOperational health, record count, and timestamp of the published knowledge index.None
get_quickstartOnboarding checklists (first-pr, run-tests, factory-gates, branch-rules).topic (enum, required)
get_repository_mapHigh-level component map, entrypoints, and branch targets for bluefin, bluefin-lts, common, dakota, documentation.repo (enum, required)

Why Bluefin is all in on agentic development

· 2 min read
Jorge O. Castro
Jorge O. Castro
Director of Dinosaurs

Is AI good or bad for open source? This is 58 minutes of me explaining what I've learned on this.

If you're here for the hot take: Are we really all on the same side? There are two worlds in Linux. What reddit/masto/youtube thinks "Linux" is. And then how Linux actually is.

Our value to our users is that we give you Linux as designed by the professionals. The flex is leveraging the collective knowledge of the community. New users have been led to believe that shipping three-year-old kernels and old software is the right way to consume Linux. Good luck with that. When it comes to my Linux, we listen to Lennart. We do listen to GNOME developers. Linux is about choice. We choose a well-designed system and thank the UNIX gods every day that we don't have to deal with that stuff.

We choose not to let people dictate to us how to use our computers. The science is out. The experts have spoken. I've been fortunate to have access to Greg K-H during his time, and we spent a long time discussing how this affects our communities. And he's right. The damn things are finding bugs. And I'm tired of Linux's bullshit. And I mean that in a loving manner. 90% of this crap is passing a 0 or 1 to some silly argument because Asus hates you.

We've got new territory to explore and we're moving quickly. My lesson from six months of AI is "Seven Days to the Wolves". Where will we be when they come? I've been doing this job a long time and it took me fifty-eight minutes of Puerto Rican mansplaining and a cloud-native symphonic metal musical to explain it. LOL.

clankers