mcp-server-skyfire

Created By
0xtotaylora year ago
Overview

What is mcp-server-skyfire?

This project is a Model Context Protocol (MCP) server implementation that enables AI models to make payments via the Skyfire payment system, utilizing a standardized protocol.

How to use mcp-server-skyfire?

To use the server, clone the repository, install dependencies, set up your Skyfire API key in the .env file, build the project, and then run the server. You can initiate payments using the make_payment tool exposed by the server.

Key features of mcp-server-skyfire:

  • Implements the Model Context Protocol for payment functionality.
  • Exposes a make_payment tool to facilitate payments to Skyfire users.
  • Comprehensive error handling for various scenarios.

Use cases of mcp-server-skyfire:

  1. Integrating AI systems with payment processing capabilities.
  2. Automating financial transactions between users in any application utilizing the Skyfire payment infrastructure.
  3. Developing custom applications that require secure payment processing.

FAQ from mcp-server-skyfire:

  • How do I set up the project?

Clone the repository, install dependencies via npm, and configure your Skyfire API key in a .env file.

  • What technologies are used in this project?

The project is built using Node.js and TypeScript, utilizing modern JavaScript features (ES2022 compatible).

  • What happens if the payment fails?

The server implements error handling to provide appropriate error messages based on the failure scenario.

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