Context — ctxt.io

io.ctxtPublished by ctxt.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Share text, markdown, code, or HTML as auto-expiring links

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A remote ctxt.io server that lets an assistant publish text, markdown, code or HTML as auto-expiring shareable links, read them back, and delete them.

What you can do
Create shareable links from text, markdown, code or self-contained HTML, with a chosen expiry and optional name or password on paid tiers; scripts are stripped and never run, so HTML stays static. Read the content of an existing link from a full URL, path or bare code, supplying a password for protected links. Delete a link you created using the delete token returned at creation, which immediately removes public access.
When to use it
Useful when an assistant produces output a person needs to view or hand to someone else — a report, table, diagram or code snippet — and a short-lived public link is more convenient than a file attachment. Also handy for retrieving content from a link someone shares back.
Requirements
A remote streamable HTTP endpoint; no account, authentication, API key or local runtime is needed. Some clients install it as a plugin or via a config entry pointing at the endpoint. Network access is required.
Before you install
Links are bearer-accessible by default: anyone with the URL can read them, so do not share secrets. The delete token is a deletion capability and should be treated as a secret. Deletion is immediate and not undoable, so confirm before calling it. Longer expiries and Pro options such as name and password cost a one-time fee completed through a payment link a human opens.

Installation

In SourceWeft

  1. Open Context — ctxt.io in the dashboard and add it to a workspace.
  2. 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.ctxt%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.

{
  "mcpServers": {
    "context-ctxt-io": {
      "type": "http",
      "url": "https://ctxt.io/mcp"
    }
  }
}

README

ctxt.io for agents

[ci]

Share whatever your agent produces as auto-expiring links. This repo packages the ctxt.io MCP server for agent runtimes: a Claude Code plugin (MCP + share skill), a Codex plugin, a Cursor plugin, and install recipes for VS Code and claude.ai.

  • Claude directory plugin: https://ctxt.io/mcp/openai (free public links, no ads or checkout). The endpoint is usable by any MCP client.
  • General MCP endpoint: https://ctxt.io/mcp (Codex, Cursor, and direct clients; streamable HTTP, no auth, no account)
  • Tools: create_context, read_context, delete_context
  • Free expiries: 5m – 1d. On the general endpoint, ttl=30d and Pro options (name, password) cost $1 one-time; the tool result says how payment completes — a payment_url a human opens, plus any agent-payment capability the server currently advertises.

Claude Code (plugin — recommended)

Run these one at a time in Claude Code (pasting both lines at once doesn't work):

  1. Add the marketplace:

    /plugin marketplace add ctxt-io/ctxt-agents

  2. Install the plugin:

    /plugin install ctxt@ctxt

You get the MCP server and a share skill that teaches Claude when to share and how to produce good-looking HTML output (self-contained HTML + inline SVG — scripts are stripped server-side, so static only). The skill also registers the /ctxt:share slash command. This bundle uses the free directory endpoint with public links lasting up to one day. See the plugin README for data handling and retention.

MCP server only, no plugin (--scope user makes it available in every project; drop it to add it to the current project only):

claude mcp add --scope user --transport http ctxt https://ctxt.io/mcp/openai

Codex

Codex plugin (bundles the MCP server + the share skill; lives in codex/ctxt/ with a .codex-plugin/plugin.json manifest):

bash
codex plugin marketplace add ctxt-io/ctxt-agentscodex plugin add ctxt@ctxt

MCP server only — add to ~/.codex/config.toml:

toml
[mcp_servers.ctxt]url = "https://ctxt.io/mcp"

Skill only — Codex loads skills from ~/.agents/skills (open Agent Skills format):

bash
mkdir -p ~/.agents/skillscp -r codex/ctxt/skills/share ~/.agents/skills/ctxt-share

Cursor

One-click install (opens Cursor with the server pre-filled):

Add to Cursor

Cursor plugin (bundles the MCP server + the share skill, which Cursor registers as /share; lives in cursor/ctxt/ with a .cursor-plugin/plugin.json manifest, and the repo root carries a .cursor-plugin/marketplace.json so the whole repo can be added as a marketplace):

Cursor → Settings → Tools & MCP → add marketplace → ctxt-io/ctxt-agents

MCP server only, by hand — add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

json
{  "mcpServers": {    "ctxt": { "url": "https://ctxt.io/mcp" }  }}

VS Code

Add to .vscode/mcp.json — note VS Code uses a top-level servers map, not mcpServers:

json
{  "servers": {    "ctxt": { "type": "http", "url": "https://ctxt.io/mcp" }  }}

claude.ai / Claude Desktop

Customize → Connectors → Add custom connector → https://ctxt.io/mcp (no auth).

Any other MCP client

Point it at https://ctxt.io/mcp: stateless streamable HTTP, plain JSON responses, no authentication.

Notes

  • Links are bearer-accessible by default — anyone holding the URL can read them; password-protected (Pro) links additionally require the password. Don't share secrets.
  • The delete_token returned at creation is a deletion capability. Treat it as a secret and keep it out of shared content.
  • Claude has a directory-specific sharing skill. Codex and Cursor keep identical general-service skills; CI checks both variants point at their intended endpoints.
  • Releasing: bump version in all three plugin manifests together (Claude only updates installed plugins when the version changes) and tag the release; CI checks the manifests stay in sync.
  • Docs: https://ctxt.io/mcp/docs · Terms: https://ctxt.io/tos · Privacy: https://ctxt.io/privacy
  • Security reports: see SECURITY.md.

License

MIT

Source: README.md at commit 6274b2f

Tools

3

create_context

Create a ctxt.io share link

Share text, markdown, code, or HTML as an auto-expiring ctxt.io link. For visual output (styled reports, tables, charts, diagrams) prefer format=html with self-contained HTML: inline CSS and inline SVG render fully; <script> is stripped server-side and JavaScript never runs, so keep it static. Free expiries: 5m, 30m, 1h (default), 8h, 1d — these return the share URL immediately. ttl=30d and the Pro options (name, password) cost $1 one-time: the link is created in a pending state and the result includes a payment_url a human can open in a browser to complete checkout (platforms enrolled for agentic payments receive an acp block instead and can pay programmatically); until payment the link lives 1 day without Pro features. Anyone with the link can read it. The returned delete_token authorizes deletion via delete_context — keep it private.

Parametersttllangnameformatcontentrequiredpassword

read_context

Read a ctxt.io link

Fetch the content of an existing ctxt.io link. Accepts a full ctxt.io URL, a /3/<code> path, or a bare code. Password-protected links need the password argument.

Parametersformatpasswordurl_or_keyrequired

delete_context

Delete a ctxt.io link

Delete a ctxt.io link you created. Requires the delete_token returned by create_context. Immediately removes public access and requests backing-storage deletion. Destructive and not undoable — confirm with the user before calling.

Parametersurl_or_keyrequireddelete_tokenrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts