Transcription: OpenAgents Episode 165 - Integrating MCP via AI SDK
June 9, 2026 ยท View on GitHub
Source: https://x.com/OpenAgentsInc/status/1900282953244303440 Wiki source: https://raw.githubusercontent.com/wiki/OpenAgentsInc/openagents/Video-Series.md Media title: OpenAgents - Episode 165: Integrating MCP via AI SDK We use the new to 'vibe cod... Upload date: 20250313 Transcription model: gpt-4o-transcribe-diarize Generated at: 2026-06-01T04:59:21Z
Machine-generated transcript. Review speaker labels and wording before using this as quote-grade source material.
[00:00] Christopher David: One benefit of a startup focused on coding agents is that when new stuff comes out, we can very quickly integrate it.
[00:06] Christopher David: So let's try that out.
[00:07] Christopher David: The AI SDK that we use from Vercel, amazing software,
[00:12] Christopher David: just dropped MCP client support five hours ago.
[00:14] Christopher David: So let's see what we can do with this.
[00:16] Christopher David: So recap,
[00:17] Christopher David: in the last video,
[00:18] Christopher David: we used our new Agentic chat UI here to build a integration with Dexy.
[00:26] Christopher David: To power our chat history there,
[00:28] Christopher David: so instead of loading from the database each time.
[00:31] Christopher David: That's just like a complex thing, not too complex, but somewhat complex thing using a library that I had never used before,
[00:38] Christopher David: a software I had never used before,
[00:40] Christopher David: and we used it to open an issue,
[00:43] Christopher David: about 15 minutes of back and forth,
[00:45] Christopher David: and it cost about $7 of compute,
[00:49] Christopher David: started with $82,
[00:50] Christopher David: now $75.
[00:51] Christopher David: And we have a PR,
[00:52] Christopher David: it's merged and works.
[00:54] Christopher David: And that's really great.
[00:55] Christopher David: And I'd love to multiply that by 10. If I could spend $70 to have 10 PRs done,
[01:00] Christopher David: man,
[01:00] Christopher David: I would do that all day.
[01:01] Christopher David: So anyways,
[01:02] Christopher David: to extend the capabilities of our agent,
[01:05] Christopher David: we are going to integrate MCP servers.
[01:09] Christopher David: Obviously, tons of people talk about MCP these days.
[01:11] Christopher David: And now to have an easy way of integrating it into our app is amazing. So one little 30-second history lesson in...
[01:21] Christopher David: Earlier in this series,
[01:22] Christopher David: around episode...
[01:25] Christopher David: hmm 92 ish year ago now we did a kind of an MVP of an agent store the world's first AI agent marketplace with revenue sharing paid daily in Bitcoin we let people developers contribute plugins get paid some rev share kind of this like boutique thing that we figured out ourselves and that was cool we had like 20 developers paid out but we didn't really have the use case
[01:51] Christopher David: um in place for which people were willing to actually pay thousands of dollars which is what brought us to coding agents because this is a thing that uh well um but anyway our little recap here of our agent store what do we say here um blah blah blah
[02:14] Christopher David: Yeah, basically we need that compelling use case for which people are willing to pay.
[02:17] Christopher David: And then we're going to take a piece of what people pay for that and we're going to pay developers.
[02:23] Christopher David: Lots of people will now trying to make it so you can contribute MCP clients or servers into some directory or whatever.
[02:32] Christopher David: But we actually want to combine that idea with payments, like rewarding people proportionally to the value that they create if you create an MCP server that's using a coding agent workflow that people are.
[02:41] Christopher David: People are paying for you should get a percentage of that stream directly to you and the obvious way of doing that to pay you is in Bitcoin.
[02:49] Christopher David: So let's just see how far we can get building this into open agents right now.
[02:56] Christopher David: I'll probably start with some specification and kind of like think about it a bit, but hopefully we can just kind of let open agents do a lot of the heavy lifting here.
[03:07] Christopher David: So let's go over here.
[03:09] Christopher David: And let's say we want to add support for this.
[03:15] Christopher David: Scrape it.
[03:17] Christopher David: Look at all files relevant in our code base, then open a GitHub issue.
[03:26] Christopher David: Ooh, let's make sure I'm on the right repo, first of all.
[03:30] Christopher David: There we go.
[03:32] Christopher David: Okay.
[03:34] Christopher David: Add support for this, scrape it, open a GitHub issue.
[03:38] Christopher David: with plan and then this is the kind of thing also that like hey read this stuff that's new open issue and then soon a PR this is stuff that I'm not really gonna need to be doing myself like I can have an agent just be tasked with like pulling in new stuff to open agents
[04:03] Christopher David: So, let's break this down into steps. First I'll scrape the Versal AI SDK documentation. Let's search our code base for relevant files.
[04:14] Speaker B: Mm-hmm.
[04:14] Christopher David: Using grep which again like last video uh uses our external service that we have, we're like clone the V4 repo.
[04:22] Christopher David: And we can do CLI type things, the kinds of things that PowerCloud coder and to some extent cursor to make them so good is they're able to run Linux commands on your desktop.
[04:32] Christopher David: Well,
[04:32] Christopher David: we have that same ability now through the web app because we're just communicating with a service that we run.
[04:40] Christopher David: OK,
[04:40] Christopher David: let me check the tools directory.
[04:42] Christopher David: Check index.ts to see how tools are currently structured based on documentation and our code base analysis I'll create an issue outlining the plan to implement MCP tools support
[04:54] Christopher David: All right, let's go take a look at what it did so
[04:59] Christopher David: So yeah,
[05:00] Christopher David: and I don't think I mentioned in the message that I want there's to be like a whole marketplace will like separately have like separately
[05:07] Christopher David: Loom crashed and we're back.
[05:09] Christopher David: So add support for MCP tools.
[05:11] Christopher David: Yeah, I did not ask in here to like create a marketplace. We just hey integrate this.
[05:17] Christopher David: So we'll do a separate issue or strategy doc around the marketplace piece of it, but let's read this first.
[05:24] Christopher David: We can add support for MCP tools to enable our applications to discover and use tools across various services through a standardized interface.
[05:34] Christopher David: Add MCP client support,
[05:35] Christopher David: implement MCP client initialization with both blah blah blah. So STDIO.
[05:43] Christopher David: Wonder if we could do that for a VR workbench or just do the S_S_E_ transport. I think we'll pro probably focus on S_S_E_
[05:52] Christopher David: Proper clean-up, M_C_P_ blah-di blah. Setup instructions, okay.
[06:03] Christopher David: Okay,
[06:04] Christopher David: so here's what I want to do. I want to have one agent doing this in one tab,
[06:08] Christopher David: and then I'm going to open another tab and point at the same issue and have it speculate separately about marketplace stuff.
[06:13] Christopher David: Okay,
[06:13] Christopher David: so here's what I'm going to do here.
[06:16] Christopher David: Open a branch,
[06:17] Christopher David: make all needed file changes on that branch,
[06:22] Christopher David: open a pull request when complete, or otherwise add GitHub comments to the
[06:31] Christopher David: issue when at good stopping point etc and got a matula blah okay so I'm going to separately say
[06:44] Christopher David: read issue 82 scrape
[06:52] Christopher David: and I'll just have it also scrape the boom and let's just also scrape
[06:59] Christopher David: That I have another agent now doing the basic integration for that issue but I separately want to speculate about how to build a marketplace around this so look as much as you need to
[07:26] Christopher David: around those docks and anything else. Also take a look through our current code base.
[07:39] Christopher David: Like look at the convex schema so you see that. See our data models.
[07:48] Christopher David: And then put here some thoughts.
[07:54] Christopher David: Put here in this chat some thoughts to
[07:59] Christopher David: flesh out the marketplace plan and when I'm happy with it I'll ask you to make a github issue for it.
[08:12] Christopher David: But not yet.
[08:14] Christopher David: Okay let's see if I can get two of these going.
[08:16] Christopher David: That's going.
[08:21] Christopher David: Okay, so I'm going to need a demo MCP server where we could build our own, perhaps.
[08:30] Christopher David: I'm sure we will be building,
[08:32] Christopher David: I will probably be building multiple MCP servers or functionality into our current service,
[08:38] Christopher David: but it would be nice to, that's
[08:45] Christopher David: nice, that's nice.
[08:46] Christopher David: Two tabs running. Now.
[08:50] Christopher David: So who's got M_C_P_ servers that I can just uuuuuse? I know our friends at Exism are doing some stuff with this. Do they have uh
[09:05] Christopher David: Do do do do do do do do do do.
[09:10] Christopher David: M_C_P_ server
[09:13] Christopher David: directory.
[09:19] Christopher David: Finance and Badoo, do do do.
[09:23] Christopher David: GitHub. Oh, those are from Anthropik. That might be a good place to start.
[09:26] Christopher David: Build and query persistent semantic networks.
[09:35] Christopher David: Anthropik. TypeScript.
[09:39] Christopher David: Yeah,
[09:40] Christopher David: this is going to get pretty interesting pretty fast.
[09:46] Christopher David: Pretty interesting.
[09:48] Christopher David: Okay,
[09:48] Christopher David: let's see what this says.
[09:51] Christopher David: I've created a pull request with the initial implementation of MCP tool support.
[09:55] Christopher David: The changes include core MCP functionality and tools such as MCP, integration with existing tool system,
[09:59] Christopher David: TypeScript types and interfaces,
[10:01] Christopher David: error handling and lifecycle management.
[10:03] Christopher David: Next step would be add UI components,
[10:05] Christopher David: add text.
[10:07] Christopher David: Okay, give
[10:15] Christopher David: me a minimal.
[10:18] Christopher David: Way to test the MTP integration.
[10:30] Christopher David: Now is someone running this somewhere?
[10:36] Christopher David: I want to know who's running servers.
[10:44] Christopher David: This is stuff that you can run yourself I'm guessing?
[11:29] Christopher David: Open protocols are awesome.
[11:52] Christopher David: Should we run our own M_C_P_ server
[11:57] Christopher David: on workbench?
[11:57] Christopher David: Look through code base for workbench to see where we have
[12:05] Christopher David: an external node.js app running. Think if we should use that as a place to deploy mcp servers or if
[12:24] Christopher David: You can read this read-me here,
[12:28] Christopher David: Main branch,
[12:31] Christopher David: and figure out if these directories include hosted versions we can test with or if we should do our own.
[12:48] Christopher David: I still haven't even really thought through like what the implications are for
[12:52] Christopher David: for
[12:53] Christopher David: I hosted one. But fortunately I don't need to think through it all myself.
[12:59] Christopher David: Let me check our code base for workbench references and also look at the M_C_P_ directory.
[13:45] Christopher David: Base on my research, the workbench service currently handles our grep functionality at workbench@opens dot com. This could be a good place to host M_C_P_ servers, since we already have infrastructure there. Looking at m_c_p_ dot S_O_ and the m_c_p_ ecosystem, there are many public m_c_p_ servers available. Two two six nine listed. Popular ones blah blah blah. For testing our m_c_p_ integration I recommend start with a simple local S_T_D_O_ based m_c_p_ server that implements a basic tool like a character calculator or echo service.
[14:11] Christopher David: Then integrate with an existing public one.
[14:13] Christopher David: Okay.
[14:14] Christopher David: I've added a plan to do blah blah blah.
[14:19] Christopher David: Local testing.
[14:20] Christopher David: Tools mpbs clerk.
[14:30] Christopher David: When you say local for a studio,
[14:32] Christopher David: do you mean local on my computer or what?
[14:37] Christopher David: I can run this locally or try
[14:43] Christopher David: prod via Bacel help me understand.
[15:04] Christopher David: Let me explain the standard input-output transport options. Local development, you run both the Next.js app and MTP server on your computer.
[15:12] Christopher David: The MTP server is spawned as a child process by the Next.js app.
[15:48] Christopher David: So um yes proceed with local dev env. Add all this info to GitHub comment on that issue to cause we may need to pass this off to another coding agent. Uh start with the local dev and add instructions for running it and connecting etcetera to the issue.
[16:16] Christopher David: Okay, let's see what this did. Now this what happened?
[16:26] Christopher David: Now this stopped, that's not good. Did it hit an error?
[16:31] Christopher David: Sometimes it can trip up when it hits multiple um web pages.
[16:37] Christopher David: Or I'll just say continue.
[16:46] Christopher David: Based on the gathered information, here are some key thoughts.
[16:49] Christopher David: Core marketplace structure. Need a new tools table in the schema to track published tools. Need a tool publishers table linked to teams and users. Consider tool subscriptions or tool access table to track usage rights. Tool publishing model. Should tools be published by teams only or individual users too?
[17:05] Christopher David: Need verification review process for published tools. Version control and update management. Blah blah blah blah. Okay, monetization options. Pay-per-use pricing.
[17:15] Christopher David: subscription-based access to tool bundles, revenue-sharing model with tool publishers,
[17:21] Christopher David: different pricing tiers based on usage volume features,
[17:24] Christopher David: okay.
[17:25] Christopher David: How to handle tool discovery and search, authentication.
[17:29] Christopher David: This doesn't seem hard.
[17:31] Christopher David: S-E-K dot dot dot dot.
[18:01] Christopher David: Okay, so first write a very comprehensive doc slash M_C_P_ store
[18:12] Christopher David: and then write a GitHub issue for
[18:17] Christopher David: um
[18:20] Christopher David: then write
[18:22] Christopher David: one or more GitHub issues for implementation.
[18:27] Christopher David: focused on what's needed for an MVP.
[18:37] Christopher David: But first look once more at issue 82,
[18:41] Christopher David: the comments added recently,
[18:43] Christopher David: so you know what's being done there.
[18:49] Christopher David: Okay.
[18:51] Christopher David: Hey, we got a new comment right here.
[18:54] Christopher David: About the local setup.
[19:03] Christopher David: Are those real packages?
[19:26] Christopher David: Created the test M_C_P_ server, added build scripts, created a test page, added detailed testing instructions. To test this, P_N_P_M_ I'm a little nervous. Now we're gonna see if this thing actually frickin works.
[19:43] Christopher David: Before we do that let's take a quick peek at the
[19:46] Christopher David: docs slash M_C_P_ store which it did on May and uh oh, forgot to specify.
[19:55] Christopher David: Um
[20:00] Christopher David: The MCP store is a marketplace for model context protocol tools that enables developers to publish discovered monetized tools that can be used by AI applications.
[20:07] Christopher David: The store integrates with open agencies'
[20:10] Christopher David: existing infrastructure while leveraging the standardization provided by MCP data model.
[20:20] Christopher David: Metadata, tool versions,
[20:22] Christopher David: tool access,
[20:23] Christopher David: tool usage.
[20:25] Christopher David: Dang,
[20:26] Christopher David: tool creation.
[20:27] Christopher David: Developer creates tool implementation following MCP specs, submits basic metadata and documentations as pricing model,
[20:32] Christopher David: SETS PRICING MODEL MOTHER CUZ.
[20:38] Christopher David: Automated checks, schema validation,
[20:40] Christopher David: performance testing,
[20:41] Christopher David: manual overview,
[20:42] Christopher David: blah dee blah,
[20:42] Christopher David: tool moves to publish state.
[20:44] Christopher David: Yeah, discoverable in the marketplace.
[20:46] Christopher David: Discovery and search.
[20:47] Christopher David: Oh yeah. Pricing models.
[20:50] Christopher David: Yup. Yup. Yup.
[20:53] Christopher David: integration yep yep yep yep yep
[21:08] Christopher David: good do it ship it do it do it okay so that's great now let's see if this actually works so I give the cursor something to do cursors over here feeling lonely okay
[21:24] Christopher David: Cursor's over here feeling lonely.
[21:27] Christopher David: So V_ four.
[21:36] Christopher David: And the branch name is
[21:58] Christopher David: Let's give Cursor something to do. It's feeling lonely.
[22:10] Christopher David: I'm really just using it for the terminal. Okay.
[22:11] Christopher David: P-M-P-M-Rum.
[22:13] Christopher David: So first of all, do a type check.
[22:15] Christopher David: Let's see if there's anything messed up.
[22:19] Christopher David: Yeah, there we go.
[22:23] Christopher David: So before I even run this, I'm going to say...
[22:26] Christopher David: I could let Cursor do this, but let's just do this. Um
[22:32] Christopher David: Fix all these errors.
[22:36] Christopher David: And this is a thing that pretty soon I will not need to be pasting in there because using the same kind of little microservice that we built that has this repo cloned,
[22:45] Christopher David: we'll just run the linting and type checks there and let you steer your code base as well as CLI tools and scripts from the Web UI.
[22:56] Christopher David: The point is you shouldn't need to download a desktop app. There should be no reason to download a desktop app.
[23:01] Christopher David: There should be no reason to have a complex interface where you're looking at code because the agents can figure this out.
[23:07] Christopher David: Okay,
[23:08] Christopher David: you don't need a desktop app.
[23:12] Christopher David: You don't need a $10 billion valuation on your company.
[23:20] Christopher David: Sorry, share,
[23:21] Christopher David: okay?
[23:25] Christopher David: Let's fix the server types. Let's fix the client types.
[23:31] Christopher David: Does this agent need something to do?
[23:34] Christopher David: Oh, it also made let's see what issues it made.
[23:39] Christopher David: Implement MCP store MVP.
[23:41] Christopher David: My goodness. Following the integration of basic MCP support, we need to implement the core marketplace functionality that will allow users to discover and use MCP tools. Data model implementation. Add tool access,
[23:52] Christopher David: table, core API endpoints, basic yada yada yada.
[23:54] Christopher David: Schema updates, okay,
[23:56] Christopher David: cool.
[24:01] Christopher David: Okay, um
[24:11] Christopher David: Uh that's good for now. What I want you to do is look at the V_ four readme.
[24:19] Christopher David: And add a nice section there describing the MCP store.
[24:26] Christopher David: So focus less on technicals and more on product considerations like what this store allows the users to do, etcetera.
[24:38] Christopher David: And then do I even have a read-me here?
[24:42] Christopher David: Keep it simple, stupid. Okay.
[24:48] Christopher David: A basic read-me for V4.
[24:54] Christopher David: What we're doing here. I don't even know if it has that context, but let's see what it comes up with.
[25:08] Christopher David: And you can see how I'm juggling between two agents,
[25:11] Christopher David: an agent just being in a browser.
[25:13] Christopher David: And then pretty soon this is going to be even more hands-off and asynchronous than this, where I'll be more kind of like Devin style,
[25:20] Christopher David: giving it the high-level plan and letting it chunk out a lot of this stuff itself.
[25:28] Christopher David: The powerful idea contra Devin is that instead of having some team of super nerds...
[25:34] Christopher David: building everything,
[25:35] Christopher David: we're going to be leveraging the open source community.
[25:38] Christopher David: And our bet as a company is that no team of 10,
[25:42] Christopher David: 50, 100 nerds in one room is going to be able to outperform outmaneuver properly incentivized open ecosystems.
[25:50] Christopher David: And then the business opportunity there is just to take all of that beautiful open source mojo and make it accessible to users.
[26:00] Christopher David: If they're building the Linux,
[26:01] Christopher David: we'll build the Apple on top of that to make it nice and not be so closed source and lethargic like Apple is today. They're getting wrecked. But they had a good run, right?
[26:17] Christopher David: I've updated the readme. Let's take a look.
[26:21] Christopher David: Open Agents v4.
[26:23] Christopher David: Open Agents is building the future of AI-powered software development.
[26:27] Christopher David: Among other things, our platform enables developers and teams to create, share, and monetize AI tools while making them easily accessible to users through natural language.
[26:38] Christopher David: Yada, yada, yada, sure,
[26:40] Christopher David: MCP Store coming soon.
[26:41] Christopher David: The MCP Store is our marketplace for AI-powered development tools built on the model context protocol standard. Think of it as an app store for AI tools that enables for developers.
[26:52] Christopher David: Publish your AI tools and reach a growing audience.
[26:55] Christopher David: Monetize your innovations through flexible pricing models.
[26:57] Christopher David: Get usage analytics and user feedback.
[26:59] Christopher David: Focus on building great tools while we handle distribution.
[27:02] Christopher David: For teams,
[27:03] Christopher David: discover specialized tools for your development needs,
[27:06] Christopher David: try tools before purchasing,
[27:07] Christopher David: pay only for what you use,
[27:09] Christopher David: access enterprise grade tools with proper security and compliance.
[27:12] Christopher David: For the community,
[27:13] Christopher David: share open source tools,
[27:14] Christopher David: build on each other's work,
[27:15] Christopher David: create tool collections and workflows,
[27:17] Christopher David: contribute to a growing ecosystem of AI development tools.
[27:19] Christopher David: Yes.
[27:20] Christopher David: Example: Code Analyzer to understand your framework; Custom Documentation Generators; Framework specific Migration Assistants; Database Schema Optimizers; Security Scanners; Performance Profilers; Testing Tools; et cetera. Getting started: visit Open Agents, connect your repo, start chatting, explore tools, create your teamwork space. Cool. Discord, we don't have a Discord.
[27:40] Christopher David: Okay,
[27:40] Christopher David: not bad.
[27:41] Christopher David: Not bad, not bad at all.
[27:44] Christopher David: There's more to say.
[27:46] Christopher David: Alright, where we at?
[27:48] Christopher David: I've fixed all the TypeScript errors.
[27:49] Christopher David: I'll be the judge of that.
[27:59] Christopher David: Cannot find module.
[28:01] Christopher David: That is the one thing I need to do very easily right here.
[28:12] Christopher David: MCP transport now found.
[28:13] Christopher David: Yeah, what the fuck are you basing this on?
[28:18] Speaker B: What are you basing this on?
[28:28] Christopher David: Where did you get that from look at docs and give me specific thing?
[28:47] Christopher David: Yeah, we're not smartly compressing the conversation context, so this is gonna start getting long and expensive a little bit.
[28:56] Christopher David: I apologise for the confusion.
[29:19] Christopher David: The file that I linked to doesn't even have the right package, or does it?
[29:27] Christopher David: Or is there even a package?
[29:29] Christopher David: Looking at the docs, I see that we don't need any external p M_C_P_ packages.
[29:33] Christopher David: The Vercel A_I_ S_D_K_ already includes M_C_P_ support through its tool system. Let me update our implementation.
[30:17] Christopher David: I'm going to take one more look at that issue it made.
[30:51] Christopher David: Oops.
[30:59] Christopher David: Two errors.
[31:05] Christopher David: Should I give cursor something to do?
[31:07] Christopher David: Fix this. Sad little cursor.
[31:12] Christopher David: Almost irrelevant.
[31:16] Christopher David: Cursor, you can use some of your VC bucks to invest five mil into us, we'll leave you alone,
[31:22] Christopher David: you know, mostly.
[31:23] Christopher David: So you can call me.
[31:45] Christopher David: You're making a lot of changes here. You're making a lot of changes here.
[31:59] Christopher David: If you have a specific mode that should be used, otherwise I'll need to make a educated guess.
[32:05] Christopher David: An educated guess? Why don't you read the fucking docs.
[32:11] Christopher David: Cursor, are you gonna f my code?
[32:35] Christopher David: I don't care, fix this.
[32:37] Christopher David: Do I need to update my SDK?
[32:42] Christopher David: Hang on, hang on, hang on.
[32:53] Christopher David: Look at package dot Jason, I may need to update relevant packages.
[32:58] Christopher David: Do that now via PNPMI.
[33:07] Christopher David: I'm assuming it's just like in the one what they push to M_P_M_
[33:16] Christopher David: Motherfucker.
[33:19] Christopher David: Oh M_C_P_ core.
[33:22] Christopher David: Remove that M_C_P_ core thing.
[33:42] Christopher David: Add to.
[34:48] Speaker C: I made new errors with my fix
[34:54] Speaker C: all this.
[35:02] Speaker C: What the hell?
[35:17] Speaker C: What does it say about React 19?
[35:48] Speaker C: Well, I'm going to ignore these other errors and just see.
[35:55] Speaker C: Fix this now.
[36:22] Christopher David: Okay, anyways.
[36:28] Christopher David: Cursor, I don't know what the fuck you're doing.
[36:30] Christopher David: Revert all of that bullshit,
[36:32] Christopher David: okay?
[36:34] Christopher David: All I'm going to do is clean up these stupid fake packages here.
[36:42] Christopher David: Those don't exist.
[36:44] Christopher David: Pimpin' eye.
[36:47] Christopher David: Okay, anyways.
[36:49] Christopher David: Thanks for nothing,
[36:50] Christopher David: cursor.
[36:52] Christopher David: Let's go into here and say,
[36:55] Christopher David: what does it want me to do?
[37:03] Christopher David: Run it.
[37:05] Christopher David: Shall we?
[37:06] Christopher David: What's going to happen?
[37:08] Christopher David: I don't have it running already,
[37:09] Christopher David: do I?
[37:09] Christopher David: No.
[37:10] Christopher David: What's going to happen?
[37:10] Christopher David: What's going to happen?
[37:17] Christopher David: Visit this.
[37:18] Christopher David: this.
[37:19] Christopher David: Okay, so first of all, is the application running?
[37:22] @: Okay.
[37:25] Christopher David: Okay.
[37:27] Christopher David: Can't resolve child process.
[37:29] Christopher David: That's interesting.
[37:32] Christopher David: Okay, let's have OpenAges.
[37:35] Christopher David: I ran
[37:38] Christopher David: Pimpim.
[37:40] Christopher David: I-S and Pimpim ran dev.
[37:45] Christopher David: visit an X_P_ test and this.
[38:19] Speaker D: Let me clean that up for you.
[38:20] Christopher David: Ah thank you.
[38:58] Christopher David: Let's also update the test server to be more focused.
[39:02] Christopher David: Sounds good to me.
[39:31] Christopher David: Let's also update the test page to test both tools.
[40:12] Christopher David: I've removed the node file, simplify the test server, blah blah blah blah blah blah blah.
[40:28] Christopher David: Okay, what's it do? What's it do.
[41:04] Christopher David: Some of these things are the kinds of things that I would just jump in, if I wanted to do something quickly and conserve tokens.
[41:11] Christopher David: But I'm really just interested in demonstrating just how much we can rely on open agents to do essentially everything.
[41:22] Christopher David: And this is the worst it'll ever be.
[41:34] Christopher David: Should I look at any of the code should I look at it or just run it and give it control of my system?
[42:00] Christopher David: Oh, it's using mock model that's
[42:42] Christopher David: Okay, try this.
[42:43] Christopher David: Um
[42:48] Christopher David: Fix this, also don't do a mock.
[42:53] Christopher David: Look in
[42:54] Christopher David: um
[42:56] Speaker B: Mm-hmm.
[43:01] Christopher David: Here
[43:10] Christopher David: To see how we do this usually.
[43:15] Christopher David: Um
[43:18] Christopher David: And where do we actually do the Grok piece of it? Get tool context
[43:23] Christopher David: and tools get context.
[43:31] Christopher David: Um
[43:35] Christopher David: there and
[43:37] Christopher David: and there to see how it is usually for the test use claud
[43:43] Christopher David: anthropic with
[43:47] Christopher David: model
[43:51] Christopher David: okay you guys watch this while I go pee okay
[44:57] Christopher David: So let me fix gettools.ts and update the test to use Claude properly.
[45:13] Christopher David: I need to add something like the um Claude coder slash compact command.
[45:19] Christopher David: In fact I might just add exactly that.
[45:22] Christopher David: Same type of thing.
[45:50] Christopher David: need to hand this off to another coding agent at full
[45:56] Christopher David: um update of what you've done
[46:01] Christopher David: to the github issue as a comment.
[46:05] Christopher David: Okay first let me do this.
[46:19] Christopher David: Holy shit! Okay, we got something worth testing. First let me do this.
[46:25] Christopher David: That'll be the last thing that chat does. Okay, test.
[46:30] Christopher David: Test test test test. What's he gonna do? Test Echo Tool. Hello.
[46:38] Christopher David: Oh,
[46:41] Christopher David: choose that. Okay, cool. Test Add Tool.
[46:55] Christopher David: 'Cause here I'm gonna say
[46:57] Christopher David: uh read issue
[47:01] Christopher David: is it eighty two?
[47:19] Christopher David: Read issue eighty two.
[47:27] Christopher David: The M_Z_P_ test page works, uh renders. But when I submit
[47:40] Christopher David: I get these errors.
[47:42] Christopher David: Look at all needed files and then add a
[47:51] Christopher David: comment to the GitHub issue with analysis.
[47:53] Christopher David: When I'm starting a new agent,
[47:55] Christopher David: I usually like to start with this.
[47:56] Christopher David: So and then, you know, there's all sorts of room for optimization here.
[48:00] Christopher David: So starting a new conversation,
[48:02] Christopher David: for example, we don't have memory implemented.
[48:05] Christopher David: But I'm excited to try to extend this interface using MTP tools like the MTP tools we saw earlier for knowledge,
[48:13] Christopher David: memory like I should not be writing memory modules.
[48:15] Christopher David: I should not be writing most things.
[48:18] Christopher David: You people are going to write it.
[48:19] Christopher David: You people are writing it, but you've got all these plugins and things just sitting all over the place
[48:24] Christopher David: without the ability to like
[48:26] Christopher David: smartly compose them
[48:29] Christopher David: Ah fuck it didn't give the right branch did
[48:37] Christopher David: it not save oh i'm just refreshed the wrong thing
[48:44] Christopher David: Um, oh,
[48:45] Christopher David: oh, I think I busted some of the persistence
[48:49] Christopher David: Fortunately we have this issue. Okay, let's try this again.
[48:55] Christopher David: That'll be fixed by the time you see this.
[48:58] Christopher David: Alright, uh open GitHub issue eighty two.
[49:03] Christopher David: We are on branch
[49:25] Christopher David: And we
[49:25] Christopher David: use
[49:34] Christopher David: use the M_C_P_ test.
[49:35] Christopher David: Page
[49:38] Christopher David: Page, it renders, but submitting tool gives this error, console error.
[49:45] Christopher David: Look at all needed files and then post an analysis on the GitHub.
[49:51] Christopher David: Issue. As a comment. Okay, and then I'm gonna back up this.
[50:00] Christopher David: I've been messing with like the thread ID situations.
[50:06] Christopher David: I don't care that you saw that. Okay.
[50:10] Christopher David: I've been messing with the thread ID URL updating and I messed up something with the persistence of the thread ID.
[50:18] Christopher David: i think okay let me look at the relevant files and
[50:24] Christopher David: just take a look at what it's seeing here
[50:34] Christopher David: oh
[50:41] Christopher David: i think that's from the agent that was looking at the wrong branch so
[50:47] Christopher David: i might delete
[50:49] Christopher David: this one,
[50:52] Christopher David: or did it look at the right one? Branch I don't know.
[51:19] Christopher David: Thanks make all that make the needed changes directly to
[51:29] Christopher David: the branch now
[51:32] Christopher David: and post comment.
[51:37] Christopher David: Yeah, I've got kind of like this split definition where I'll define the description in one file, I don't know.
[51:46] Christopher David: Should be an easy fix.
[52:06] Christopher David: It's like the kind of flow that you have are probably accustomed to with cursor agent, except it's
[52:11] Christopher David: smarter, keeps context better. But it's more expensive, it's all a trade-off. But like if you're doing powerful coding work, you want your shit to actually work, and not introduce a bunch of bugs. Okay.
[52:23] Christopher David: Let's just see what happens here.
[52:27] Christopher David: Test echo.
[52:30] Christopher David: Test tool echo F_ two three F_ F_
[52:36] Christopher David: Number one. Number two.
[52:40] Christopher David: Okay, okay, okay.
[52:42] Christopher David: So,
[52:43] Christopher David: seems to work.
[52:48] Christopher David: Got that.
[52:50] Christopher David: Now tell me, reading
[52:55] Christopher David: issue 82,
[52:56] Christopher David: is that issue done?
[53:00] Christopher David: Like ready to merge this PR?
[53:05] Christopher David: Do I even have a PR here?
[53:08] Christopher David: 83.
[53:09] Christopher David: So for the SSE version of this,
[53:12] Christopher David: that maybe doesn't need to be done separately.
[53:14] Christopher David: Or should we do SSE one now?
[53:18] Christopher David: I think I want to like set up a server.
[53:25] Christopher David: I think I want to set up a server maybe on our workbench thing.
[53:30] Christopher David: To test the SSE for the remote piece of it, uh that is probably worth doing as a separate video. Let's see. Let me review based on the original issue description.
[53:39] Christopher David: This was a multi-phase implementation. Basic tool structure implemented.
[53:43] Christopher David: Studio transport working. Not SSE.
[53:53] Christopher David: Okay, oh cool. Thanks. Yes, make the new issue linking to this one.
[53:58] Christopher David: I'll merge this PR.
[54:05] Christopher David: Update the PR issue A3 as needed,
[54:09] Christopher David: then I'll merge it.
[54:18] Christopher David: We now have MCP support for local tools via STDIO,
[54:23] Christopher David: one of the two main ways of consuming MCP.
[54:27] Christopher David: added to OpenAges V4 that took 30 minutes,
[54:31] Christopher David: 45 minutes.
[54:34] Christopher David: And then for the SSE version,
[54:36] Christopher David: which is how you kind of communicate with remote servers,
[54:39] Christopher David: I don't see any easily consumable server out there that I can just drop in or that I would trust to drop in,
[54:47] Christopher David: which is amazing.
[54:49] Christopher David: This is an amazing problem to solve because look,
[54:52] Christopher David: discoverability unsolved.
[54:54] Christopher David: I looked around. I couldn't find a single server that I could just use with this. All the directory sites are like, here's things that you can run.
[55:01] Christopher David: But I don't want to solve for people who are able to run servers on their own command line.
[55:05] Christopher David: I want to be able to have it available in a directory that can be pulled into any agent,
[55:11] Christopher David: coder, researcher.
[55:13] Christopher David: Like, I want to build a researcher at...
[55:15] Christopher David: out of composing a bunch of these tools.
[55:18] Christopher David: And I'm going to let people like you say,
[55:20] Christopher David: hey,
[55:21] Christopher David: that researcher is not as good.
[55:22] Christopher David: Let me rip out this module and put this module in.
[55:25] Christopher David: If you improve the agent,
[55:26] Christopher David: insert evals here to measure that,
[55:31] Christopher David: you should get a piece of that revenue generated through that.
[55:34] Christopher David: So we should have very soon here the best assistant,
[55:38] Christopher David: the best coder, the best researcher.
[55:41] Christopher David: The best, you decide what comes next.
[55:45] Christopher David: Stay tuned.