Finix MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FINIX_PASSWORD | Yes | Your Finix password | |
| FINIX_USERNAME | Yes | Your Finix username | |
| FINIX_ENVIRONMENT | No | The Finix environment to use. Options: 'Sandbox' (default) - Uses https://finix.sandbox-payments-api.com, 'Live' or 'Production' - Uses https://finix.live-payments-api.com | Sandbox |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_finix_docsB | This tool searches the Finix documentation for relevant information. It takes the following arguments:
|
| create_buyerC | This tool creates a new Buyer Identity in Finix. It takes the following arguments:
|
| create_sellerB | This tool creates a new Seller Identity in Finix with full underwriting data. Required arguments:
Optional arguments include extensive business and underwriting data fields. See the schema for complete field descriptions. |
| list_buyersB | This tool will fetch a list of Buyers from Finix. It takes two arguments:
|
| list_sellersB | This tool will fetch a list of Sellers from Finix. It takes two arguments:
|
| create_payment_linkC | This tool will create a payment link in Finix. It takes three arguments:
|
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover separate operations: creating buyers/sellers, listing buyers/sellers, creating payment links, and searching documentation. There is no overlap in functionality that could cause misselection.
All tool names follow a consistent verb_noun pattern (e.g., create_buyer, list_sellers, search_finix_docs). The naming is uniform across all tools, using snake_case and clear action-object pairs without any deviations.
With 6 tools, the count is well-scoped for a Finix server covering identity management and documentation. Each tool earns its place by addressing core operations like CRUD for buyers/sellers and payment links, without being too sparse or bloated.
The tool set provides good coverage for identity management (create and list for buyers/sellers) and payment links, with a useful documentation search tool. A minor gap exists in lacking update or delete operations for buyers/sellers, but agents can work around this for basic workflows.