Remote MCP over Streamable HTTP

Connect an MCP client to https://txt-fil.es/mcp. Grok, Claude, Cursor, Codex, and other OAuth-capable clients can discover txt's authorization server, register as public clients, use PKCE, and ask you to approve scoped access after you sign in with dots. A scoped txt_… bearer key from /sync remains available for clients that support manual headers.

The endpoint uses the standard JSON-RPC initialization and tool-list flow over Streamable HTTP. Its public registry-shaped manifest is available at /.well-known/mcp.json, with a server card at /mcp/server-card. OAuth protected-resource and authorization-server metadata are published under /.well-known/.

Start with list-files or list-skills. Read only resources relevant to the request. Use trash_note for ordinary removal; permanent purge applies only to an already-trashed note and requires explicit confirmation. MCP tool listings describe their inputs at runtime, so clients should not infer capabilities from marketing text.

{
  "mcpServers": {
    "txt": {
      "url": "https://txt-fil.es/mcp",
      "headers": { "Authorization": "Bearer txt_…" }
    }
  }
}