Launched this week
CoreSpeed
One MCP for everything your agents need: apps, memory, tools
605 followers
One MCP for everything your agents need: apps, memory, tools
605 followers
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.
How does an agent choose among the available media-generation tools? Can the user specify a preferred provider?
@eexlkuang_se Yep, you can ask for a specific model. The agent can check the available image, video and audio models and their inputs before choosing, so you don’t have to leave that choice entirely up to it.
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 😄
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.”
@scoootscooob Thanks for your support Scott❤️
@scoootscooob thanks scott
The activity logs caught my attention more than the one MCP part. Once agents start doing more things on their own being able to see what actually happened becomes pretty important. How detailed are the logs?
@zubaran_k You can see which identity called which tool, when, whether it succeeded, and any associated charge. Calls that failed or stopped for approval show up too. It’s useful for finding the step where things went sideways.
@axelkane The activity trail focuses on the action and outcome, with sensitive metadata redacted before storage. It isn’t intended to keep a copy of your prompts. I still need to confirm the custom field-exclusion part before giving you a definite yes on that.
We keep raw tool arguments and conversation prompts out of the activity log. It records who called which tool, when, the outcome, and any cost. Failed calls also include an error code and a brief error message, so you can troubleshoot without storing the full request payload.
Connecting an app once and reusing the same accounts and memory across Claude Code, Codex and Cursor solves a real annoyance, since everyone ends up wiring the same integrations over and over. Supporting multiple accounts per app is a thoughtful detail. How do you keep shared versus private memory separated between agents?
@karimbenkeroum Good question Ben, for the memory part, the default option is "privet", if you want to switch it to "shared", you can just tell your agent"make this memory to be shared", or you can visit the CoreSpeed dashboard to switch it to "Org Shared".
@karimbenkeroum One distinction worth adding: private memory belongs to your identity, not to a particular agent client. So Claude Code and Codex signed in as you can use the same private memories, while another teammate cannot. Shared memories are currently available across your organization. We’re also rolling out more granular controls so you can choose who to share them with.