Datpaq MCP server
{
"mcpServers": {
"datpaq": {
"type": "http",
"url": "https://mcp.datpaq.com/mcp"
}
}
}{
"mcpServers": {
"datpaq": {
"type": "http",
"url": "https://mcp.datpaq.com/mcp"
}
}
}{
"mcpServers": {
"datpaq": {
"type": "http",
"url": "https://mcp.datpaq.com/mcp"
}
}
}{
"servers": {
"datpaq": {
"type": "http",
"url": "https://mcp.datpaq.com/mcp"
}
}
}{
"mcpServers": {
"datpaq": {
"type": "http",
"url": "https://mcp.datpaq.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
An MCP server that exposes 34 Datpaq API endpoints as tools over HTTP. It serves any MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, agent frameworks) and supports both modern stateless protocol (2026-07-28) and legacy handshake-based versions (2025-11-25 and earlier).
- Call Datpaq API endpoints from Claude Desktop or other MCP clients without writing custom integrations.
- Build agent workflows that interact with Datpaq services using standard MCP tool calling.
- Self-host the server on your own infrastructure or use the public hosted endpoint at mcp.datpaq.com with per-request API key authentication.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.