-
Notifications
You must be signed in to change notification settings - Fork 9
Documentation MCP Server
The Visa Documentation MCP Server provides AI agents with integration guides, code examples, and tool definitions for the Visa Developer Platform, covering both VDP and Visa Intelligent Commerce (VIC) integrations.
Endpoint:
https://sandbox.mcp.visa.com/mcp/doc
get-docs
Returns structured documentation for Visa Developer Platform integrations, including:
- Authentication patterns (X-Pay Token, Two-Way SSL / Mutual TLS, MCP tokens)
- Message Level Encryption (MLE/JWE) implementation
- Credential management and environment configuration (Sandbox, Certification, Production)
- Workflow and code examples for MCP and direct API flows
- Tool definitions for VIC MCP server
- Payload schemas for VIC APIs and related services
- Best practices for AI-driven implementations across MCP and REST APIs
- Building or debugging integrations with Visa APIs
- Setting up authentication (X-Pay Token, Two-Way SSL / Mutual TLS)
- Working with Message Level Encryption (MLE/JWE)
- Managing credentials and environment configuration (Sandbox, Certification, Production)
- Integrating VIC agent commerce workflows (card enrollment, purchase instructions, payment credentials)
- Generating MCP client or direct API client code
- Referencing VDP, VIC, X-Pay Token, or Visa MLE
A short 3-minute walkthrough showing:
- Connecting an AI agent to the Documentation MCP Server
- Generating an MCP client
- Authenticating and retrieving tools
- Example tool usage (enroll-card)
mcp-vic-doc-tool-demo.mp4
The Documentation MCP Server is also available through the Gemini CLI Extension, allowing you to access Visa documentation directly inside the Gemini terminal workflow.
1. Install the extension
gemini extensions install https://github.com/visa/ai2. Activate
Restart the Gemini CLI — the extension will auto-load and expose the documentation tool.
You can then query Visa documentation directly from Gemini using natural language.
- Add the Documentation MCP Server (or Gemini extension) to your AI workflow
- Agent uses get-docs to fetch integration guidance
- Agent generates MCP client code + authentication + tool calls
- Developer validates the resulting integration