Visa Developer MCP
Follow this step-by-step guide to connect to the Visa Developer Model Context Protocol (MCP) server.
Overview
Connect your AI agents to the Visa Developer MCP server to enable automatic discovery of Visa integration scenarios, documentation, API reference/schemas and code generation. Model Context Protocol (MCP) enables your agent to discover available Visa tools and provides direct access to the developer ecosystem.
Visa Developer tools and capabilities
The Visa Developer MCP Server provides a centralized, AI-native, read-only interface to Visa Developer documentation, schemas, and integration knowledge. It enables developers and AI agents to discover, design, and generate integrations faster.
MCP server capabilities
- Read-only access to public documentation and reference data
- Product and API discovery across the Visa Developer platform
- OpenAPI-derived schemas for integration development
- Use Cases and Sample Code for development guidance
- Semantic search across Visa Developer content
Before you begin
To get started with the Visa Developer MCP, you need:
- A compatible AI development tool (choose one - supported AI development tools may vary and expand over time):
- VS Code
- Cursor
- Claude Code
- Cline
- OpenAI Codex
- Other
- A basic understanding of the MCP standard
- A Visa Developer account (optional for enhanced capabilities)
Allow a few minutes for initial setup. You can start using the Visa Developer MCP immediately with any MCP‑compatible AI tool - the Visa Developer account unlocks additional capabilities when needed.
Authentication model
Understanding how authentication works will help you set up your connection.
- Session-based authentication: OAuth 2.1 authentication triggers automatically when you access functionality that requires it
- Automatic tool discovery: After successful authentication, available tools are discovered automatically
- Automatic token management: Token refresh happens automatically in the background
- Supported clients: VS Code, Cursor, Claude Code, Cline, and others
When authentication is required:
- Your browser opens for login
- Log in with your Visa Developer credentials
- Browser redirects back to your development tool
- Authorized tools become available - authentication handles access automatically
- Authentication tokens are managed automatically in the background
Authentication details
Visa Developer MCP uses OAuth‑based authentication for secure access. Authentication is largely automatic, with minimal user action beyond login and authorization.
Post-authentication behavior
Once authentication succeeds:
- Tools become available in your MCP host environment
- No additional configuration required - all setup is automatic
- Available tools are discovered automatically based on your Visa Developer account access.
- No per‑tool authentication or individual permission prompts occur
- Automatic token refresh handles session management transparently
Token management
The system manages authentication tokens automatically:
- Tokens refresh automatically in the background
- No manual token management required
- Session-based authentication is automatically managed by your development tool
Managing MCP access
You can manage your MCP server access through the Visa Developer Portal or by disconnecting from your development tool.
Revoking or disabling access
To temporarily disconnect:
- Remove the Visa Developer MCP server configuration from your AI development tool
- Restart your development tool to clear the active connection
Tokens will expire automatically based on session timeouts
Access tools
Your available tools depend on your Visa Developer account permissions. The system automatically determines your permissions during authentication, and tools become available based on your granted permissions.
Configure your tool
Choose the configuration that matches your AI development tool. All configurations connect to the same Visa Developer MCP server and rely on automatic tool discovery and OAuth handling when authentication is required.
VS Code with MCP extensions
VS Code MCP extensions register remote MCP servers using extension settings that follow the standard MCP server mapping pattern. Add the following configuration to your MCP extension settings and restart VS Code.
{
"servers": {
"visa-developer": {
"type": "http",
"url": "https://developer.visa.com/mcp"
}
}
}
Cursor
Cursor uses its built-in MCP support to connect to remote MCP servers. Add the following configuration to your Cursor settings and restart the application.
{
"mcpServers": {
"visa-developer": {
"url": "https://developer.visa.com/mcp"
}
}
}
Claude Code
Claude Code integrates directly with MCP servers through its native MCP protocol support. Add the following server configuration to your Claude Code MCP settings.
{
"mcpServers": {
"visa-developer": {
"type": "http",
"url": "https://developer.visa.com/mcp"
}
}
}
Cline
Cline connects to MCP servers using streamable HTTP transport for real-time communication. Add the following configuration to your Cline MCP server settings.
{
"mcpServers": {
"visa-developer": {
"type": "streamableHttp",
"url": "https://developer.visa.com/mcp"
}
}
}
OpenAI Codex
OpenAI Codex can connect to MCP servers using standard MCP protocol configuration. Add the following server configuration to your OpenAI Codex MCP settings.
{
"mcpServers": {
"visa-developer": {
"type": "http",
"url": "https://developer.visa.com/mcp"
}
}
}
Other
MCP is an open protocol, and any MCP client following the MCP protocol should be able to connect to the Visa Developer MCP server. Refer to your MCP client/IDE documentation for additional information. Use the server url https://developer.visa.com/mcp and "OAuth" as the connection mechanism if possible.
{
"mcpServers": {
"visa-developer": {
"url": "https://developer.visa.com/mcp"
}
}
}
Verify your connection
Test your setup to ensure everything is working:
- Restart your development tool after adding the configuration
- Look for Visa Developer MCP server connection confirmation in your tool's output/logs
Tool |
How to check |
VS Code |
Run MCP: List Servers, select visa-developer, and review its status or output |
Cursor |
Open MCP settings and confirm that visa-developer is enabled and its tools are listed |
Claude Code |
Run claude mcp list, claude mcp get visa-developer, or claude /mcp |
Cline |
Open MCP Servers and confirm that visa-developer is enabled and exposes tools |
OpenAI Codex |
Run codex mcp list and confirm that visa-developer appears |
Your connection is working if you see:
"Visa Developer MCP server connected successfully" (or similar message)
Available tools discovered automatically
No authentication errors in your development tool logs
Run your first query
Test your Visa Developer MCP setup with this simple query:
Ask your AI agent: "What Visa APIs are available for payment processing?"
- Submit the query to your AI agent
- Review the response for expected content
Your agent should:
- Automatically use available Visa developer tools to access platform information
- Provide a comprehensive API catalog including Visa Direct, Visa Checkout, CyberSource, and Transaction Controls
- Include descriptions and use cases for each API
- ✅ Agent responds with specific Visa product information
- ✅ Response includes multiple Visa APIs with descriptions
- ✅ No authentication or connection errors
- ✅ Information appears current and comprehensive
Best practices
These optional recommendations help you use Visa Developer MCP effectively:
- Use natural language queries to discover relevant information
- Authentication is handled automatically when required
- Keep credentials secure in environment variables
- Allow your agent to discover tools automatically
- Start with general queries to explore available documentation
Common issues
Troubleshooting guide for common problems with the Visa Developer MCP connection.
Problem: Connection failed
Symptoms: Tool shows "Visa Developer MCP server connection failed" or similar error.
Solutions:
- Verify the server URL is correct: `[DEVELOPER_MCP_SERVER_URL]`
- Check your internet connection
- Restart your development tool and try again
- For authenticated access: verify credentials are correct
Problem: Authentication errors
Symptoms: "Authentication failed" or OAuth-related error messages
Solutions:
- Ensure your development tool supports OAuth authentication
- Restart your development tool to refresh the authentication flow
- Check that your browser-based login completed successfully
Problem: No tools discovered
Symptoms: Agent connects but shows 0 available tools
Solutions:
- Restart your development tool completely
- Check your IDE logs for specific error messages
- Ensure your development tool supports MCP protocol
Problem: Agent can't access documentation
Symptoms: Agent responds with "I don't have access to that information"
Solutions:
- Verify Visa Developer tools appear in your agent's tool list
- Try a different query format such as "What Visa products are available?" or "Show me Visa Direct documentation"
- Check if you need authenticated access for specific content
- Ensure your agent is configured to use available MCP tools
Reference
Additional information and resources for the Visa Developer MCP server
What's included vs not included
Included access:
- Read‑only access to public documentation and reference data
- Product and API discovery
- OpenAPI‑derived schemas
- Use cases and sample code (availability may vary in MVP and expand over time)
- Semantic search across Visa Developer content
Not included:
- Runtime API invocation
- Customer or merchant data
Additional examples
Example 1: Get specific documentation
Agent Query: "Show me the schema for Visa Direct API requests"
Visa Developer MCP Response: Uses available tools to provide detailed request/response formats, required fields, and data validation rules for Visa Direct push payment transactions.
Example 2: Search documentation
Agent Query: "How do I implement fraud detection in my payment flow?"
Visa Developer MCP Response: Uses available search capabilities to find relevant fraud prevention documentation across all Visa products, including Risk Manager, Advanced Authorization, and Transaction Controls integration patterns.
Message level encryption
Visa Developer MCP server enforces read-only access and does not handle sensitive customer data. The server provides access to documentation and other developer resources only. Message Level Encryption is not required.
Help and support
For help and support using the Visa Developer MCP server, view the MCP documentation at `https://developer.visa.com/mcp`.