MCP server for the Seline Analytics API
Seline MCP talks to the Seline public API.
You can connect in two ways:
https://api.seline.com/mcp (OAuth, for ChatGPT / Claude)npx @seline-analytics/mcp with an API key (Cursor / Claude Code / Codex)For the local server you can use either:
With an account token, use seline_list_projects to find a project, then pass projectId on analytics tools.
{
"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.
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @seline-analytics/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-getseline-seline-mcp": {
"command": "npx",
"args": [
"-y",
"@seline-analytics/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@seline-analytics/mcpnpmSeline works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.