MCP access ships for AI assistants | Sep 14

Elena Reyes: Okay, Mato just shipped MCP access this week, and it's the biggest thing in the change log by a mile. Blake: The one everyone's been asking for. Elena Reyes: Right, like actually asking, not just vibes. Blake: Sure. So for anyone who doesn't live in this world, MCP is basically the plumbing that lets an AI assistant talk to a tool directly instead of you copy-pasting stuff back and forth. Elena Reyes: Which honestly is exhausting. I'm Elena. Blake: I'm Blake. This is Made on Mato. Elena Reyes: And this week's change log isn't just the MCP piece. There's assistant side cards where it's supported, a cleaner manual review handoff, and Apple catalog checks that are apparently more reliable now. Blake: Four things in one week. Elena Reyes: The cards piece is the one I actually want a demo of, an assistant showing you a card instead of just spitting back a wall of text. Blake: Yeah, and that's only where it's supported, so don't expect it everywhere yet. Elena Reyes: Four things. But here's the part I wanna sit with before we even get into the feature list. Blake: Oh? Whether Mato's the only one who did this? Elena Reyes: Exactly. Because that's not actually clear yet. Blake: We'll get there. Let's start with what's actually in the box. Elena Reyes: Feature by feature. Okay, so the word doing all the work in that change log entry is workspace control. That's the part I wanna sit on for a second. Blake: Sit on it how? Um. Elena Reyes: Like, who's actually flipping that switch? Is it me? Is it a producer? Is it whoever set up the Mato account originally? Blake: The change log just says, "Access is workspace controlled," full stop. It doesn't say who inside a workspace gets to grant it. Elena Reyes: Right. That's my whole question. Blake: There's a blog post that walked through this when it first went up back on September ninth, written by a guy named Benz over there. Elena Reyes: And what's it actually let you do? Blake: Connect Mato to your assistant, create podcasts and episodes straight from it, check your analytics and rankings without opening the dashboard. And this is the line that matters, choose which workspaces the assistant can touch. Elena Reyes: Wait. So if I run three shows under one Mato login? Blake: You could theoretically hand the assistant one of them and lock the other two out. That's the pitch anyway. Elena Reyes: Theoretically. Blake: The post describes the choice. It doesn't walk through what the permission screen actually looks like or whether it's one owner clicking a toggle or something more granular like per seat access. Elena Reyes: So we don't actually know if it's a light switch or a whole panel of switches. Blake: Correct. And that's not nothing. If you've got a co-host or an editor with their own login, does workspace control mean they each set their own assistant permissions, or does one admin decide for everybody? Elena Reyes: Mm. I feel like I know which one it is. Blake: The one admin probably. Elena Reyes: Yeah. Most of these tools start that way and add the fine-grain stuff later. Blake: Which, fine, is a reasonable place to start. You don't ship the complicated version first. Elena Reyes: Sure. But if you're producing for a client and you don't want their assistant poking around your other shows, you'd wanna know that answer before you connect anything. Blake: That's fair. It's a flag, not a deal breaker. Elena Reyes: Think about it like this. Say I've got Made on Mato under one login, but I also run a client show for a local business through the same account. Blake: Right. That's not a hypothetical. Plenty of people run multiple shows on one login. Elena Reyes: Exactly. So if the assistant can touch a workspace, I wanna know if that's scoped down to just Made on Mato or if it can see everything tied to my account the second I connect it. Blake: And neither the change log nor the blog post walks through that. They both just say choose which workspaces the assistant can access like it's a given you'll get a clean list to pick from. Elena Reyes: Which, fine, maybe it is a clean list. But choose implies there's a menu, not just an on/off toggle for the whole account. Blake: That's the generous reading. The stingier reading is it's still early, and the choosing part is coarser than the marketing language makes it sound. Elena Reyes: So until someone actually pulls up the settings screen and shows us, we're guessing. Blake: We are. And I'd rather say that plainly than pretend we know how granular it is. Elena Reyes: Okay. So bottom line for someone listening, connect it on your primary show first, not the client accounts, until we know more. Blake: That's the cautious move, yeah. Elena Reyes: Right. Okay, before we get further into the review handoff and the rest of it- Blake: We should probably back up. Elena Reyes: Yeah. Because we've been saying MCP for five minutes, and I don't think we've actually said what the protocol is or where it came from. Blake: Good idea. Let's go there. Elena Reyes: Okay, so where did MCP even come from? Because it's not like Mato cooked this up in a backroom. Blake: No. Anthropic put this out in November of twenty twenty-four. Elena Reyes: Wait, that far back? Blake: Yeah. Anthropic's announcement pitched it as an open standard, a way to connect an assistant to something like a content system without writing custom code for every single integration. Elena Reyes: So instead of building a one-off bridge for every platform, you write it once. Blake: That's the pitch. One protocol, lots of tools. Elena Reyes: And people actually used it? Or was this one of those launches that just sits there? Blake: Early adopters were named. Block and Apollo were both mentioned as adopting it early. Elena Reyes: Block, like the payments company? Blake: Same one. Elena Reyes: Huh. Okay, that's actual traction, not just a white paper nobody touched. Blake: Right. And that's almost a year before Mato ships anything with it. Elena Reyes: So Block's been running production payments infrastructure, and they trusted this same protocol for connecting a system to an assistant. That's not a company that experiments carelessly. Blake: No. And Apollo's a different kind of user entirely, which tells you the standard wasn't built for one narrow use case. Elena Reyes: Right. It wasn't the podcast protocol or the payments protocol. It's just meant to be the plumbing however you show up. Blake: That's the whole point of calling it an open standard instead of a product. Anthropic wasn't trying to own every implementation. They were trying to make integration something you build once instead of over and over. Elena Reyes: Which explains why Mato didn't need to invent anything here. They just had to plug into rules that already existed and that other serious companies had already leaned on. Speaker 3: Right, and that's a lower risk bet than shipping something totally novel and hoping it holds up. Elena Reyes: So for a podcaster listening to this, what does that actually mean for them? Like, translate it. Speaker 3: It means the thing that lets your assistant talk to Mato isn't a Mato thing. It's a shared standard other companies already agreed to build against. Elena Reyes: So if I've got some assistant I already use for scheduling or email, and it happens to support MCP- Speaker 3: It can talk to Mato the same way it talks to whatever else it's already wired into. No special Mato-only adapter Elena Reyes: That's actually kind of a big deal because it means Mato didn't have to convince some other company's engineering team to build a custom hook just for them. Speaker 3: Exactly the point. The standard already existed. Mato just had to implement it. Elena Reyes: Which, I mean, is a smaller lift than inventing your own protocol from scratch. Speaker 3: Considerably smaller, and it means whatever assistant adds MCP support next also gets to talk to Mato basically for free. Elena Reyes: Okay, but here's what's bugging me a little. Speaker 3: What? Elena Reyes: If this has been out since 2024, and other companies already built on it, Block, Apollo- Speaker 3: Then Mato is not exactly first to the party. Elena Reyes: Right. So Mato didn't invent this thing at all. Speaker 3: Not even close. They implemented a year old standard. Elena Reyes: So the real question isn't whether Mato has MCP. It's whether Mato is even the only podcast platform that's done this. Speaker 3: That's the one I don't know the answer to yet. Elena Reyes: Well, let's find out. Okay, so it's not just Mato at this door. Blake: No. Springcast is already through it. They call themselves, and I'm quoting their own site here, "The first podcast platform to implement MCP." Elena Reyes: Wait, they said first? Before Mato? Blake: Way before. Springcast lets you list episodes, pool analytics, publish all from Claude or ChatGPT. Elena Reyes: Huh. So that's basically the same pitch. Blake: Same pitch, different price tag. It's bundled into their scale tier, so you're paying for the privilege. Elena Reyes: Okay, that's one platform doing the flashy version. Anybody doing it quiet? Blake: Podigee. Completely different posture. Elena Reyes: How so? Blake: Podigee's support docs actually warn you, "Don't expose this thing to listeners. It's infrastructure, not a feature you show off." Elena Reyes: That's a hell of a warning label. Blake: Right? You need an API key and repo access just to ask Claude Desktop for your own analytics. Elena Reyes: So one company's shouting about it in marketing copy, and the other's basically saying, "Use with caution. Keep this in the back room." Blake: Exactly the split. And it's not just podcast tools either. Elena Reyes: What do you mean? Blake: There's reporting on ad platforms, Bumper's MCP server specifically, that says the industry's own registry run by IAB Tech Lab had ten active MCP entries as of this past March. Elena Reyes: Ten. That's more than I expected. Blake: And the same reporting names Amazon Ads, Meta, Pacvue, all rolling out MCP servers with basically the same pattern Bumper used. Elena Reyes: So it's not even one weird move by one platform. It's a pattern the entire ad side landed on independently. Blake: Read-only access basically everywhere. Nobody's letting the assistant write yet. They're letting it look. Elena Reyes: Which tracks with what Mato shipped too. The assistant can act, but the review step is still there before anything actually goes out. Blake: Right, and that's worth noting because Springcast's pitch sounds like it goes further, publish straight from Claude or ChatGPT. No mention of a review gate in what they're advertising. Elena Reyes: That's a meaningfully different risk profile then. Soft versus here go publish. Blake: Assuming their marketing copy is describing the whole picture, yeah. We don't actually know what happens behind the scenes on their end. Elena Reyes: So this isn't a Mato thing. It's not even a podcasting thing. It's just happening everywhere at once. Blake: Which is what makes the manual review hand off interesting to me. Is that actually different, or is Mato just catching up to what Podigee already decided was obvious? Elena Reyes: I mean, Podigee basically built the caution in by default. Don't expose it. Gate it behind a key. Blake: Right. So if Mato is selling manual review as the safety story- Elena Reyes: Is that a real differentiator or just the thing everyone else already assumed you'd do? Blake: I don't think we can answer that yet. Feels like table stakes dressed up as a feature. Elena Reyes: Or it's the one thing that actually matters, and nobody's marketing it right. I'll take the other side of that. Blake: Fair. Leave it there for now. Elena Reyes: Either way, I think it says something that Podigee's the cautious one, and they're not even podcasting's newest player. Blake: No. They've been around a while. So caution here isn't a startup thing. It's apparently just what people land on once they've thought about it for more than a week. Elena Reyes: Or once they've been burned by something. We don't know their reasoning, just their posture. Blake: Fair. We're reading a support doc, not a postmortem. Elena Reyes: Still, ten entries across an entire industry registry as of March feels like early days, not consensus. Blake: Early days that are moving fast, though. Elena Reyes: One more wrinkle before we move off this. This isn't new, but it changes the compliance math. Apple rewrote its own terms back in February. Blake: Yeah, and that's worth its own conversation because it touches the catalog checks Mato just shipped. Elena Reyes: Okay, so Apple didn't just sit still this year either. Blake: Yeah. Back in February, the 18th actually, Apple rewrote its Podcasts Connect terms. Elena Reyes: Wait, all the way back in February, and we're just now talking about it? Blake: Podnews covered it when it happened, but it's relevant now because of what changed. New clauses on video podcasts, for one. Elena Reyes: Okay. Video podcasts, sure. That tracks with everything moving toward video anyway. Blake: Right. But here's the one that got people's attention. Apple gave itself the right to use show content for promotion. Elena Reyes: Meaning what? They can clip your show and put it in an ad without asking. Blake: That's the reading a lot of people had, and there's a jurisdiction shift too. Everything's now under Delaware law instead of whatever it was before. Elena Reyes: Which sounds boring until you're the one in a dispute with Apple. Blake: Exactly. And the last piece, Apple added language giving itself more room to change the terms going forward without much notice. Elena Reyes: So they basically future-proofed their own flexibility. Speaker 4: That's the shape of it, yeah. Elena Reyes: Okay, so actual question. Does any of that connect to Mato's own changelog line, the one about more reliable Apple catalog checks? Speaker 4: I wanna be careful here because the two things aren't stated as connected anywhere. Nobody at Mato said the terms update caused the catalog fix, and I'm not going to imply that just because the timing lines up. Elena Reyes: Hold on. Don't put words in their mouth. Speaker 4: Right. No, I mean literally. There's no line tying the terms update to the catalog fix. It's just a fact that Apple was actively touching its rules around the same window Mato was tightening how it checks the catalog. Elena Reyes: So it's a coincidence in timing, not a documented cause. Speaker 4: That's fair to say. Could be totally unrelated plumbing on Mato's side. Elena Reyes: Could also just be normal maintenance that happens to line up. Speaker 4: Sure. I just don't want us implying a link the sources don't back up. Elena Reyes: Fair enough. It's the kind of thing that's easy to turn into a headline, Apple forces Mato's hand, when really we just don't know. Speaker 4: Right. And headlines like that outlive the correction. Elena Reyes: Noted. Short pause. Okay, speaking of Mato doing its own thing. Speaker 4: Quick word, actually, since we're on the subject of the platform itself. Elena Reyes: Yeah, Mato's who made this show, and if you've been sitting on the idea of launching a podcast for your company or brand, now's a decent time to actually do it. Speaker 4: For a limited time, when you sign up for Mato, they'll throw in a custom cover design, white glove onboarding, your own custom jingle, and a spot on their promotional list. Elena Reyes: That whole package is worth five thousand dollars, and it's included. Speaker 4: Head to hiMato.com to get started. Elena Reyes: Okay, so back to where we were with Apple. That's one more thing sitting on top of an already busy week of changes. Speaker 4: And it's a good place to zoom out, actually. Elena Reyes: Yeah. Zooming back out to Mato specifically, here's what all of this actually changes for someone running a show on the platform. Speaker 4: That's the part worth spending real time on. Elena Reyes: Okay, so practically, you're a small show. You turn on the assistant access. What actually happens the first time you use it? Speaker 4: You ask the assistant to draft an episode or pull your rankings, and it goes and does that part on its own. But the changelog is clear. The manual review step still sits right before anything actually publishes. Elena Reyes: So there's a wall between the assistant doing stuff and the assistant shipping stuff. Speaker 4: Right. The assistant can act, but a human still has to sign off before it goes live. Elena Reyes: That's actually reassuring, honestly. Speaker 4: It is. But it also means the convenience only goes so far. You're not skipping a step. You're just moving where the step happens. Elena Reyes: Which for a two-person show, is that a relief, or is that just one more thing to remember to check? Speaker 4: Both. Like, if you're the one doing review, now you're reviewing assistant output instead of your own drafts. Different muscle. Elena Reyes: Yeah. That's a fair distinction. Speaker 4: And that's basically the whole tension from the Podigee comparison earlier, just pointed at Mato specifically now. Is the review step a real safety net, or is it friction dressed up as safety? Elena Reyes: I don't think we can answer that yet. Nobody's had it long enough. Speaker 4: No. But I'll say this. Podigee drew a hard line at listener-facing exposure. Mato's version doesn't draw that line the same way. It just inserts a person before publish. Elena Reyes: Which is a looser rule. Speaker 4: It's a different rule. Looser in one sense because assistants can touch more of the workflow. Tighter in another because nothing goes out the door without a human looking at it first. Elena Reyes: Okay, so if I'm running a small show, and I flip this on tomorrow, what do I actually watch for? Speaker 4: Whether your review habit actually holds up once the assistant's doing the busy work. It's easy to skim something you didn't write yourself. Elena Reyes: Oh, that's real. I do that with emails I didn't draft. Speaker 4: Everyone does that with emails they didn't draft. Elena Reyes: Like, what would actually catch me is if the assistant wrote something that sounded right but was subtly wrong, a stat off by a little, a title slightly mangled. Speaker 4: That's the exact failure mode. It reads fine. It sounds like you, and that's exactly why it's easy to wave through. Elena Reyes: So maybe the real skill is reading slower, not faster, once the assistant's involved. Speaker 4: Slower and more suspicious. Yeah. Elena Reyes: So the honest answer is this doesn't remove your judgment from the loop. It just changes what you're using your judgment on. Speaker 4: Yeah. You're not writing the episode description anymore. You're deciding whether the one an assistant wrote is right. Elena Reyes: Which is a different skill than most podcasters have been asked to practice. Speaker 4: It is. And Mato didn't build a way to test that skill. They built a smoother handoff and left the judgment part to the person on the other end. Elena Reyes: Which, going back to what we said earlier, is that convenience, or is that risk? Speaker 4: Depends entirely on whether the person doing review actually reviews. Elena Reyes: That's not a satisfying answer. Speaker 4: No, but it's the honest one. The tools got better this week. The habits didn't change on their own. Elena Reyes: Fair. Okay. I think that covers it. Speaker 4: Yeah. Between the assistant access, the review handoff, and Apple's terms sitting next to all of it. Elena Reyes: That's the changelog and the blog roundup for this week. Speaker 4: Okay, that's the review question sitting with me for the week. Yeah, same. Short pause. So where do people actually find all this? Full changelog, the blog post, everything we talked about, it's all up at hiMato.com. And if you're running a show on Mato and want to come on here and talk about it, email hello@himato.com. Elena Reyes: We mean that, by the way. We'll read it. Speaker 4: Doesn't matter if it's a two-person show or a big team. If you're using Mato and something's actually working or not working, that's the conversation we want to have. Elena Reyes: Yeah, real workflow stuff, not just the highlight reel, the stuff that actually eats your afternoon. Speaker 4: Subscribe wherever you're listening so you don't miss next week. Elena Reyes: Which, given this week, might already have another update in it. Speaker 4: Wouldn't be shocked. Elena Reyes: Either way, thanks for sticking with us through a pretty dense week of updates. Speaker 4: Appreciate you listening. Elena Reyes: Alright. Talk soon.