Connect your AI tools

This page is for developers who want their own AI coding tool to look up VBAPI endpoints, parameters, and schemas while it writes code. It shows how to connect common MCP clients to the VBASoftware MCP server and how to check that the connection works.

What the MCP server will never do

Call the VBASoftware API, or read or change any record in your database.
Ask for, store, or forward your VBASoftware API key, password, or tokens.
See client data such as members, claims, or payments.

It only searches and returns the published documentation and the API description. If an MCP tool or your AI client asks you for VBASoftware credentials, do not enter them, and tell VBA support. See AI assistant and MCP server for what the AI features can and cannot see.

Server details

Setting	Value
Server URL	`https://vbapi-docs.vbasoftware.com/mcp`
Transport	Streamable HTTP (called `http` in most client configurations)
Sign-in	None. Do not add headers or an API key.
Server name	`VBASoftware MCP Server`

Use the Connect to MCP button

The quickest way to connect is the button below. It offers a one-click install for Cursor and VS Code, a Claude connector link, the Claude Code and Codex commands, and a copy of the server URL.

If the button does not suit your setup, use the steps for your client below.

Set up your client

Client settings change often. Each tab links to the client's own documentation; follow it if a menu name has moved.

Add the server to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "vbasoftware-mcp-server": {
      "url": "https://vbapi-docs.vbasoftware.com/mcp"
    }
  }
}

If the file already has an mcpServers object, add the vbasoftware-mcp-server entry to it. Then check that the server is turned on in Cursor's MCP settings and that its tools are listed.

Cursor documentation: Model Context Protocol (MCP).

Check the connection

Ask your AI tool:

Using the VBASoftware MCP server, which endpoint adds a claim to a claim batch? Give the method and path.

A working connection shows a call to one of the server's tools in the conversation, and the answer names POST /claim-batches/{batchNumber}/claims. If the answer appears without a tool call from the VBASoftware server, the client answered from its own training data: check that the server is turned on and ask again, naming the server.

Tools the server provides

All of these tools only read the published documentation and the API description.

Tool	What it does
`list-apis`	Lists the APIs documented on the portal.
`get-endpoints`	Lists every endpoint of an API, with its method, path, and summary.
`get-endpoint-info`	Returns one endpoint in full: parameters, request body, responses, and security.
`get-security-schemes`	Returns the API's security schemes, such as the API key and bearer token.
`get-full-api-description`	Returns the whole OpenAPI description. It is large, so prefer `get-endpoint-info`.
`search`	Searches the published pages for a word or phrase.

Some clients see two tools instead, describe-tools and execute. They run the same documentation lookups as one script in Redocly's sandbox, which saves round trips. They do not change what the server can see.

Troubleshooting

What you see	What to do
The server is listed, but its tools never run	Turn the tools on in the client's tool list. Visual Studio adds new MCP tools turned off.
The answer has no tool call from the VBASoftware server	Name the server in the prompt, for example "Using the VBASoftware MCP server".
Visual Studio asks you to trust the server again	Visual Studio asks again when a server's tools change. Check that the URL is still `https://vbapi-docs.vbasoftware.com/mcp` before you accept.

Next, try the prompt recipes in Build with AI.