Let AI work with the database you already use.
Discover schema and query tools without building a custom MCP server. Backend credentials stay out of the AI client.
Hosted Model Context Protocol for real systems
datamcp connects PostgreSQL, MySQL, OpenAPI, and shared agent context to the AI tools you already use. Keep backend credentials server-side, set access per link, and start in minutes.
1 source + 1 hosted MCP link. $0 forever.
One remote HTTPS endpoint between your systems and AI clients.
Transport and authentication support varies by platform. Use a client compatible with the datamcp remote MCP flow.
Everything inside datamcp
Start with the job you need to finish. Connect a live database, publish an API, keep PostgreSQL private, share project memory, or control several AI clients from one hosted gateway.
Discover schema and query tools without building a custom MCP server. Backend credentials stay out of the AI client.
Import OpenAPI 3.x or Swagger documentation, expose discovery, and allow only the HTTP methods one link needs.
Run the Local Agent on EC2, a VPS, or Docker. The PostgreSQL password stays on that machine; SQL and results pass through datamcp cloud.
Save deliberate decisions, progress, risks, and handoffs in an append-only record that compatible clients can search later.
Create remote HTTPS links for specific tools, environments, and people. Database activity and permission denials stay reviewable.
Local Agent Tunnel / shipped
Create a Local Agent source, then run @datamcp/agent on EC2, a VPS, or Docker beside PostgreSQL. The agent connects outbound, so you do not expose the database to inbound internet traffic.
The PostgreSQL password stays on the agent machine. SQL requests and query results still pass through datamcp cloud. Local Agent supports PostgreSQL only and uses the normal source and MCP-link slots in your plan.
Built-in playground
Test a PostgreSQL or MySQL connection inside datamcp before adding it to an external MCP client. Inspect the schema tools, query result, and permission outcome in one place.
get_schema · customers, ordersALLOWED · 126msquery · SELECT ... LIMIT 3ALLOWED · 94msDatabase or API to MCP link
datamcp handles source discovery or memory storage, hosting, MCP transport, and access policy. For private PostgreSQL, the Local Agent connects outbound while the AI tool still gets one hosted URL.
Read the setup guideConnect PostgreSQL, MySQL, or Swagger/OpenAPI, create Agent Memory, or choose Local Agent for private PostgreSQL.
Choose read-only or write access. Database credentials and API tokens never reach the AI client.
Use the hosted endpoint in Cursor, Claude, ChatGPT, VS Code, or another client that supports the required remote MCP flow.
Security is the product
Direct database credentials are encrypted at rest, supported API credentials stay server-side, and database queries or API methods are checked against the MCP link policy before execution. With Local Agent, the PostgreSQL password remains on the agent machine.
Pricing
Free includes one source and one hosted MCP link forever. Upgrade when you need more sources, links, retention, chat, or team capacity.
For one source and one MCP link, forever.
Add one more source and MCP link beyond Free.
For developers shipping with AI.
For teams that need oversight.
From the field
A practical PostgreSQL row-level security setup for AI agents: non-owner roles, FORCE RLS, explicit SELECT, INSERT, and UPDATE policies, plus denial tests.
Agent MemoryGive Codex persistent shared project context through an MCP memory server. Compare Codex Memories, AGENTS.md, chat history, and cross-agent handoffs.
Agent MemoryCompare Cursor Memories, Rules, Memory Bank files, chat history, and an MCP memory server for persistent context shared with Claude Code and Codex.
Your database or API. One link. Their next build.