F
licenseNot graded
qualityC
maintenanceDeploy, manage, and scale applications directly from your AI assistant.
6
Croft
by net.oncroft
Server Details
Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsB
Average 3.9/5 across 26 of 26 tools scored. Lowest: 2.7/5.
Server CoherenceA
Disambiguation4/5
Most tools target distinct resources and actions (create_app, delete_app, deploy, etc.). However, grant_access and invite_user both involve granting app access, which could cause confusion. Also, set_database_sharing and set_public_paths both affect data visibility but in different ways, which might require careful reading.
Naming Consistency4/5
The naming predominantly follows a verb_noun pattern (e.g., create_app, delete_app, list_apps, grant_access). There are minor deviations: two tools use 'set_' (set_database_sharing, set_secret) instead of a more specific verb, and request_public_data_access is a bit longer but still clear. Overall, the pattern is consistent and predictable.
Tool Count5/5
26 tools is on the higher end but appropriate for the full lifecycle management of apps on a platform workspace: provisioning, deployment, user/connector management, file operations, configuration, and monitoring. Each tool addresses a specific need without redundancy, and the count reflects the complexity of the domain.
Completeness4/5
The tool surface covers the entire app lifecycle from creation to deletion, including deployment, rollback, secret management, file editing, access control, connector management, and logging. Minor gaps: there is no tool to update an app's metadata (like description) or to list/delete secret keys by name (only set_secret exists). Overall, core workflows are well covered.
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!
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to scaffold, edit, live-preview, and deploy full-stack apps with built-in database, email, and push notification capabilities through natural language.19MIT
- FlicenseNot gradedqualityCmaintenanceDeploy full-stack apps from AI. 75+ tools: GitHub/Docker deploy, databases, environments, security, billing.2
- AlicenseNot gradedqualityBmaintenanceOBTO gives your AI assistant a hosted app platform: it scaffolds, deploys, and operates real full-stack apps — pages, APIs, database, scheduled jobs — in a workspace created automatically at your first Google sign-in.1Apache 2.0
