Hosted Model Context Protocol for real systems

Your database, API, or Agent Memory.One hosted MCP link.

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.

01No MCP server to manage02Credentials stay server-side03Works across compatible clients
Connect
Choose your sourceDirect or private tunnel
Compare source setup
Hosted MCP gateway

One remote HTTPS endpoint between your systems and AI clients.

AuthenticationPer-link accessRevocationQuery activity
Live route protected
Automate
Use your MCP tools in workflowsRemote MCP clients for visual workflows
ZapierComing soonSoon
n8nMCP Client Tool
MakeComing soonSoon
ActivepiecesComing soonSoon

Transport and authentication support varies by platform. Use a client compatible with the datamcp remote MCP flow.

Use
Open in AI clientsOne link, many workflows
View client setup
Connect cloud and private infrastructure
Supabase
Neon
AWS
Google Cloud
DigitalOcean
Docker
Private PostgreSQL

Everything inside datamcp

Pick the source.
Keep one controlled path.

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.

APIs02
OpenAPI

Turn OpenAPI into approved MCP tools.

Import OpenAPI 3.x or Swagger documentation, expose discovery, and allow only the HTTP methods one link needs.

Explore OpenAPI to MCP
Private PostgreSQLLive

Keep port 5432 closed.

Run the Local Agent on EC2, a VPS, or Docker. The PostgreSQL password stays on that machine; SQL and results pass through datamcp cloud.

See Local Agent Tunnel
Shared project context03

Give several AI chats one durable project memory.

Save deliberate decisions, progress, risks, and handoffs in an append-only record that compatible clients can search later.

Explore Agent Memory
Gateway controls04
Per-link accessDifferent policy for every client
Client authenticationOAuth 2.0 + PKCE or API keys
Revoke one linkDo not rotate the backend secret
Credential isolationBackend secrets stay connection-side

One hosted MCP gateway, with boundaries you can explain.

Create remote HTTPS links for specific tools, environments, and people. Database activity and permission denials stay reviewable.

See gateway controls

Local Agent Tunnel / shipped

Private PostgreSQL.
Hosted MCP access.

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.

● outbound connectionPostgreSQL only
PRIVATE NETWORKPostgreSQLpassword stays here
→
YOUR MACHINE@datamcp/agentEC2 · VPS · Docker
↓ outbound HTTPS
DATAMCP CLOUDScoped hosted MCP linkSQL requests and results pass through the cloud

Built-in playground

Test the link before
you ship it.

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.

PostgreSQLMySQLSchemaQueriesPermissions
datamcp playground storefront-db
Show customer 1842 and their last three orders.
TOOL CALLget_schema · customers, ordersALLOWED · 126ms
TOOL CALLquery · SELECT ... LIMIT 3ALLOWED · 94ms
Customer found.

Sam Rivera · Pro plan · 3 recent orders totaling $428.00.

Ask your database...↵

Database or API to MCP link

One. Two.
Three.

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 guide
  1. 01
    Choose a source

    Connect PostgreSQL, MySQL, or Swagger/OpenAPI, create Agent Memory, or choose Local Agent for private PostgreSQL.

  2. 02
    Create a safe link

    Choose read-only or write access. Database credentials and API tokens never reach the AI client.

  3. 03
    Drop the URL into your builder

    Use the hosted endpoint in Cursor, Claude, ChatGPT, VS Code, or another client that supports the required remote MCP flow.

Security is the product

Real access.
Real boundaries.

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.

AES-256-GCMCredentials encrypted at rest
Verified TLSCloud CA certificates built in
OAuth 2.0 + PKCESecure client authentication
Database query historyReview PostgreSQL and MySQL queries and permission denials
FOR PRIVATE POSTGRESQL

Keep inbound database access closed and the password on your agent machine.

Explore Local Agent Tunnel

Pricing

Start with one source.
Scale when it matters.

Free includes one source and one hosted MCP link forever. Upgrade when you need more sources, links, retention, chat, or team capacity.

Starter

$9/ month

Add one more source and MCP link beyond Free.

  • 2 source connections total
  • 2 MCP links total
  • No built-in chat
Start 14-day trial

Pro

$19/ month

For developers shipping with AI.

  • 3 source connections
  • 5 MCP links
  • AI chat: 100 messages/day
Start 14-day trial

Enterprise

$49/ month

For teams that need oversight.

  • 15 source connections
  • 50 MCP links
  • AI chat without plan message limit
Choose Enterprise

Your database or API. One link. Their next build.

Stop mocking.
Start shipping.