# DATPAQ

Hosted MCP server providing single-endpoint access to Datpaq APIs over streamable HTTP. Works with MCP-ready assistants without local daemons.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: datpaq
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/datpaq/mcp
- Updated: 2026-10-12
- HTML: https://affpapa.org/en/nevibecode/mcp/datpaq

## What it does

Exposes Datpaq endpoints as Model Context Protocol tools over a single streamable HTTP address. It publishes only verified, active APIs from the platform catalog, filtering out commands that depend on local filesystem access or client-side configuration files.

You can point your assistant directly at `https://mcp.datpaq.com/` or run the standalone binary using Go 1.26.3+ or Docker. The server stays completely stateless and stores no credentials, meaning every incoming request must include your Datpaq API key in the `Authorization` header. Calls without a bearer token fail immediately.

## Requirements
- Needs: Docker
- Remote server: `https://mcp.datpaq.com/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http datpaq https://mcp.datpaq.com/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add datpaq --url https://mcp.datpaq.com/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "datpaq": {
            "url": "https://mcp.datpaq.com/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "datpaq": {
            "type": "http",
            "url": "https://mcp.datpaq.com/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http datpaq https://mcp.datpaq.com/mcp
```

## When to use it
- route calls to Datpaq APIs through a single hosted HTTP address
- run Datpaq platform tools without configuring local command-line binaries
- self-host an MCP gateway in private infrastructure using Go or Docker
- block shell-dependent and local-state operations from model context

## Example prompts
- Check available Datpaq API tools via the connected HTTP endpoint.
- Call the Datpaq service using the bearer token configured in the environment.
- List the active endpoints currently exposed by the Datpaq MCP server.

## Similar
- [MCP Toolbox for Databases](https://affpapa.org/en/nevibecode/mcp/googleapis-mcp-toolbox-for-databases.md) — MCP server · ★ 16730
- [PostHog MCP Server](https://affpapa.org/en/nevibecode/mcp/posthog-mcp-server.md) — MCP server · ★ 40459
- [OpenWork MCP Gateway](https://affpapa.org/en/nevibecode/mcp/openwork-mcp-gateway.md) — MCP server · ★ 24271
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18779
- [Nhost](https://affpapa.org/en/nevibecode/mcp/nhost.md) — MCP server · ★ 9369
- [basebalance.cloud — x402 RPC & MCP gateway](https://affpapa.org/en/nevibecode/mcp/basebalancecloud-x402-rpc-mcp-gateway.md) — MCP server · ★ 7548

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md