MCP stands for Model Context Protocol. It's an open standard that lets AI assistants like Cursor and VS Code call external tools: not just talk about them, but actually use them.
AI assistants are great at generating text. But they can't run Python on your actual file, score data quality, or build a chart that proves the number. They can tell you how to do it, but they can't do it for you. getqueryly can.
MCP is like a USB port for AI. Instead of building custom integrations for every AI platform, you build one MCP server and every compatible AI assistant can use it.
Here's the flow:
Say you need to know what is driving revenue. With getqueryly's MCP server, you just say in Cursor or VS Code:
Analyze /tmp/sales.csv: what is my best product by revenue and show a bar chart
Your assistant calls getqueryly's ds_upload then ds_query, which runs Python on your actual file and returns the chart plus the numbers. You get the answer without leaving your chat.
Most MCP servers are simple wrappers. getqueryly has 20 tools covering the full data lifecycle:
And every tool uses the same Makes cost system as the web UI. No separate billing, no surprises.
Add this to your AI assistant config:
{
"mcpServers": {
"getqueryly": {
"url": "https://getqueryly.com/mcp/sse",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}
Get your API key at getqueryly.com: sign in, go to Settings - API Keys, generate one with a name and expiry, then copy once. Works with one header X-API-Key for both REST and MCP at https://getqueryly.com/mcp/sse.
MCP is becoming the standard for AI tool integration. Anthropic open-sourced it, and it's now managed by a neutral foundation alongside OpenAI's agent standard. This means it's going cross-lab, not staying locked to one company.
For developers, this means: build one MCP server, and every AI assistant can use your tools. For users, this means: your AI can actually do things, not just talk about them.
Try getqueryly