Follow these best practices to get more accurate insights and use Insider One MCP securely.
Write effective prompts
When querying Insider One MCP, always:
Specify the channel type, such as Email, SMS, or Web Push.
Include the date range you want to analyze.
Clearly describe the metrics or analysis you need.
These details help the AI client map your request to the correct analytics functions and return more accurate results.
Example: Discover available functions
Prompt: What analytics functions are available through Insider One MCP?
Output: A list of all available MCP functions organized by channel, so you can understand what you can query before writing detailed prompts.
Example: List and export campaign data
Prompt: List my Email campaigns that were activated over the last month.
Output:
List of campaigns
Campaign type
Campaign details
Example: Channel performance overview
Prompt: Give me the top metrics for Web Push campaigns.
Output:
Targeted audience
Top metrics
Performance issues that may require investigation
Example: Trend analysis over time
Prompt: How has email conversion rate changed over the last month?
Output:
Performance trends over time
Spikes or drops that may require investigation
Overall momentum of a channel or metric
Example: Channel performance comparison
Prompt: Compare Email, SMS, and Push performance for the last 7 days.
Output:
Which channels drive the most engagement or conversions
Relative performance differences
Which channels may need optimization
This approach removes the need to manually export reports or switch between multiple dashboard views.
Insider One MCP returns answers generated by an AI model based on live data. Always cross-check critical figures, such as revenue, conversion rates, or campaign counts, directly in the Insider One dashboard before making decisions.
Depending on your AI client, you may be able to export MCP query results to a file, such as CSV or TXT. This functionality is handled by the client, not by Insider One MCP itself. Refer to your client’s documentation for available export options.
Security best practices
Model Context Protocol (MCP) is a newly introduced open protocol and may be susceptible to security issues or vulnerabilities. Follow your organization’s security policies and review configurations carefully.
Your MCP client configuration file contains sensitive API keys. Treat it as a secret at all times.
Practice | Detail |
|---|---|
Do not commit to source control | Never add your configuration file to Git or any shared repository. |
Do not share screenshots with keys | Blur or redact API key values before sharing configuration screenshots. |
Restrict file access permissions | Limit who can read the configuration file on your machine. |
Rotate keys immediately if exposed | Regenerate any key you suspect has been exposed to an unauthorized party. |
Use dedicated, least-privilege keys | Create separate keys per channel exclusively for Insider One MCP. Do not reuse existing keys. |
If you need to share your configuration for troubleshooting purposes, always remove the actual key values before sharing.