Codinfy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODINFY_API_KEY | Yes | Your Codinfy publishable API key (pk_live_xxx or pk_sandbox_xxx). Get one from https://hub.codinfy.com/settings/api-keys | |
| CODINFY_API_BASE | No | Base URL of the Codinfy API | https://api.codinfy.com |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_licenseC | Validate a Codinfy purchase code against the licensing API (HMAC + JWT). |
| check_license_statusA | Return the current status of a license (active | expired | suspended | cancelled) and its grace period. |
| list_user_licensesA | List all licenses owned by the current authenticated user. |
| create_checkoutA | Create a Codinfy Pay checkout session via GeniusPay direct API. Returns a pay.codinfy.com URL or a USSD push reference. |
| get_payment_statusA | Poll a payment status by reference (used by the wait screen on pay.codinfy.com). |
| list_geniuspay_operatorsA | List the active GeniusPay operators (per country) with their logos and payment methods. |
| list_productsA | List published marketplace products (cursor-paginated). |
| get_productC | Get a product by slug or id. |
| search_productsB | Full-text search across the marketplace catalog. |
| track_eventA | Track a public event on Codinfy's analytics pipeline (CRM funnel + product analytics). |
| get_design_tokensA | Return Codinfy's current design tokens (palette, typography, spacing) from Brand Manager. |
| get_brand_settingsA | Return public brand metadata (site name, logos, social links) — sourced from Brand Manager (R13). |
| get_brand_assetsA | Return signed URLs for brand assets (logo light/dark/icon/og/pwa). |
| oauth_discovery_metadataA | Return the OpenID Connect discovery metadata (auth.codinfy.com/.well-known/openid-configuration). |
| oauth_jwksA | Return the JWKS used to verify ID tokens issued by Codinfy Identity. |
| list_ad_unitsA | List the Codinfy Ad Network ad units available for a publisher. |
| get_ads_configA | Return the public configuration of the Codinfy Ads SDK for the calling site. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
All 17 tools have clearly distinct purposes. Each targets a specific resource and action (e.g., license validation vs. status check, brand assets vs. settings). There is no overlap that would confuse an agent.
All tools use a consistent verb_noun snake_case pattern (e.g., create_checkout, get_product, list_ad_units). Even OAuth tools follow this implicitly. No mixing of conventions.
17 tools cover multiple subdomains (licensing, payments, ads, branding, marketplace, auth, analytics). While slightly above the typical 15-tool threshold, each tool serves a distinct need and the count is justified for the platform's breadth.
The tool surface covers key read operations and essential writes (checkout creation, event tracking) across all subdomains. Minor gaps exist (e.g., no product creation or license revocation), but for a client-facing API these are acceptable and do not hinder common workflows.