Connector API MCP Server Integration
The Connector API, provided by Apideck as part of its Unified API platform, serves as a critical metadata and discovery layer for enterprise software integration. It does not handle transactional data or CRUD operations for business records itself; instead, it exposes a comprehensive catalog of the available API connectors within the Apideck ecosystem and their technical specifications. Developers can use it to programmatically discover which third-party services (like Salesforce, HubSpot, or QuickBooks) are supported, retrieve detailed schemas for the data resources each service exposes (such as contacts, invoices, or tickets), and understand the level of API coverage for each resource—meaning which standard operations (like read, create, update) are implemented and stable. The primary use case is for platform engineers, integration developers, and product teams who need to dynamically build or configure integration workflows, generate documentation, or validate which connected services meet their application’s requirements before initiating data flows.
Technical Integration & Multi-Client Support
The Connector API MCP Integration translates REST paths, operational endpoints, and tool schemas into standardized Model Context Protocol JSON-RPC 2.0 messages. This allows AI assistants like Claude Desktop, Cursor IDE, VS Code (Cline/Roo Code), and Zed Editor to run tool queries and execute functions seamlessly.
Add stdio configuration block to claude_desktop_config.json.
Configure workspace root at .cursor/mcp.json or Settings -> MCP.
Insert server JSON payload into cline_mcp_settings.json.
Specification & Compatibility Table
| Property | Specification Detail |
|---|---|
| Target Integration | Connector API (apideck-com-connector) |
| Directory Category | finance payments |
| Protocol Spec | JSON-RPC 2.0 (stdio) |
| Canonical Path | /mcp/apideck-com-connector/ |
Frequently Asked Questions
How do I access the full JSON configuration for Connector API?
Click 'Open Full Connector API MCP Config' above to view the complete parameter schema, environment variable setup, and copy-pasteable JSON configs for Claude Desktop, Cursor, and VS Code.
Does Connector API require authentication secrets?
Authentication depends on upstream API requirements. Check the environment variable table on the detail page to view required API keys and header tokens.
Related Integrations
Stripe MCP
Process payments, manage subscriptions, and handle billing. Let your AI agent interact with Stripe seamlessly.
Stripe API MCP
The Stripe API is a comprehensive, RESTful interface provided by Stripe, Inc. that enables developers to programmatically manage all aspects of an online payment ecosystem. Core capabilities span the entire transaction lifecycle, including accepting payments, managing subscriptions, handling disputes, processing payouts, and orchestrating complex multi-party financial workflows. The provided endpoints specifically target the Connect product, which allows platforms and marketplaces to manage connected accounts (sellers, service providers, or sub-merchants), their associated bank accounts, and account onboarding via account links. Typical enterprise use cases include building global marketplaces, gig economy platforms, SaaS with revenue sharing, and any system requiring automated, multi-stakeholder financial operations. Consumer applications might involve freelancer tools or peer-to-peer payment interfaces that leverage these account management functions.
1Forge Finance APIs MCP
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.
Adyen Account API MCP
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.
Browse by Category
Explore MCP server integrations organized by platform and use case.