The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Seline listing page.
Seline MCP runs over stdio and sends tool requests to the Seline public API using your API key (Settings → Integrations).
You can use either:
With an account token, use seline_list_projects to find a project, then pass projectId on analytics tools.
Then restart Cursor so it reconnects MCP servers.
Run this command:
Then restart Claude Code.
If your Codex client uses mcpServers JSON config, add:
Then restart Codex and confirm the seline_* tools appear.
Projects:
seline_list_projects -> POST /api/v1/projectsData 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_pages -> POST /api/v1/pagesseline_get_visit_metrics -> POST /api/v1/visit-metricsseline_get_custom_events -> POST /api/v1/custom-eventsEvents 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.