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