Payman AI Documentation MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Payman AI Documentation MCP Server?

Payman AI Documentation MCP Server is a server that provides easy access to Payman AI's documentation, enabling developers to build integrations more efficiently with AI assistants.

how to use Payman AI Documentation MCP Server?

To use the server, clone the repository, install the necessary dependencies, build the project, and check if the server is properly set up. Once running, it can be integrated with AI assistants like Claude or Cursor.

key features of Payman AI Documentation MCP Server?

  • Provides access to comprehensive Payman AI documentation.
  • Enhances AI assistants' ability to answer integration questions.
  • Supports local server setup for development purposes.

use cases of Payman AI Documentation MCP Server?

  1. Assisting developers in integrating Payman AI with their applications.
  2. Enabling AI assistants to provide accurate information about Payman AI capabilities.
  3. Facilitating quick access to documentation for troubleshooting and development.

FAQ from Payman AI Documentation MCP Server?

  • What are the prerequisites for running the server?

You need Node.js (v14 or higher), npm or yarn, and Git.

  • How do I check if the server is set up correctly?

You can run the command node /ABSOLUTE/PATH/TO/PARENT/FOLDER/payman-doc-mcp-server/build/index.js to verify the setup.

  • Can I integrate this server with any AI assistant?

Yes! The server can be integrated with AI assistants like Claude and Cursor.

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