Seline MCP

MCP serverDatabases & data

MCP server for the Seline Analytics API

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use Seline MCP

From the project's README

As published by getseline/seline-mcp in README.md.

 

Seline MCP talks to the Seline public API.

You can connect in two ways:

  • Hostedhttps://api.seline.com/mcp (OAuth, for ChatGPT / Claude)
  • Local stdionpx @seline-analytics/mcp with an API key (Cursor / Claude Code / Codex)

For the local server you can use either:

  • A project API token — scoped to one project
  • An account API token — access to all projects on the account

With an account token, use seline_list_projects to find a project, then pass projectId on analytics tools.

Cursor setup

{
  "mcpServers": {
    "seline": {
      "command": "npx",
      "args": ["-y", "@seline-analytics/mcp", "sln_your_api_key"]
    }
  }
}

Then restart Cursor so it reconnects MCP servers.

Claude Code setup

Run this command:

claude mcp add seline -- npx -y @seline-analytics/mcp sln_your_api_key

Then restart Claude Code.

Codex setup

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.

Tools

Projects:

  • seline_list_projects -> POST /api/v1/projects

Data over time:

  • seline_get_data -> POST /api/v1/data
  • seline_get_charges -> POST /api/v1/charges

Counts and totals:

  • seline_get_top_visitors -> POST /api/v1/stats
  • seline_get_pages -> POST /api/v1/pages
  • seline_get_visit_metrics -> POST /api/v1/visit-metrics
  • seline_get_custom_events -> POST /api/v1/custom-events

Events and properties:

  • seline_get_events -> POST /api/v1/events
  • seline_get_property_values -> POST /api/v1/property-values
  • seline_get_field_keys -> POST /api/v1/event-data
  • seline_get_field_values -> POST /api/v1/field-values

Funnels:

  • seline_get_funnel -> POST /api/v1/funnel

Visitors:

  • seline_get_visitors -> POST /api/v1/visitors
  • seline_get_visitor -> POST /api/v1/visitor
  • seline_get_visitor_events -> POST /api/v1/visitor-events
  • seline_get_most_active_visitors -> POST /api/v1/most-active-visitors
  • seline_get_visitor_insight -> POST /api/v1/visitor-insight

Privacy Policy

This MCP server runs locally and sends requests only to the Seline API using your API key.

  • Data collected: Your API key (stored locally in your MCP client) and analytics queries you run through the tools.
  • Usage: The API key authenticates read-only requests to your Seline workspace.
  • Storage: Seline stores analytics per Seline Privacy Policy.
  • Third parties: Requests go to Seline infrastructure only.
  • Retention: Governed by Seline account and privacy policy.
Advanced
Delivery
seline-mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
io-github-getseline-seline-mcp
Source
github.com/getseline/seline-mcp
Hosted endpoint
https://api.seline.com/mcp