Skip to main content
Glama
theYahia

paymongo-mcp

by theYahia

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAYMONGO_SECRET_KEYYesSecret API key from PayMongo dashboard

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_payment_intentA

Create a PayMongo payment intent — the object that tracks a payment through its lifecycle.

get_payment_intentA

Retrieve a PayMongo payment intent by its ID.

create_sourceA

Create a GCash/GrabPay payment source (returns a redirect checkout URL).

get_sourceB

Retrieve a payment source by its ID.

create_paymentA

Charge a chargeable source to create a payment (moves money).

list_paymentsA

List payments with cursor pagination (before/after by payment ID).

create_refundA

Refund a payment, fully or partially (moves money back to the customer).

create_checkoutA

Create a hosted checkout session (returns a checkout URL).

get_checkoutB

Retrieve a checkout session by its ID.

create_linkA

Create a PayMongo Payment Link (no-code shareable checkout). Returns a checkout_url and reference_number.

get_linkA

Retrieve a Payment Link by link_id, or look it up by reference_number.

archive_linkB

Archive or unarchive a Payment Link.

create_webhookA

Register a webhook endpoint for event delivery. The response includes the per-webhook signing secret (store it to verify signatures).

list_webhooksA

List all registered webhooks.

get_webhookA

Retrieve a webhook by its ID.

update_webhookA

Update a webhook's URL/events and/or enable/disable it. Provide any combination of url, events, enabled.

verify_webhook_signatureA

Locally verify a PayMongo webhook's 'Paymongo-Signature' header (HMAC-SHA256 over timestamp.body). No network call — uses the per-webhook signing secret you pass in.

create_payment_methodA

Create a payment method (e.g. a card) to attach to a payment intent. Handle card data with care.

get_payment_methodA

Retrieve a payment method by its ID.

create_customerA

Create a customer record (stores PII for reuse across payments).

get_customerA

Retrieve a customer by its ID.

list_customersA

List customers with cursor pagination (before/after by customer ID).

get_refundA

Retrieve a refund by its ID.

list_refundsA

List refunds with cursor pagination (before/after by refund ID).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 24 tools

Disambiguation4/5

Tools are mostly distinct, each targeting a specific resource and action. However, create_checkout, create_link, and create_source all initiate payment collection and could be confused by an agent; their descriptions partially mitigate this.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_, create_, list_, update_, archive_, verify_). There are no mixed naming conventions or vague verbs.

Tool Count4/5

24 tools is on the heavier side but appropriate for a payment API covering multiple resources (payments, refunds, checkouts, links, webhooks, customers). Each tool serves a clear purpose within its resource.

Completeness3/5

Core payment flows are covered, including payment intents, sources, payments, refunds, and webhooks. However, there are notable gaps: no get_payment, no update/delete for customers, and payment intents lack attach/confirm operations, requiring workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo issues