CoreSpeed - One MCP for everything your agents need: apps, memory, tools
by•
CoreSpeed is an operating system for agents. Connect apps once and bring your accounts and shared or private memory to Claude Code, Codex, Cursor and other MCP agents. Use multiple accounts per app, including X, with web search, social research and media generation built in. CoreSpeed holds app credentials. Budgets, activity logs and Smart Approval (beta) keep agents in check. Planned: Agent Drive, Mail, Pay, sandboxes, and more. Everything your agents need, through one MCP endpoint.
Replies
Hey Product Hunt! 👋 We're the founding team of CoreSpeed.
We kept hitting the same wall: our agents were capable, but getting them to do real work meant wiring up integrations, managing credentials, and rebuilding context. After rebuilding that foundation across three products, we realized the foundation itself was the product.
So we're building CoreSpeed, an operating system for agents. Set it up once, and every MCP agent you sign in, whether Claude Code, Codex, Cursor or your own, works from the same setup:
- Your connected apps, with multiple accounts per app, like personal and company accounts on X
- Saved memory, shared with your team or kept private
- Built-in web search, social research, and image, audio and video generation. Think of this layer as OpenRouter for agent tools: no separate API keys or provider subscriptions. Just pay as you go through CoreSpeed.
- App credentials held by CoreSpeed, never handed to your agents
- Budgets, activity logs and Smart Approval (beta), where you write in plain English which actions need your OK first
Planned, not live yet: Agent Drive, Mail, Pay, sandboxes, and more.
Everything your agents need, through one MCP endpoint. Give this to your agent to start for free:
set up https://corespeed.io/SKILL.md
@miltonheyan Really cool, is there any plans to add direct integration with Slack or Discord in the future?
@miltonheyan @priya_kushwaha1 Thanks, Priya! Slack and Discord are already available as connectors. You can connect them once in CoreSpeed and use them from your MCP agent.
@miltonheyan @spencer_zhao Perfect, that's exactly what I was hoping
@miltonheyan How does smart Approval decide which actions need human confirmation ?
@dipanshu_kushwaha5 Hi Dipanshu, thanks for comment! Smart Approval checks write actions against rules you set in plain language. If approval is required—or it’s unsure how a rule applies—it pauses and asks you rather than guessing. (Jev evaluates the tool call and your rules, it uses a confidence score. If confidence score falls below the configured threshold, it asks for human confirmation instead of guessing).
More on how it works: https://corespeed.io/blog/introducing-smart-approval
@miltonheyan @dipanshu_kushwaha5 Hi Dipanshu, for example, if you are dealing with a customer complaint involves a small refund, your agents handle the ticket and make a refund without human in the loop when it stays in the "smart approval" zone, when a larger amount gated by smart approval rules.
Checkout our Smart Approval video here: https://youtu.be/-MOXwSdUSbE?si=PB-PCLYS1KhLjZND
@miltonheyan If I connect two X accounts, personal and company, how does the agent know which one to post from? Do I pick it each time, or can I set a default....??
@miltonheyan @mishaal_rashid You can name them “personal” and “company,” then tell your agent which one to use. If both are available and it doesn’t specify an account, CoreSpeed returns the choices rather than guessing.
@miltonheyan @mishaal_rashid Hi Mishaal, you don't have to pick each time. Just say "post this from the company account" and your agent knows which one you mean. If it's not clear from what you asked, it'll check with you instead of guessing.
@miltonheyan Congrats on the launch! The core idea is easy to understand: connect apps once, then make them available to different coding agents.
@miltonheyan @vipul_kumar1280 Thanks Vipul! Trying a new agent shouldn't mean reconnecting all your apps and starting its memory from scratch. That's what we're trying to fix with CoreSpeed.
@miltonheyan Can I inspect the exact action before approving it? I'd want to check both the account and the destination.
@miltonheyan @amrita_prajapati2 Yep Amrita, you can check the tool call and its arguments in the dashboard before approving it. Smart Approval cards are still pretty basic today—we're working on making those details easier to see right in the card.
@scoootscooob Thanks for your support Scott❤️
@scoootscooob thanks scott
Multiple accounts per app is the detail I like Personal and company X accounts side by side, and the agent picks the right one. I always end up logging in and out for that.
@julian_ting2 Haha yeah, the login/logout shuffle gets old fast. Multi-account support was one of those small details we really wanted to get right.
@julian_ting2 Exactly! The same idea carries over to memory: some context is just for you, some is for the team. A little like Severance, but you get to choose what to share 😄
I like that CoreSpeed supports multiple accounts for the same app. That could be handy for keeping personal and work accounts separate.
@maali_baali Thanks, Maali! You don't need switch your account from"Personal" to "Company" again and again, cuz your Agent can control them all. When u connect your account to CoreSpeed, you can choose "Private" if you want only you and your Agent to manage this account; You can also choose "Shared" to share the account access every agents in your team~
The activity logs and budgets caught my attention. Having some control over what agents can do seems important when they have access to multiple services.
@mathew_james2 Thanks, Mathew! Once agents can work across multiple services, you need to see what they’re doing and set limits you’re comfortable with. That’s why we built activity logs, spend caps, and approvals into CoreSpeed. Sharing a peek at our own dashboard below: you can see individual tool calls, what each one costs, whether it succeeded, and which actions were held for approval.
Could users choose exactly which apps or accounts each agent is allowed to access?
Not per agent yet, but we’ll be adding that soon! Today, an agent signed in as you can access your private and shared connections. You can create a separate agent identity and connect using its key to give it access to shared connections only, keeping your private accounts out of reach.
What’s your use case—which apps or accounts would you want each agent to access?
How does Smart Approval work when an agent wants to perform a sensitive action? Can users approve each request individually?
@zeeshan_ali95 Hi Zeeshan. Yes, each one gets its own approval. You see exactly what the agent wants to do and approve or reject it from Slack, email or the dashboard. What you approve is exactly what runs. This 2-minute video shows it with a $1,200 refund approved in Slack: https://youtu.be/WkJX4gyd_Yk
The activity log seems like a useful place to start a demo. It could show what the agent accessed, changed, and spent.
@wys1010 Thanks Yansong, will try it
@wys1010 I like that angle. Seeing the actual tool calls and costs makes a demo much more concrete than just watching an agent say “done.”
keeping the app credentials away from agents makes sense. if a smart approval rule is ambiguous, does the action wait for me or go through?
@jeetendra_kumar2 Thanks Jeetendra! If the evaluator isn’t confident how your rule applies, the action pauses for your approval rather than going through. You can approve or reject it via Slack, email, or the dashboard.
@miltonheyan ah nice, pausing for approval instead of blocking outright is the right call - does the approval ping show what rule it tripped on?
Is there a way to give an agent access to only a small subset of connected apps?
@jasonwu A separate agent identity is useful here—it won’t automatically get your private connections. Anything shared with the whole organization is still available, so I wouldn’t describe it as a per-agent checkbox for every app yet.
@jasonwu For now, you can create a separate agent identity and connect using its key. It can access your organization’s shared connections, but not your private ones. We’ll be adding more granular controls so you can choose exactly which apps and accounts each agent can access.