AI-ERD
Server Details
AI-powered ERD design tool. Create and manage database schemas using DBML with real-time canvas.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.9/5 across 23 of 23 tools scored. Lowest: 1.8/5.
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (enum, ERD diagram, ref/relationship, table, table group) and a specific action (create, get, list, update, delete), making it easy for an agent to select the correct tool. For example, create_table vs. update_table are clearly differentiated by their action on the same resource.
All tool names follow a consistent verb_noun pattern throughout, with verbs like create, get, list, update, delete paired with nouns like enum, erd_diagram, ref, table, table_group. There are no deviations in naming conventions, making the set predictable and readable.
With 23 tools, the count is slightly high but reasonable for the domain of ERD diagram management, which involves multiple resources (diagrams, tables, enums, relationships, groups) each requiring CRUD operations. It feels comprehensive rather than bloated, though it borders on the upper limit of typical scope.
The tool surface provides complete CRUD/lifecycle coverage for all key resources in the ERD domain: ERD diagrams, tables, enums, relationships, and table groups. Each resource has create, get, list, update, and delete operations, with no obvious gaps that would cause agent dead ends. The descriptions even include important details like UUID usage and partial updates.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!