Back to Browse

Mayar Agent Plugin MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Mayar payments (Indonesia): invoices, payment links, products, customers, transactions and QRIS.

About

Mayar payments (Indonesia): invoices, payment links, products, customers, transactions and QRIS.

Remote endpoints: streamable-http: https://mcp.mayar.id/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-mayarid-mayar": {
      "url": "https://mcp.mayar.id/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Mayar Agent Plugin

Connect an AI agent to your Mayar account. This package uses Mayar's official hosted MCP server at https://mcp.mayar.id/mcp. With it, the agent can read and manage invoices, payment links, products, customers, transactions, memberships, coupons, webhooks, reviews, QRIS and license codes.

This is a Portable Agent Plugins v1 package (plugin.json, mcp.json and skills/). It is configuration only. It contains no executable code.

Requirements

  • A Mayar account.
  • A production API key. Get it in the Mayar dashboard under Integration > Api Keys (web.mayar.id/api-keys).

Install in Hermes Agent

hermes plugins install mayarid/mayar-agent-plugin --no-enable
hermes plugins enable mayar

Set your API key (see below). Restart Hermes. Then ask: "Use Mayar. Call the account tool with action balance." A working key returns your balance.

Install in Cursor

Add to Cursor

The button adds Mayar's hosted MCP server to Cursor. Set MAYAR_API_KEY first (see below). This repository also includes a Cursor config file at .mcp.json. Cursor and cursor.directory read that root file. It uses Cursor's ${env:MAYAR_API_KEY} syntax. Do not change it for Claude Code.

Install in Claude Code

This repository also ships a Claude plugin in plugins/mayar (manifest, skill, license, and a Claude .mcp.json). Anthropic's directory can list that subfolder through the submission "Plugin path" field. The root .mcp.json stays the Cursor file, because the two clients authenticate differently.

Claude Code requires "type": "http" on a remote server. The plugin file at plugins/mayar/.mcp.json sends Authorization: Bearer ${user_config.mayar_api_key}. Claude Code asks for that key when you install or enable the plugin in a session. It stores the key outside settings.json (macOS Keychain, or ~/.claude/.credentials.json with mode 600 on Linux). It does not read MAYAR_API_KEY from the environment, and it does not expand ${env:MAYAR_API_KEY}.

Load the plugin from a local clone:

claude --plugin-dir ./plugins/mayar

Or add this repository as a marketplace and install mayar:

claude plugin marketplace add mayarid/mayar-agent-plugin
claude plugin install mayar@mayarid

A --plugin-dir or shell install does not open the key dialog. In a Claude Code session, run /plugin configure on the installed plugin to set the key. For a marketplace install, that command is /plugin configure mayar@mayarid. You can also pass --config mayar_api_key=YOUR_KEY to claude plugin install. See Claude Code under Set your API key.

You can still add the server by hand with claude mcp add (see Claude Code under Set your API key). Mayar has no OAuth. On claude.ai and in Cowork, the plugin skill loads, but the Connectors tab expects an OAuth sign-in that Mayar does not offer, so tool calls there cannot authenticate with an API key the way Claude Code can.

Set your API key

Mayar does not use OAuth. Every client sends your production API key in the Authorization header. Get the key in the Mayar dashboard: Integration > Api Keys (web.mayar.id/api-keys).

Cursor

Set the MAYAR_API_KEY environment variable. The Add to Cursor button and .mcp.json send it as Authorization: Bearer ${env:MAYAR_API_KEY}.

Hermes

Put the key in ~/.hermes/.env, or set it in the plugin settings form:

MAYAR_API_KEY=your-production-key

Agent Plugins v1.0.0 does not allow secrets or placeholders in mcp.json remote headers. Hermes does not yet attach this key from the plugin extension alone. Add this block to your Hermes config.yaml so Hermes sends the header. A same-name entry replaces the package server, so keep trust: untrusted:

mcp_servers:
  mayar:
    url: https://mcp.mayar.id/mcp
    headers:
      Authorization: "Bearer ${MAYAR_API_KEY}"
    trust: untrusted

Claude Code

When you install or enable the plugin in a Claude Code session, Claude Code asks for your production API key and stores it outside settings.json (macOS Keychain, or ~/.claude/.credentials.json with mode 600 on Linux). To set or change the key later, run /plugin configure mayar@mayarid in a session. Get a key from https://web.mayar.id/api-keys.

If you installed the plugin from the shell, Claude Code does not prompt for the key. Pass --config mayar_api_key=YOUR_KEY on install, or run /plugin configure mayar@mayarid afterward and restart Claude Code.

If you installed the plugin in plugins/mayar, Claude Code reads Authorization: Bearer ${user_config.mayar_api_key} from that folder's .mcp.json. To add the server by hand instead:

claude mcp add --transport http mayar https://mcp.mayar.id/mcp \
  --header "Authorization: Bearer $MAYAR_API_KEY"

The shell expands $MAYAR_API_KEY when you run the command. This by-hand server does not use the plugin's userConfig field.

Other clients

The same server works in any MCP client that speaks Streamable HTTP. Send the key in the Authorization header. The Bearer prefix is optional. The server URL is https://mcp.mayar.id/mcp.

Tools

Each domain is one tool with an action argument: account, invoice, installment, customer, transaction, product, payment, membership, credit, coupon, webhook, review, qr, license and search_docs. The full reference is at mcp.mayar.id/docs.

Disclosure

  • Every tool call goes to https://mcp.mayar.id, which calls the Mayar production API (api.mayar.id) with your key.
  • Write actions use real money and live data. They can create or update invoices, payment links, products, customers and coupons, change membership status, change the webhook URL and add or spend credits.
  • The package marks the server untrusted. Hermes asks you before each write-capable call.
  • Account data that the tools return (customers, transactions, balances) goes to your model provider.
  • The tool list comes from the server at run time. The pinned commit does not cover it.
  • The plugin stores no credentials. You set MAYAR_API_KEY in the client. This package's mcp.json does not include an Authorization header.

License

MIT

Reviews

No reviews yet

Be the first to review this server!