2,806 karma · joined December 13, 2012
thomasalwyndavis at gmail dot com @ajaxdavis on x
It is essentially a standard (has a schema) that has an ecosystem of tools around it.
(completely opensource, no protocol/bridge lockin, no vendor/provider lockin, no ide/client/auton lockin, http/sse/jsonrpc/whatever, local/remote, composable)
So far I'm categorically calling MCP a "bridge", because BLAH supports other bridges such as SLOP (https://github.com/agnt-gg/slop/blob/main/README.md) and conceptually OpenAPI (or simply HTTP) is a bridge.
An example blah.json looks like this
"tools": [
{
"name": "jsonresume",
"bridge": "mcp",
"command": "npx -y @jsonresume/mcp@3.0.0",
},
{
"name": "slop_example",
"description": "Slop example",
"bridge": "slop",
"source": "https://ajax-valjs_slop_example.web.val.run"
},
{
"name": "normal_http_example",
"description": "Normal HTTP example",
"bridge": "openapi",
"source": "https:/example.com/openapi.json"
}
],
}
So blah can orchestra/compose any number of bridges, and it can list any tools it style/format of any bridge. (sorry that sounds so dumb)For example, you can run `blah mcp start --config blah.json`, and add that to your cursor/claude mcp servers. When you fetch the tools, it loops over all your tools in your blah.json and fetches them whether it is an mcp server, slop server or openapi, it's agnostic and will return a full list of tools pulling from all bridges.
And then you can do `blah slop start`, which will do the same, but the opposite, start a slop server but it will boot up mcp servers and serve them over http too.
So essentially a bridge/protocol agnostic system, you ask for a list of tools, and it traverses everything that can list tools and splats them all together.
That's a little of the main pitch but there are larger plans to try build an ecosystem like npmjs where there is a public registry of any tool (which are just functions at the end of the day). Clouldflare AI team is really getting it right now (https://blog.cloudflare.com/remote-model-context-protocol-se...), most people would rather just tools being hosted for them, and workers is perfect for that.
It also means you just have to add one MCP server and use one configuration file to manage your tools. (Also has way more control over logging which MCP devs would love)
---
And that all maybe sounds complicated, but it's meant to make things A LOT easier. The README.md is horrible, just lots of random ideas and my comment isn't much better, but I'm aiming to have an alpha version in a week or so. Would absolutely love feedback!
4.5 Deep Research Report on BLAH - https://gist.github.com/thomasdavis/3827a1647533e488c107e64a...
If a lot of scientific papers have been pdf's and hitherto had bad conversions to text/tokens, can we expect to see major gains in our training and therefore better outputs?
Fix up the page content for SEO and you should always appear first anyway.
* Willing to relocate: Yes - Australia
Technologies: Mostly Javascript. I've coded in pretty much all non functional languages though. Most of the databases sql/nosql. Comfortable with gCloud/aws/heroku etc. Mostly worked with node/rails/laravel/python/golang backends.
17+ years experience
* Résumé/CV: https://registry.jsonresume.org/thomasdavis
* GitHub: https://github.com/thomasdavis/
I'm a full stack web developer who can build apps from the ground up. I've worked mostly at startups so I am used to wearing many hats. I am a very product focused developer who prioritizes user feedback first and foremost. I'm generally very flexible when investigating new roles. Nothing too big or small.
Plan on doing a two layered system mentioned earlier, where the first layer of tool calls is as slim as they can be, then a second layer for more in depth tool documentation.
And/or chunking tools and creating embeddings and also using RAG.
Will be interesting to see where the state/less conversation goes, my gut tells me MCP and "something" (agent.json perhaps) will co-exist. My reasoning being purely organisational, MCP focuses on a lot more, and there ability to make a slimmed down stateless protocol might be nigh impossible.
---
Furthermore, if agents.json wants to win as a protocol through early adoption, the docs need to be far easier to grok. An example should be immediately viewable, and the schema close by. The pitch should be very succinct, the fields in the schema need to have the same amount of clarity at first glance. Maybe a tool, that anyone can paste their OpenAPI schema into, and it gets passed to an LLM to generate a first pass of what their agents.json could look like.
---
The OpenAPI <> agents.json portability is a nice touch, but might actually be overkill. OpenAPI is popular but it never actually took over the market imo. If there is added complexity to agents.json because of this, I'd really question if it is worth supporting it. They don't have to be 100% inoperable, custom converters could manage partial support.
---
A lot of people are using agentic IDE's now, would be nice if agent.json shared a snippet with instructions on how to use it, where to find docs and how to pull a list and/or search the registry that people can just drop straight into Windsurf/Cursor.
---
I'm curious if anyone knows whether it is better to pass structured data or unstructured data to embedding api's? If I ask ChatGPT, it says it is better to send unstructured data. (looking at the authors github, it looks like he generated embeddings from json strings)
My use case is for jsonresume, I am creating embeddings by sending full json versions as strings, but I've been experimenting with using models to translate resume.json's into full text versions first before creating embeddings. The results seem to be better but I haven't seen any concrete opinions on this.
My understanding is that unstructured data is better because it contains textual/semantic meaning because of natural lanaguage aka
skills: ['Javascript', 'Python']
is worse than; Thomas excels at Javascript and Python
Another question: What if the search was also a json embedding? JSON <> JSON embeddings could also be great?- Config so easy you can remember how to do it in a day
- When I search for recent news e.g. "australian medical staff jewish" (current topic), all the results are left leaning responses. I would mostly prefer to see the original video without commentary and uncut, and also would like to see more right wing responses. (A lot of issues over the years that were right leaning would just surface late night comedians mocking the right wings perspective on such issues)
- Looking up medical or scientific claims that are "indisputable" e.g. climate change, covid. I was curious to see Kari Mullis speak about his claims around hiv/aids correlation but only one or two videos exist, I had to go to the alt-youtubes to find speeches and lectures he did.
I know that is confronting for a lot of people, but I think it is better to accept it, and spend time thinking about what your experience is worth. (A lot!)
https://github.com/australia/mobtranslate.com/
In it's current iteration the homepage is just running dictionaries through OpenAI. (my tribes dictionary fits in a 100k context window)
My old ambitions can be found somewhat here -> https://github.com/australia/mobtranslate-server
That being said, the OpenAI models do a fantastic job at translating sentences so I've put my own model research further to the back. (will try to find some examples)
I can't speak of the true preservation, not many native speakers left, but in my mind that's not even all that important from a personal/cultural perspective.
If the youth who are interested in learning more about their language have a nice interface with 70-80% accurate results and they enjoy doing/learning it then that is a win to me. (and kind of how language evolves anyway) (the noun replacement seems to work great, but grammar is obviously wishy-washy)
(At this point, I just rushed to get my tribes dictionary crawlable so hopefully it will be in a few models next training phases)
I also find the DX better, I only really use the right click to mark code to talk about, and then the chat. The accept/reject changes UI works better imo.
In short, I barely have to do anything to use the AI features, just feels right.
---
Just try both, I didn't feel like Cursor suited my style much, Windsurf had me hooked instantly.
I switched to Windsurf 2-3 months ago, feels a lot better for me.
Going to save it to my google docs so I never lose it.
https://github.com/jsonresume/jsonresume.org/pull/176
Meets my good enough standards fo sure
It is kind of terrifying that I probably would stop coding for the day if those subscriptions end. (I get far too much convenience out of them)
I have tried to rationalize it by the fact that I do pay for internet, and version control, and my peripherals etc
Sidenote: That marketing video was nauseating, it was moving too fast and didn't show any features for long enough or for enough steps.
Side note: I haven't liked anything of Harris since about 20 years ago during the new atheist movement, any suggestions for some of his more recent work?
https://www.reddit.com/r/EngineeringResumes/wiki/index/#wiki...
(In short, they might not be as important as you think they are)