Session Status — SRIFT MCP Resource
Session Status
is one of 3 resources on the
SRIFT
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Session Status from your client
- Claude Code SRIFT Resource/Session Status run in your project directory
- Claude Desktop SRIFT Resource/Session Status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SRIFT Resource/Session Status ~/.cursor/mcp.json
- VS Code SRIFT Resource/Session Status .vscode/mcp.json
- Zed SRIFT Resource/Session Status ~/.config/zed/settings.json
- Windsurf SRIFT Resource/Session Status ~/.codeium/windsurf/mcp_config.json
- Cline SRIFT Resource/Session Status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SRIFT Resource/Session Status ~/.gemini/settings.json
- Grok SRIFT Resource/Session Status .mcp.json (in your project root)
- ChatGPT SRIFT Resource/Session Status Settings → Connectors → Advanced → Developer mode
- Claude.ai SRIFT Resource/Session Status Settings → Connectors → Add custom connector
- LangChain SRIFT Resource/Session Status pip install langchain-mcp-adapters
Other resources on this server
SRIFT also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.