trend_resource — DataPulse MCP Resource

trend_resource is one of 8 resources on the DataPulse MCP server. Connect the server and your client can attach it as context.

by client

How to attach trend_resource from your client

• Claude Code DataPulse Resource/trend_resource run in your project directory
• Claude Desktop DataPulse Resource/trend_resource ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor DataPulse Resource/trend_resource ~/.cursor/mcp.json
• VS Code DataPulse Resource/trend_resource .vscode/mcp.json
• Zed DataPulse Resource/trend_resource ~/.config/zed/settings.json
• Windsurf DataPulse Resource/trend_resource ~/.codeium/windsurf/mcp_config.json
• Cline DataPulse Resource/trend_resource ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI DataPulse Resource/trend_resource ~/.gemini/settings.json
• Grok DataPulse Resource/trend_resource .mcp.json (in your project root)
• ChatGPT DataPulse Resource/trend_resource Settings → Connectors → Advanced → Developer mode
• Claude.ai DataPulse Resource/trend_resource Settings → Connectors → Add custom connector
• LangChain DataPulse Resource/trend_resource pip install langchain-mcp-adapters

Other resources on this server

• dataset_index
• anomaly_resource
• reliability_summary
• drift_resource
• reconciliation_resource
• attestation_resource
• licence_summary

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.