datamcp — Hosted Model Context Protocol for Databases, APIs, and Agent Memory
Server Details
PostgreSQL, MySQL, OpenAPI/Swagger, and shared Agent Memory with scoped access.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 12.3% over 81 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- DataMCP
TDQS
Scored across 14 tools
Tools are cleanly partitioned by resource (connections, databases, OpenAPI endpoints, Git repos) and action (list/get/search/call), so an agent can usually pick correctly. Minor overlap exists: get_readme is effectively a special case of get_file_content, and get_api_schema vs get_endpoint_details both expose API structure.
Nearly all 14 tools follow a predictable verb_noun snake_case pattern (get_schema, list_connections, search_tables, call_endpoint). The lone outlier is 'setup', which breaks the pattern but is clearly a one-off onboarding tool.
14 tools is well within a healthy range and each earns its place across the three advertised domains. The count is proportionate to covering database, API, and Git introspection without bloat.
Despite 'Databases' being in the server name, there is no query/execute tool for databases — only get_schema and search_tables, leaving the core DB workflow unusable. 'Agent Memory' from the description has no corresponding tools at all, and Git access is read-only, so the surface has significant gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
14 tool updates
- First observed
call_endpoint - First observed
get_api_schema - First observed
get_commit_history - First observed
get_endpoint_details - First observed
get_file_content - First observed
get_readme - First observed
get_repository_structure - First observed
get_schema - First observed
list_api_endpoints - First observed
list_connections - First observed
search_endpoints - First observed
search_repository_files - First observed
search_tables - First observed
setup
Related MCP Connectors
Versioned agent memory in your own Postgres: portable context, permissioned, audit trail.
Document hosting and encrypted agent memory with multi-tenant persistence.
Supabase-compatible Postgres for agents: projects, branches, SQL, auth, storage, email.
Secure durable memory and bounded context for AI agents, with hosted OAuth and local Lite support.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to store, retrieve, and manage contextual knowledge across sessions using semantic search with PostgreSQL and vector embeddings. Supports memory relationships, clustering, multi-agent isolation, and intelligent caching for persistent conversational context.21 npm50MIT
- FlicenseAqualityBmaintenanceEnables AI agents to persist, search, and query shared memories in PostgreSQL through hybrid retrieval, preset answers, and AI-to-AI consultation via MCP.9-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to persist, retrieve, and share source-linked memory across sessions via MCP tools, backed by PostgreSQL with project/session management, decision tracking, keyword search, and cross-host context handoff.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceUser-owned shared memory for AI agents, providing a persistent, curated knowledge layer with hybrid search and cross-agent coordination via Postgres + pgvector.19Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.