datamcp

Hosted Model Context Protocol gateway for PostgreSQL, MySQL, and OpenAPI/Swagger, plus a hosted MCP memory server for structured shared Agent Memory.

datamcp turns a PostgreSQL 12+ database, MySQL database, OpenAPI 3.x API, or Agent Memory project into a managed remote HTTPS Model Context Protocol endpoint for AI clients. It hosts the transport and memory layer, authenticates MCP clients separately, and applies source permissions and project scope per MCP link.

• Website: datamcp.app
• Dashboard: dashboard.datamcp.app
• Documentation: datamcp.app/docs
• Pricing: datamcp.app/pricing
• Agent Memory: datamcp.app/mcp-memory-server
• Machine-readable product summary: datamcp.app/llms.txt
• Security model: SECURITY.md
• Cline installation instructions: llms-install.md

When to use datamcp

Use datamcp when Cursor, Claude, ChatGPT, VS Code, or another compatible remote MCP client needs controlled access to:

• a PostgreSQL or MySQL database without storing the database connection string in the AI client's configuration;
• a REST API described by OpenAPI 3.x, Swagger UI, or Redoc without generating and deploying a separate MCP server;
• shared, project-scoped memory that compatible AI clients can search, append to, compact, and use for handoffs;
• separate MCP links for different clients or users, each with its own authentication and source permissions.

datamcp hosts the MCP transport and control layer. It is not a marketplace for proxying arbitrary third-party MCP servers.

Supported sources

Source	Current support
PostgreSQL	PostgreSQL 12+ through standard PostgreSQL credentials, including providers such as Supabase, Neon, AWS RDS, and Google Cloud SQL
MySQL	MySQL through a mysql:// URL or structured connection fields, with schema discovery and single-statement SQL execution
OpenAPI	OpenAPI 3.x JSON or YAML specifications and supported Swagger UI or Redoc documentation pages
Agent Memory	Hosted, project-scoped memory with structured append-only entries, filtered full-text search, canonical Rules and Project Summary, and compact handoffs

MariaDB and other database engines are not currently supported.

PostgreSQL MCP

PostgreSQL connections expose schema and query tools through a hosted MCP endpoint.

• Read Only permits SELECT.
• Read, Write & Delete permits SELECT, INSERT, UPDATE, and DELETE, but not DDL.
• Full Access permits operations allowed by the effective database credentials.
• Custom permissions can restrict operations by table.
• PostgreSQL query activity and permission denials are available for review.
• Connection credentials are encrypted at rest with AES-256-GCM.

Product overview: PostgreSQL MCP server

MySQL MCP

MySQL connections expose schema context and single-statement SQL execution through a hosted MCP endpoint.

• Schema discovery covers tables and views, columns, primary keys, foreign keys, and indexes.
• MCP link policy narrows allowed operations and remains bounded by the effective MySQL grants.
• MySQL query execution and denied operations use the database activity path.
• MySQL credentials remain server-side rather than being copied into each AI client.

Product overview: MySQL MCP server

Practical MySQL resources:

• MySQL AI access security kit — a downloadable SQL template for a host-scoped account, TLS, explicit table grants, effective-account checks, denial tests, and emergency revocation.
• Connect MySQL to Cursor with MCP — restricted-user setup, MCP configuration, and allowed/denied verification.
• MySQL MCP server comparison — local, self-hosted, multi-engine, and hosted deployment options with ownership disclosure.

OpenAPI and Swagger MCP

OpenAPI connections expose four schema-aware MCP tools:

• list_api_endpoints
• get_endpoint_details
• get_api_schema
• call_endpoint

Upstream API authentication can use an API key, a pre-issued Bearer token, HTTP Basic authentication, or custom headers. Credentials remain on the datamcp connection and are injected into approved upstream calls.

Read Only links permit GET and HEAD while blocking POST, PUT, PATCH, and DELETE. Individual operations can also be hidden from discovery and execution.

OpenAPI endpoint calls do not currently appear in the datamcp activity log. Use upstream API or infrastructure logs for those calls.

Product overview: OpenAPI to MCP

Agent Memory MCP

Agent Memory provides a hosted shared project record for compatible AI clients such as Cursor, Claude, Codex, ChatGPT, and VS Code.

• One memory source can contain separate projects for repositories, products, clients, or workstreams.
• MCP links can be scoped to one project.
• Read Only supports canonical reads, search, entry retrieval, and handoffs.
• Read & Append adds session registration, structured entries, compaction, and canonical change proposals.
• Full Access can apply canonical Rules or Project Summary changes directly for an owner/admin API key user.
• Work-log entries are append-only. Compaction can archive entries from default results without deleting them.
• Search uses PostgreSQL full-text search and filters, not vector embeddings or semantic recall.
• The AI client must explicitly call memory tools; datamcp does not automatically write after every task.

Product overview: Hosted MCP Memory Server

Authentication and permissions

Two separate security boundaries are involved:

1. The MCP client authenticates to datamcp with an API key or OAuth 2.0 with PKCE.
2. datamcp uses the connection credential to access PostgreSQL, MySQL, or an upstream REST API. Agent Memory uses hosted project storage instead of an external source credential.

Authentication identifies the MCP client. The MCP link then narrows the operations available to that client. Backend database grants or upstream API authorization remain an independent boundary.

Gateway overview: MCP gateway

Compatible clients

Remote MCP endpoints can be configured in clients that support the required remote MCP transport and authentication flow, including:

• Cursor
• Claude
• ChatGPT
• VS Code

Setup guides: Cursor, Claude, ChatGPT, and VS Code.

Plans

Plan	Price	Source connections	MCP links	Members	Activity retention
Free	$0	1	1	2	7 days
Pro	$19/month	3	5	5	30 days
Enterprise	$49/month	15	50	25	365 days

See the pricing page for the current public plan details.

Current limitations

datamcp does not currently offer:

• MariaDB and database engines other than PostgreSQL and MySQL;
• a self-hosted or on-premise edition;
• SSO or SAML;
• upstream OAuth authorization flows or automatic upstream token refresh;
• activity logging for OpenAPI endpoint calls;
• published SOC 2, HIPAA, or ISO 27001 certification claims;
• a published uptime SLA.

Canonical metadata

• Brand spelling: datamcp
• Category: hosted Model Context Protocol gateway
• Supported source types: PostgreSQL 12+, MySQL, OpenAPI 3.x and Swagger APIs, and Agent Memory
• Website: https://datamcp.app
• Base MCP transport endpoint for registry metadata: https://api.datamcp.app/api/mcp (not a client-ready MCP link; configure AI clients with the generated per-link URL from the dashboard)
• Official MCP Registry package: io.github.mironovisa/datamcp
• Cline Marketplace icon: assets/datamcp-cline.png (400×400 PNG)

Public product claims are reviewed against the current application behavior before publication.

Registry and ecosystem profiles

These profiles refer to the same hosted datamcp service and canonical io.github.mironovisa/datamcp Registry identity:

• Official MCP Registry — canonical package metadata;
• Smithery — verified server profile;
• Glama — hosted connector profile;
• MCPServers.org — documentation profile;
• MCP Server Hub — curated directory listing.

The official Cline MCP Marketplace submission is under review.

Contact and contributions

• Email: hello@datamcp.app
• Bug reports and feature requests: GitHub Issues
• Contribution guide: CONTRIBUTING.md