Jampp MCP Server

Created By
springwqa year ago
Overview

what is Jampp MCP Server?

Jampp MCP Server is a server that provides access to the Jampp Reporting API through the Model Context Protocol, enabling LLMs to fetch campaign performance data.

how to use Jampp MCP Server?

To use the Jampp MCP Server, clone the repository, install the necessary dependencies, set up your environment variables with your Jampp API credentials, and run the server using Python.

key features of Jampp MCP Server?

  • OAuth 2.0 authentication with automatic token refresh
  • GraphQL-based API integration
  • Campaign spend reporting
  • Daily spend tracking
  • Comprehensive performance metrics
  • Asynchronous report generation and retrieval
  • Available metrics and dimensions listing

use cases of Jampp MCP Server?

  1. Fetching campaign spend data for specific date ranges.
  2. Tracking daily spend for marketing campaigns.
  3. Generating comprehensive performance reports for analysis.
  4. Integrating with Claude Desktop for enhanced reporting capabilities.

FAQ from Jampp MCP Server?

  • What are the prerequisites for using Jampp MCP Server?

You need Python 3.10 or higher and Jampp API credentials (Client ID and Client Secret).

  • How do I install the Jampp MCP Server?

Clone the repository, install dependencies using pip, and set up your environment variables.

  • Can I use this server with Claude Desktop?

Yes! You can configure Claude Desktop to use the Jampp MCP Server for reporting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
springwq
Star
0
Language
Python
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)

a day ago