Northbeam MCP Server

Created By
mattcoatswortha year ago
Overview

what is Northbeam MCP Server?

Northbeam MCP Server is a Model Context Protocol (MCP) server designed for accessing Northbeam marketing analytics data, providing tools for querying various metrics and performance data.

how to use Northbeam MCP Server?

To use the Northbeam MCP Server, install the necessary dependencies, create a .env file with your Northbeam API key and brand name, and run the server using npm commands.

key features of Northbeam MCP Server?

  • Access to Northbeam marketing analytics data
  • Tools for querying metrics, dimensions, and channel performance
  • Cohort analysis and attribution data retrieval

use cases of Northbeam MCP Server?

  1. Analyzing marketing channel performance metrics.
  2. Conducting cohort analysis for targeted marketing strategies.
  3. Retrieving attribution data to understand customer journeys.

FAQ from Northbeam MCP Server?

  • What is required to set up the Northbeam MCP Server?

You need to install dependencies, create a .env file with your API key and brand name, and run the server.

  • Can I test the server before using it?

Yes! You can use the MCP Inspector to test all available tools and resources.

  • Is it possible to use Northbeam MCP Server as an npm package?

Yes! You can use it as an npm package with the command npx northbeam-mcp.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago