status — SofiaStage Events MCP Resource
status
is one of 2 resources on the
SofiaStage Events
MCP server. Connect the server and your client can attach it as context.
by client
How to attach status from your client
- Claude Code SofiaStage Events Resource/status run in your project directory
- Claude Desktop SofiaStage Events Resource/status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SofiaStage Events Resource/status ~/.cursor/mcp.json
- VS Code SofiaStage Events Resource/status .vscode/mcp.json
- Zed SofiaStage Events Resource/status ~/.config/zed/settings.json
- Windsurf SofiaStage Events Resource/status ~/.codeium/windsurf/mcp_config.json
- Cline SofiaStage Events Resource/status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SofiaStage Events Resource/status ~/.gemini/settings.json
- Grok SofiaStage Events Resource/status .mcp.json (in your project root)
- ChatGPT SofiaStage Events Resource/status Settings → Connectors → Advanced → Developer mode
- Claude.ai SofiaStage Events Resource/status Settings → Connectors → Add custom connector
- LangChain SofiaStage Events Resource/status pip install langchain-mcp-adapters
Other resources on this server
SofiaStage Events also offers 3 prompts — 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.