CoreSpeed

io.corespeedPublished by corespeed.ioOfficial publisherv1.0.0Updated Nov 3, 2026

One MCP for any agent: your connected apps, shared memory, web search, social data and media tools.

VerifiedStreamable HTTPWeb executable

Server details

Identifier: io.corespeed/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Nov 3, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to corespeed.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.corespeed%2Fmcp.svg)](https://sourceweft.com/mcp/io.corespeed%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

CoreSpeed's hosted MCP server (api.corespeed.io), published by corespeed.io; OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher: corespeed.io
Endpoint: api.corespeed.io
Last checked: Nov 3, 2026

Installation

In SourceWeft

Open CoreSpeed in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.corespeed%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "corespeed": {
      "type": "http",
      "url": "https://api.corespeed.io/mcp"
    }
  }
}

README

CoreSpeed for coding agents

CoreSpeed gives an agent one MCP server, https://api.corespeed.io/mcp, that carries the tools of every app your organization has connected (Notion, Slack, GitHub, X, Linear, and more), long-term memory shared across agents, a Drive every tool reads and writes, media generation and understanding, live web search, and public social data, all billed to one wallet with spend caps and an audit trail.

This repository holds the CoreSpeed plugin for Claude Code, Codex and Cursor, and the agent skills it bundles. The cs command-line tool is published to npm as @corespeed/cs.

Claude Code

Inside Claude Code the same is /plugin marketplace add corespeed-io/cs, then /plugin install corespeed@corespeed. Start a new session, run /mcp, pick the CoreSpeed server, and authenticate in the browser.

Codex

Start a new Codex task. When CoreSpeed shows Authentication required, select Authenticate (or open Settings → MCP servers → CoreSpeed) and finish the sign-in in the browser. In the ChatGPT desktop app the plugin appears under the CoreSpeed marketplace once it has been added.

Codex installs the self-contained plugins/corespeed-directory/ package. It uses https://api.corespeed.io/mcp/plugin/chatgpt: nine memory operations, current identity and completion of memory write approvals. Its corespeed-memory skill guides recall, saving, correction, memory links and deletion. New memories are private unless you ask to share them. This is the package prepared for OpenAI Directory review; it contains no general CLI or HTTP API skill and does not operate connected apps or files. It requires the narrowed memory contract to be deployed before installation or submission. It keeps the same MCP URL already configured for the plugin; there is no server-address migration.

Claude Code keeps the full server and the CLI/API skills in plugins/corespeed/. Cursor uses that package with the same memory-only plugin endpoint, plus the broader CLI/API skills. Codex has one manifest, in plugins/corespeed-directory/.

Codex, CLI only

This plugin registers no MCP server. Its cs-cli skill has the agent install the cs command-line tool, sign in once in the browser, and then find and call CoreSpeed tools from the shell (cs mcp search, cs mcp get, cs mcp call), and move files in and out of the organization's Drive (cs drive put, cs drive get). Pick it when Codex cannot load your organization's full tool list, or when you want every call to go through the shell. It remains available separately from the repository marketplace. It is not part of the Directory memory package, and its availability here is not an OpenAI approval.

Cursor and Grok Bot

In Cursor, open Customize, search the Marketplace for CoreSpeed, and install it. Pick the CoreSpeed MCP server and sign in in the browser when Cursor asks. Grok Bot loads plugins from the Cursor Marketplace, so the same plugin works there.

Cursor reads the legacy package's root .mcp.json, so its server is the plugin surface https://api.corespeed.io/mcp/plugin/chatgpt: the same eleven memory, identity and approval operations as the Directory package. A connected app's tools and the organization's Drive are reached through the bundled cs-cli skill (cs mcp call, cs drive).

To try this repository before a Marketplace release, copy plugins/corespeed to ~/.cursor/plugins/local/corespeed and reload the window.

The `cs` CLI

cs signs you in through the browser, mints sk-cs- API keys for CI, switches organizations, connects apps, and calls tools from a terminal. See the CLI docs.

What the plugins contain

Plugin	Part	What it does
Codex `corespeed` (`plugins/corespeed-directory/`)	MCP and `corespeed-memory` skill	Eleven individually exposed memory, identity and approval operations; no app connections, files or generic executor.
Claude/Cursor `corespeed` (`plugins/corespeed/`)	MCP server	Browser sign-in (OAuth 2.1 + PKCE), never a pasted key. Claude Code: the full `https://api.corespeed.io/mcp`. Cursor: the plugin surface `https://api.corespeed.io/mcp/plugin/chatgpt` (memory, identity and approvals).
Claude/Cursor `corespeed`	`cs-cli` skill	Using the `cs` CLI: sign-in, finding and calling tools from a shell, memory, files in the Drive, API keys, organizations, connectors, remote MCP servers, credit.
Claude/Cursor `corespeed`	`cs-api` skill	Calling CoreSpeed over HTTP from code and CI: credentials, `tools/list` and `tools/call`, error codes, credits.
`corespeed-cli`	`cs-cli` skill	The same skill, and nothing else: no MCP server is registered.

The public Directory upload is only plugins/corespeed-directory/, with the manifest at its root under .codex-plugin/. Do not upload this entire repository or the legacy plugins/corespeed/ package. Run python3 scripts/check-directory.py before packaging. CI checks the exact file inventory so a broader skill cannot enter the upload accidentally.

Standalone CLI installation remains your choice, using npm or the separate corespeed-cli plugin above. The memory plugin neither requires nor installs it and does not use it to complete an unavailable or denied operation. CLI sign-in is separate; plugin credentials are not copied.

If you added CoreSpeed to your client by hand earlier (claude mcp add, codex mcp add, or an entry in Cursor's mcp.json), remove that entry before installing the plugin, so every tool is registered once.

Sign-in happens at login.corespeed.io, and the plugins' only servers are https://api.corespeed.io/mcp and https://api.corespeed.io/mcp/plugin/chatgpt. Anything else claiming to be CoreSpeed is not this plugin.

Other clients

Copilot in VS Code, Claude.ai, ChatGPT, and any client that speaks Streamable HTTP with MCP authorization connect with the URL alone. Per-client setup is at https://corespeed.io/docs/mcp.

License

Apache-2.0

Source: README.md at commit 231befd

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestNov 3, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts