ns1_get_data_source — NS1 MCP by usefulapi MCP Tool
ns1_get_data_source
(ns1 get data source) is one of 18 tools on the
NS1 MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ns1_get_data_source from your client
- Claude Code NS1 MCP by usefulapi ns1_get_data_source run in your project directory
- Claude Desktop NS1 MCP by usefulapi ns1_get_data_source ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NS1 MCP by usefulapi ns1_get_data_source ~/.cursor/mcp.json
- VS Code NS1 MCP by usefulapi ns1_get_data_source .vscode/mcp.json
- Zed NS1 MCP by usefulapi ns1_get_data_source ~/.config/zed/settings.json
- Windsurf NS1 MCP by usefulapi ns1_get_data_source ~/.codeium/windsurf/mcp_config.json
- Cline NS1 MCP by usefulapi ns1_get_data_source ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NS1 MCP by usefulapi ns1_get_data_source ~/.gemini/settings.json
- Grok NS1 MCP by usefulapi ns1_get_data_source .mcp.json (in your project root)
- ChatGPT NS1 MCP by usefulapi ns1_get_data_source Settings → Connectors → Advanced → Developer mode
- Claude.ai NS1 MCP by usefulapi ns1_get_data_source Settings → Connectors → Add custom connector
- LangChain NS1 MCP by usefulapi ns1_get_data_source pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ns1 https://ns1.usefulapi.io/mcpOther tools on this server
- ns1_list_zones
- ns1_get_zone
- ns1_get_record
- ns1_search
- ns1_list_monitoring_jobs
- ns1_get_monitoring_job
- ns1_list_notify_lists
- ns1_list_data_sources
- ns1_list_data_feeds
- ns1_get_data_feed
- ns1_get_account_summary
- ns1_get_usage_stats
- ns1_get_qps_stats
- ns1_get_billing_records
- ns1_get_billing_queries
- ns1_create_record
- ns1_update_record
This list was read from the server itself, by connecting to it and calling tools/list on 12 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.