Connect this site via MCP

Connect AI tools to this published documentation with the Model Context Protocol.

Connect supported AI tools to live Verifone documentation.

MCP server URL

https://docs.verifone.com/~gitbook/mcp/auth

This site requires authentication. Sign in with your Verifone account when prompted.

Quick start

1

Choose your client

Add https://docs.verifone.com/~gitbook/mcp/auth using the instructions for your client.

2

Authorize access

Complete the browser sign-in flow with your Verifone account.

3

Verify the connection

Ask the client a specific documentation question and request a citation.

Before you begin

You need:

• An MCP-compatible client, such as Claude or VS Code.
• Remote MCP and OAuth support in that client.
• A Verifone account with documentation access.

The server uses published documentation. Republish changes before expecting AI tools to use them.

Authenticate

The first connection opens a browser sign-in flow. Complete it with your Verifone account. Your client stores the authorization for future requests.

If sign-in fails, open https://docs.verifone.com in a browser first. Complete required SSO or multi-factor authentication. Then reconnect the MCP server.

Do not add GitBook API tokens or passwords. Use the browser authorization flow.

Set up your client

Choose the client you use. Each configuration uses the same MCP server URL.

Claude

1. Open Settings → Connectors.
2. Select Add custom connector.
3. Name it verifone-docs.
4. Enter https://docs.verifone.com/~gitbook/mcp/auth.
5. Complete the browser authorization flow.

Start a new chat after Claude connects the server. Enable the connector if Claude asks you to select available tools.

Claude Code

Add the remote server from your terminal:

claude mcp add --transport http verifone-docs https://docs.verifone.com/~gitbook/mcp/auth

Start Claude Code and approve the browser authorization flow. The server becomes available under the verifone-docs name.

VS Code

Create or update .vscode/mcp.json in your workspace:

{
  "servers": {
    "verifone-docs": {
      "type": "http",
      "url": "https://docs.verifone.com/~gitbook/mcp/auth"
    }
  }
}

Open the MCP Servers view and start verifone-docs. Complete authentication when VS Code opens the authorization prompt.

Cursor

Open Settings → Tools & MCP. Add a new MCP server named verifone-docs. Use https://docs.verifone.com/~gitbook/mcp/auth as the server URL. Then complete authorization.

Other clients

Add a remote HTTP MCP server with these values:

• Name: verifone-docs
• Server URL: https://docs.verifone.com/~gitbook/mcp/auth
• Transport: Streamable HTTP, if the client asks

The client must support browser-based OAuth authorization. Clients without remote MCP or OAuth support cannot connect to this authenticated site.

Verify the connection

Start a new chat after the server connects. Ask a precise question.

Example prompt

Tell me Verifone's latest VAOS release and provide me a link to the latest VAOS SDK.

The client should use connected documentation as context. Ask for a citation to validate the result.

Use the documentation effectively

Give the AI a focused task and name the product area. This improves retrieval quality.

• “Find the authentication flow and summarize required headers.”
• “Compare deployment options documented on this site.”
• “List the steps for upgrading to the latest version.”

Ask follow-up questions in the same conversation. The AI can retrieve more relevant pages as the task becomes specific.

Troubleshooting

The client cannot connect

Check the URL is exactly https://docs.verifone.com/~gitbook/mcp/auth. Open the documentation site first. Confirm your Verifone account can access the required pages.

Authentication does not complete

Allow pop-ups for the client or browser. Complete SSO and multi-factor authentication. Remove and add the server again if the client saved expired authorization.

The client does not show documentation results

Confirm the MCP server is enabled for the current chat. Start a new chat, then ask a specific question that matches published content.

The client requests authentication

Follow the browser authorization flow. Sign in with an account that has the same documentation access you need in the browser.