Entity Nate Herk: AIOS course

MCP

Entity · 17 mentions in 10 sources · collections: Nate Herk: AIOS course

Mentions

Or after that, I have all the different techniques, agent teams, sub-agents, permission modes, the WAT framework, and then we've got different concepts, MCP servers, RAG, vibe coding. — Ch 14: Knowledge layer: Karpathy's LLM Wiki in Obsidian › 2:10:30
So as this continues to fill up, we can start to see patterns and relationships between every tool or every skill or every MCP server that I might've talked about in a YouTube video and I can just query it in a really efficient way now that we have this actual system set up. — Ch 14: Knowledge layer: Karpathy's LLM Wiki in Obsidian › 2:06:00
And now what it's doing is it's creating the Google doc, not via API call, not via MCP, but via a bash command, meaning it's literally running a terminal command in order to talk to Google and make this. — Ch 10: Google Workspace CLI (GWS) › 0:55:30
So what I did is I hard coded, the these list IDs, because when I was watching it, I realized every single time it was doing this, it was calling the ClickUp MCP, and it was gathering all these lists and it was searching and parsing the results and then it would extract the ID and that just was taking so long and it was costing me a ton of tokens. — Ch 11: Capabilities: building skills (embedded Claude Skills video) › 1:22:30
We're setting up our contacts, which is basically the brain, making sure it knows our business. setting up the connections to make sure that it can touch things, whether that is an MCP or an API or a CLI or, you know, whatever it is, we're setting up the — Ch 3: Framework 2: the 4 C's (Context, Connections, Capabilities, Cadence) › 0:12:00
I don't like using MCP servers because basically what happens when you do that is it gives you access to every single function and every single endpoints that's possible, but you always don't need all of them. — Ch 8: First connection: ClickUp via API, not MCP › 0:39:00
Whether that's an API or whether that's an MCP or whether that is maybe even having to just do a browser automation script. — Ch 2: Framework 1: the 3 M's (Mindset, Method, Machine) › 0:04:30
It's not the same as like having all these different API endpoints or all of these different MCP configs and tools that would take up more context. — Ch 10: Google Workspace CLI (GWS) › 0:57:00

Appears in

Related entities

Claude Code · ClickUp · ClickUp API · YouTube · CLI · Google · GitHub · Slack · QuickBooks · Nate

Topics

Topic: connect · routines · Topic: youtube video · google · gave · Topic: scheduled tasks · routines · run · Topic: second brain · wiki · youtube

Backlinks

AIOS · Andrej Karpathy · CLI · Claude Code · ClickUp · ClickUp API · GWS CLI · GitHub · Google · Google Workspace · LLM · Nate · QuickBooks · Slack · Stripe · Visual Studio Code · WAT · YAML · YouTube · Hot cache · Index · Ch 10: Google Workspace CLI (GWS) · Ch 11: Capabilities: building skills (embedded Claude Skills video) · Ch 12: Live build: branded infographic skill · Ch 13: Cadence: GitHub, routines, /loop · Ch 14: Knowledge layer: Karpathy's LLM Wiki in Obsidian · Ch 15: Dashboards: Claude Cowork live artifacts · Ch 2: Framework 1: the 3 M's (Mindset, Method, Machine) · Ch 3: Framework 2: the 4 C's (Context, Connections, Capabilities, Cadence) · Ch 4: Map your 7 tier-1 data buckets · Ch 8: First connection: ClickUp via API, not MCP · Topic: api key · repo · github · Topic: connect · routines · Topic: project · step · Topic: scheduled tasks · routines · run · Topic: second brain · wiki · youtube · Topic: youtube video · google · gave