mcp-server-creem

Created By
ffhra year ago
Model Context Protocol (MCP) Server for Creem.io – Enhancing Merchant of Record services with transparent billing and improved fees.
Overview

what is mcp-server-creem?

The mcp-server-creem is a Model Context Protocol (MCP) Server designed for Creem.io, aimed at enhancing Merchant of Record services by providing transparent billing and improved fee structures.

how to use mcp-server-creem?

To use mcp-server-creem, integrate it with your existing Merchant of Record services to streamline billing processes and gain insights into fee structures.

key features of mcp-server-creem?

  • Transparent billing processes for merchants
  • Improved fee management and reporting
  • Integration capabilities with existing systems

use cases of mcp-server-creem?

  1. Enhancing billing transparency for online merchants.
  2. Streamlining fee management for e-commerce platforms.
  3. Providing detailed reports on transaction fees and billing.

FAQ from mcp-server-creem?

  • What is the purpose of mcp-server-creem?

It enhances Merchant of Record services by providing transparent billing and improved fee management.

  • Is mcp-server-creem easy to integrate?

Yes! It is designed to be easily integrated with existing systems.

  • What kind of reporting does mcp-server-creem provide?

It offers detailed reports on transaction fees and billing processes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ffhr
Star
0
Language
-
License
MIT license
Category
finance

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