Skip to content

MCP Server Overview

The Model Context Protocol is an open standard that lets AI assistants — Claude, Cursor, Continue, and others — connect to external systems through a common interface. An MCP server exposes a set of typed tools that the assistant can invoke on the user’s behalf.

Adva’s MCP server turns data onboarding into a conversation. Instead of mapping columns in a spreadsheet, a user can paste a CSV export into Claude and say:

“Import these customers into Adva. Use airtable as the source so I can re-sync later.”

The assistant calls Adva tools to pick a schema, suggest column mappings, validate records, and submit them — with all the same guardrails as the CSV and API import paths.

ClientTransportAuth modes
Claude DesktopStreamable HTTPOAuth, API key
CursorStreamable HTTPOAuth, API key
Claude CodeStreamable HTTPOAuth, API key
MCP InspectorStreamable HTTPOAuth, API key
ContinueStreamable HTTPAPI key

Any MCP client that speaks the Streamable HTTP transport can connect.

EnvironmentMCP endpoint
Productionhttps://mcp.getadva.ai/mcp
Staginghttps://mcp-staging.getadva.ai/mcp

Use Production for real work. Use Staging for development, testing, and demos — it points at a separate Adva environment and never touches production data.