Stripe API MCP Configuration
The Stripe API MCP configuration provides a hosted JSON schema that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Stripe API API via the Model Context Protocol. This configuration maps 10 API endpoints as callable tools, including GetAccount, PostAccountLinks, GetAccounts, and more. No authentication credentials are needed — it works out of the box. The configuration is auto-generated from the Stripe API OpenAPI specification (v2022-11-15) and has a quality score of 34/99 (fair documentation coverage). Use the hosted URL below to auto-load this schema into any compatible MCP client.
Quick Specs Reference
Hosted Config URL
Use this hosted URL in any client that supports remote MCP schema auto-loading.
https://mcpbridge.org/config/stripe-com.jsonOne-Click Client Setup
Copy the configurations below to wire your local coding assistant directly.
Claude Desktop
claude_desktop_config.json{
"mcpServers": {
"stripe-com": {
"command": "npx",
"args": [
"-y",
"@mcp/stripe-com"
],
"env": {
"STRIPE_API_API_KEY": "your_stripe_api_api_key"
}
}
}
}Cursor & VS Code
MCP Server URL Setup{
"mcpServers": {
"stripe-com": {
"url": "https://mcpbridge.org/config/stripe-com.json"
}
}
}Raw Configuration JSON
For local command line wrappers or dynamic shell bindings.
{
"mcpServers": {
"stripe-com": {
"command": "npx",
"args": ["-y","@mcp/stripe-com"],
"env": {
"STRIPE_API_API_KEY": "your_stripe_api_api_key"
}
}
}
}Required Environment Keys
Substitute these secrets inside your configuration directory environment definitions.
STRIPE_API_API_KEYyour_stripe_api_api_key with your secret key credentialMapped Web APIs & Tools
The following routes will be exposed directly as protocol tools for the LLM.
/v1/accountGetAccount
/v1/account_linksPostAccountLinks
/v1/accountsGetAccounts
/v1/accountsPostAccounts
/v1/accounts/{account}GetAccountsAccount
/v1/accounts/{account}PostAccountsAccount
/v1/accounts/{account}DeleteAccountsAccount
/v1/accounts/{account}/bank_accountsPostAccountsAccountBankAccounts
/v1/accounts/{account}/bank_accounts/{id}GetAccountsAccountBankAccountsId
/v1/accounts/{account}/bank_accounts/{id}PostAccountsAccountBankAccountsId
Similar Configurations
Stripe API
Process payments, manage subscriptions, and handle billing. Let your AI agent interact with Stripe seamlessly.
https://mcpbridge.org/config/stripe.json1Forge Finance APIs
The 1Forge Finance API provides a robust, high-performance gateway to global financial market data, specializing in real-time and delayed equities and foreign exchange (Forex) quotes. As a foundational data service, it aggregates and delivers critical market information through its core endpoints: GET /quotes for retrieving current price data for specific symbols, and GET /symbols for accessing a comprehensive list of tradable assets. This API, offered by the financial data provider 1Forge, serves a vital function for developers building financial applications, trading platforms, portfolio trackers, and analytical tools. Typical use cases range from retail investors seeking live market snapshots for personal dashboards to enterprise fintech firms integrating up-to-the-moment pricing into risk management systems, algorithmic trading backtesting frameworks, or currency conversion engines for international payment services. Its value lies in providing a streamlined, dedicated source for the essential data points that underpin countless financial workflows. When exposed as tools to an AI coding assistant through the Model Context Protocol (MCP), the 1Forge API transforms from a static data source into a dynamic, queryable resource that can supercharge the development lifecycle. An AI agent, such as one operating within Claude Desktop, Cursor, or Cline, gains the ability to interact with live market context directly within the developer's workflow. This integration allows the assistant to perform just-in-time data fetches to inform its code suggestions, explanations, or generated logic. For instance, the AI could be instructed to check current exchange rates to calculate accurate invoice amounts in a multi-currency SaaS application it's helping to build, or to validate the price symbol format required for a trading bot by querying the /symbols endpoint for a list of valid Forex pairs. This bridges the gap between abstract coding assistance and concrete, data-driven implementation, enabling the AI to produce more accurate, context-aware, and functionally complete code snippets and architectures. Practical workflow examples demonstrate the powerful synergy between a developer and an AI-augmented MCP server. A developer could instruct the agent with a command like, "Use the 1Forge API to fetch the latest quotes for AAPL, MSFT, and GOOGL, then write a Python function that compares their daily price changes and returns the top performer." The AI would then execute the /quotes call, process the JSON response, and generate the requested function with the data structure pre-validated. In another scenario, a developer building a financial dashboard might say, "Query the /symbols endpoint to get a list of all available cryptocurrency pairs, then generate a TypeScript interface type that represents the structure of a single symbol object." The agent would retrieve the data, analyze its schema, and produce the corresponding TypeScript type definition, saving the developer manual parsing and modeling time. Furthermore, for automating repetitive analysis, a prompt like "Monitor the real-time quote for EUR/USD every minute and update a local JSON file with the timestamp and price" could lead the AI to suggest a complete script utilizing the API, incorporating scheduling and file I/O operations. While the 1Forge API currently operates without an authentication requirement, developers must still adhere to critical security and configuration best practices when setting up an MCP server instance. It is imperative to treat the API endpoint as a potential vector for data leakage or abuse if exposed carelessly. Implement the principle of least privilege by running the MCP server in a sandboxed environment or a container with restricted network access, allowing it to reach only the 1Forge endpoints. Never hardcode any future API keys or sensitive configuration directly into source code; instead, use environment variables or a secrets management system. Developers should also implement client-side rate limiting and request throttling within their applications to respect the API's service terms and prevent accidental denial-of-service scenarios. Input validation on both incoming developer prompts and outgoing API queries is crucial to prevent injection attacks or malformed requests. It is advisable to use the MCP server configuration to explicitly define and allowlist the specific API endpoints that the AI agent is permitted to access, further tightening control over the data flow.
https://mcpbridge.org/config/1forge-com.jsonAdyen Account API
The Account API is a foundational RESTful service provided by Adyen for the comprehensive management of account-related entities within a classic marketplace or platform integration. It serves as the primary programmatic interface for orchestrating the lifecycle of accounts, account holders, and their associated legal and financial components on the Adyen payments platform. Its core capabilities encompass the creation, retrieval, and deletion of critical data structures, including the accounts themselves, account holder profiles, bank accounts, legal arrangements, shareholder records, and signatory details. Typical use cases are prevalent in enterprise-grade platform operations: onboarding new merchants or sellers by creating account holders and linking their bank accounts for payouts, performing due diligence by managing legal and shareholder information, generating necessary financial documents via tax form retrieval, and finally, executing the secure closure of accounts or account holder relationships when required. This API is the engine behind programmatic account management for businesses that have already established their Adyen platform integration. When exposed as a set of tools through the Model Context Protocol (MCP) for integration with AI coding assistants like Claude Desktop, Cursor, or Cline, this API unlocks significant value by transforming repetitive, multi-step account management workflows into intuitive, natural language-driven tasks. An AI agent can directly interact with the API's endpoints to perform complex queries and updates, acting as a highly efficient co-pilot for platform developers and operations teams. Instead of manually composing HTTP requests or navigating a separate dashboard, a developer can instruct the AI to perform actions conversationally. For example, the AI can be tasked to "generate a summary of all account holders created in the last 7 days and their current status" by leveraging the getAccountHolder endpoint, or it can "draft the payload needed to add a new shareholder to account holder AH_123 for compliance review." This integration shifts the developer's focus from low-level API mechanics to higher-level business logic and decision-making, dramatically accelerating development, debugging, and administrative processes. In practice, a developer can instruct an AI assistant to execute a wide range of dynamic tasks using this MCP server. The AI agent can query records to audit account setups, such as "list all bank accounts linked to account holder ID 456 to verify payout destinations." It can automate compliance updates by crafting requests to "remove a dormant signatory from legal arrangement LA_789" using the deleteSignatories endpoint, or facilitate data cleanup by "deleting all test bank accounts under account ACC_TEST." The agent can also assist in lifecycle management by preparing and executing the calls needed to "close the account for a terminated merchant" or "generate a tax form for account holder AH_001 for the fiscal year." These workflows empower developers to handle bulk operations, validate data integrity, and respond to operational events through simple instructions, with the AI managing the precise API calls and data structures behind the scenes. While the basic specification notes "None" for authentication, this is a critical implementation detail that requires careful attention for production security. Developers must treat this API with the utmost care, as it handles sensitive financial and identity data. The foundational security principle is implementing robust authentication and authorization, typically via Adyen's API keys or OAuth, ensuring each request is properly signed and originates from a trusted source. Adherence to the principle of least privilege is paramount; the API credentials used should have only the permissions absolutely necessary for the task at hand, whether that is read-only access for reporting or specific write permissions for creating accounts. When configuring an MCP server for an AI assistant, credentials must be managed securely outside of the codebase, using environment variables or a secrets manager, never embedded in client-side code. Developers should also ensure that any tool exposed to an AI is wrapped in validation logic to prevent malformed or malicious payloads, and that all actions are logged for audit trails, given the irreversible nature of operations like account closure.
https://mcpbridge.org/config/adyen-com-accountservice.jsonAdyen BinLookup API
The Adyen BinLookup API is a critical financial data service provided by Adyen, a leading global payment platform, designed to enable merchants and payment service providers to enhance transaction decisioning and optimize payment acceptance rates. At its core, this API allows developers to submit a payment card's Bank Identification Number (BIN)—the first six to eight digits of a card number—to retrieve essential metadata that is pivotal for payment processing and risk assessment. The two primary endpoints, GET3DSAvailability and GETCostEstimate, serve distinct yet complementary purposes. The former checks for 3D Secure 2.x compatibility, determining whether an issuer supports this fraud-prevention protocol and which authentication version is applicable. The latter provides a real-time cost estimate for processing a transaction, factoring in the card's country, brand, and issuing bank to calculate interchange fees and scheme costs. Typical use cases are widespread in enterprise e-commerce and subscription billing platforms, where dynamically routing payments, pre-qualifying transactions for specific authentication methods, and providing upfront cost transparency to consumers can significantly reduce cart abandonment and optimize profitability. When exposed as toolsets through a Model Context Protocol (MCP) server for AI coding assistants like Claude Desktop or Cursor, the Adyen BinLookup API transforms from a static data endpoint into an intelligent, context-aware resource for development and operational tasks. The primary value lies in enabling the AI to programmatically and dynamically access live payment infrastructure data, removing the need for developers to manually look up BIN information or hard-code static card data. This allows an AI assistant to become an active participant in building and debugging payment flows. For instance, an AI can validate the integration of payment forms in real-time, cross-reference card details with Adyen's database to verify they are test or live BINs, and simulate how different card types would be processed before a transaction is ever submitted. It effectively bridges the gap between code and the complex, real-world rules of the payment ecosystem, fostering smarter, data-driven development workflows. Practical workflow examples illustrate how a developer can instruct an AI agent to perform sophisticated tasks using this MCP-connected API. A developer could command the AI to "Scan this new checkout form, extract all visible BIN prefixes, and use Adyen's tools to generate a report showing which ones support 3D Secure and their estimated processing cost." The AI would then query the endpoints and produce a detailed analysis. In a debugging scenario, one might instruct: "This EU-based user's transaction failed authentication; use the BIN 4000000000000000 to check 3D Secure availability and get a cost estimate for a card issued in Germany." The AI would execute the lookups, returning actionable data that points to whether the issue was an authentication problem or a routing miscalculation. Furthermore, for building dashboards or internal tools, a developer can direct the AI to "Create a script that uses the BIN lookup to fetch and cache cost estimates for the top 100 card BINs we encounter, updating the cache daily." This automates a previously manual data-aggregation task. Critical security and configuration guidelines are paramount when deploying this API, especially within an MCP context. Although the system prompt indicates "None" for authentication, the official Adyen documentation specifies that all calls require authentication via an API credential, typically using a merchant account-specific API key or a combination of a username and password, passed via HTTP Basic Authentication. Best practices must be strictly followed: first, adhere to the principle of least privilege by generating a dedicated API user with permissions restricted solely to the BinLookup service, avoiding use of a primary or high-privilege account key. Second, all communication must occur over TLS 1.2+ encryption. Third, the API key or credentials must be stored securely, never exposed in client-side code or public repositories, and injected into the environment of the MCP server or AI assistant runtime via secure secrets management. When configuring the MCP server, ensure it acts as a secure proxy, handling authentication internally and not exposing raw credentials to the AI model. Developers should also implement rate limiting and error handling in their integration to manage quota and gracefully handle API response variations.
https://mcpbridge.org/config/adyen-com-binlookupservice.json