Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"seline": {
"args": [
"-y",
"@seline-analytics/mcp",
"sln_your_api_key"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Seline MCP runs over stdio and sends tool requests to the Seline public API using your API key (Settings → Integrations).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@seline-analytics/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @seline-analytics/mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
MCP server for Google Lighthouse performance metrics
MCP Security Weekly
Get CVE alerts and security updates for io.github.getseline/seline-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Seline MCP runs over stdio and sends tool requests to the Seline public API using your API key (Settings → Integrations).
{
"mcpServers": {
"seline": {
"command": "npx",
"args": ["-y", "@seline-analytics/mcp", "sln_your_api_key"]
}
}
}
Then restart Cursor so it reconnects MCP servers.
Run this command:
claude mcp add seline -- npx -y @seline-analytics/mcp sln_your_api_key
Then restart Claude Code.
If your Codex client uses mcpServers JSON config, add:
{
"mcpServers": {
"seline": {
"command": "npx",
"args": ["-y", "@seline-analytics/mcp", "sln_your_api_key"]
}
}
}
Then restart Codex and confirm the seline_* tools appear.
Data over time:
seline_get_data -> POST /api/v1/dataseline_get_charges -> POST /api/v1/chargesCounts and totals:
seline_get_top_visitors -> POST /api/v1/statsseline_get_visit_metrics -> POST /api/v1/visit-metricsseline_get_custom_events -> POST /api/v1/custom-eventsseline_get_exit_pages -> POST /api/v1/exit-pagesEvents and properties:
seline_get_events -> POST /api/v1/eventsseline_get_property_values -> POST /api/v1/property-valuesseline_get_field_keys -> POST /api/v1/event-dataseline_get_field_values -> POST /api/v1/field-valuesFunnels:
seline_get_funnel -> POST /api/v1/funnelVisitors:
seline_get_visitors -> POST /api/v1/visitorsseline_get_visitor -> POST /api/v1/visitorseline_get_visitor_events -> POST /api/v1/visitor-eventsseline_get_most_active_visitors -> POST /api/v1/most-active-visitorsseline_get_visitor_insight -> POST /api/v1/visitor-insightThis MCP server runs locally and sends requests only to the Seline API using your API key.