Ctxt MCP server
{
"mcpServers": {
"ctxt": {
"type": "http",
"url": "https://ctxt.io/mcp"
}
}
}{
"mcpServers": {
"ctxt": {
"type": "http",
"url": "https://ctxt.io/mcp"
}
}
}{
"mcpServers": {
"ctxt": {
"type": "http",
"url": "https://ctxt.io/mcp"
}
}
}{
"servers": {
"ctxt": {
"type": "http",
"url": "https://ctxt.io/mcp"
}
}
}{
"mcpServers": {
"ctxt": {
"type": "http",
"url": "https://ctxt.io/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Ctxt provides tools to create auto-expiring links that share text, markdown, code, or HTML output from agents. It is for developers who want to share agent-generated content with configurable expiry times and optional password protection.
- Generate shareable links to agent output that expire automatically after a set time period.
- Store and retrieve temporary context or generated content using bearer tokens and optional passwords.
- Delete previously shared content using deletion tokens to manage what remains accessible.
Tools this server exposes
| Tool | Does |
|---|---|
| create_context | Create an auto-expiring link for text, markdown, code, or HTML content with configurable TTL and optional password protection. |
| read_context | Retrieve content from a previously created context link using its URL and optional password. |
| delete_context | Remove shared content from the server using its deletion token. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.